Quick Answer: Most UK web traffic now comes from phones, and Google finished moving every site to mobile-first indexing in 2023. In practice, the mobile version of your site is the one Google reads and ranks. If it's slow, cramped or missing content, your rankings suffer, even for people searching on a desktop.
Look at your own website statistics and you'll probably find that most visitors arrive on a phone. For local searches such as "plumber near me" or "electrician in Manchester", the share is usually higher still, because people search when they're out or when something has just gone wrong.
Google adjusted to this years ago. It now reads and ranks the mobile version of every website. If your site looks lovely on a laptop but awkward on a phone, Google only sees the awkward version, and ranks you on that.
This guide explains what mobile-first indexing means, why it matters and what to do about it, whether you're a plumber, a solicitor or running a small shop.
What is mobile-first indexing?
Until 2018, Google read the desktop version of each website and ranked it on that. As phone use took over, that stopped making sense: a site that looked perfect on a big monitor could be unusable on a phone.
So in March 2018 Google began switching sites over to mobile-first indexing, and by late 2023 the move was complete. Since then, the mobile version of a site is the one Google stores and ranks.
Desktop still matters to your visitors. But for Google, the mobile site is the starting point, and if it's weak, your rankings everywhere suffer.
Mobile-first, responsive and mobile-friendly: what's the difference?
| Term | What It Means | Is It Enough? |
|---|---|---|
| Mobile-first indexing | Google using your mobile site for ranking | Not a design choice. It's simply how Google works now |
| Responsive design | One site that rearranges itself for any screen size | Yes. This is the approach Google recommends |
| Mobile-friendly | The site works on a phone, but wasn't designed for one | Partly. Better than nothing, but not ideal |
| Separate mobile site (m.) | A different address for phone users, e.g. m.example.com | Outdated, and often leaves content out |
Responsive design is the answer for nearly everyone: one website whose layout adapts to whatever screen it's on.
Why it matters for your business
A local business feels this directly. Someone with a burst pipe at 9pm doesn't switch on a laptop. They grab their phone. If your site takes eight seconds to load, has tiny text or buttons too small to tap, they go to the next business on the list.
Google's own research found that as a mobile page's load time goes from one second to three, the chance of the visitor leaving rises by about a third. At five seconds it nearly doubles.
There's no opting out and no desktop-only setting. Every site is judged on how it performs on a phone.
How Google's mobile crawler works
Google reads your site with a crawler called Googlebot Smartphone, which visits pages as if it were an Android phone. It reads the text, images and links on your mobile pages, picks up structured data and page titles, and stores that mobile version as the one it ranks. Separately, Google uses real visitors' Core Web Vitals data to judge how good the experience is.
The important consequence: anything that exists on your desktop site but is missing from the mobile version may simply not count. Watch out for:
- text removed from mobile pages to "keep things short"
- images hidden on mobile to save space
- menu links that are cut down or missing on mobile
- structured data that only appears on the desktop version
Content tucked inside expandable sections is fine, as long as it's in the page. That's why responsive design works so well: everyone gets the same content, laid out differently.
What if my mobile and desktop sites differ?
This is the commonest problem on older websites. Many businesses built a desktop site first and then a stripped-down mobile version, or even a separate m. site with half the content missing.
| Scenario | Impact on Ranking |
|---|---|
| Mobile site has all the desktop content | No problem |
| Mobile site puts content in expandable sections | Still indexed, as long as it's in the page |
| Mobile site drops images | Lost image search traffic and a poorer experience |
| Mobile site has no structured data | Rich results such as FAQs and star ratings can disappear |
| Mobile site takes 8+ seconds to load | Poor Core Web Vitals and most visitors gone |
| Separate m. site with less content | Google ranks the thinner version |
If your site is responsive, you're probably fine; just check nothing is hidden on mobile. If you still have a separate mobile site, it's time to merge it into one responsive design.
How to check your site
Step 1: Test mobile speed
Go to PageSpeed Insights, enter your address and look at the Mobile tab, not Desktop. You'll get a score out of 100 and a list of suggestions.
- A performance score below 50 is a problem. Above 90 is good.
- Largest Contentful Paint (LCP) should be under 2.5 seconds.
- Interaction to Next Paint (INP) should be under 200 milliseconds. INP replaced the older First Input Delay measure in 2024.
- Cumulative Layout Shift (CLS) should be under 0.1.
Step 2: Check Google Search Console
If you haven't set up Search Console yet, it's free and worth doing. Under Settings you can confirm that Googlebot Smartphone is the main crawler for your site. The Core Web Vitals report shows how real mobile visitors experience your pages. (Google retired its separate Mobile Usability report at the end of 2023, so use Lighthouse in Chrome for layout checks instead.)
Step 3: Try it on a real phone
Open your website on your own phone, ideally on mobile data rather than wi-fi, and ask yourself:
- Can I read the text without zooming?
- Are buttons big enough to tap with a thumb?
- Does the page appear within about three seconds?
- Is the menu easy to use on a small screen?
- Do the forms work properly?
Step 4: Compare content side by side
Open the site on a desktop and a phone together and check the same content, images, menu links and forms appear on both, along with any structured data. If something's missing on the phone, Google can't see it either.
The most common mobile problems
1. Slow loading
Plenty of small business sites take five seconds or more to load on a phone, against Google's target of 2.5. The usual reasons:
- uncompressed images, where a single photo is 2MB when 200KB would do
- too many scripts loading before anything appears
- no browser caching, so every visit downloads everything again
- overloaded cheap hosting
2. A shrunken desktop layout
The site technically works on a phone, but it's the desktop design squashed down. Text is tiny, columns are cramped and people have to pinch and zoom. That's mobile-friendly at best, not mobile-first.
3. Content missing on mobile
Some sites hide whole sections on phones to "simplify" things. If the crawler can't see your selling points, service areas or prices, Google can't rank you for them.
4. Tiny tap targets
Buttons and links that are too small or too close together. WCAG 2.2 sets a minimum of 24 by 24 pixels; Google's Lighthouse suggests 48 by 48 for comfortable tapping.
5. Intrusive pop-ups
Full-screen pop-ups on a phone, especially as the page loads, annoy people and count against you in Google's page experience guidance. A small banner is fine. A full-screen overlay isn't.
How to fix it
Priority 1: speed
| Fix | Difficulty | Impact |
|---|---|---|
| Compress images (WebP format) | Easy | High |
| Enable browser caching | Easy | Medium |
| Minify CSS and JavaScript | Medium | Medium |
| Upgrade to faster hosting | Easy | High |
| Use a CDN (Content Delivery Network) | Medium | Medium |
For images, WebP is typically 25 to 35% smaller than a JPEG of the same quality, and every modern browser supports it.
If your site sits on very cheap shared hosting, moving to a decent managed plan with modern servers can make a dramatic difference on its own.
Priority 2: layout
- Use responsive CSS with media queries.
- Include the viewport tag:
<meta name="viewport" content="width=device-width, initial-scale=1"> - Size things in relative units (%, vw, rem) rather than fixed pixels.
- Stack columns on top of each other on small screens.
- Keep body text at 16px or larger.
Priority 3: the same content everywhere
- Don't remove content on mobile. Use expandable sections if space is tight.
- Make sure images aren't hidden on mobile with
display:none. - Keep structured data and menu links identical on both versions.
Priority 4: the details
- Give tap targets room: at least 24 by 24 pixels, ideally 48 by 48, with a little space between them.
- Remove full-screen pop-ups on mobile.
- Make email addresses tappable, for example
<a href="mailto:hello@example.co.uk"> - Use big, clear buttons for the action you want people to take.
Mobile-first indexing and Core Web Vitals
| Aspect | Mobile-First Indexing | Core Web Vitals |
|---|---|---|
| What it is | Which version of your site Google reads | How good the experience is for real visitors |
| Focus | Content and structure | Speed, responsiveness and stability |
| Effect | Decides what content Google sees | One of the signals behind your position |
| How to check | Google Search Console | PageSpeed Insights, Search Console |
Mobile-first indexing is about whether Google can see your content. Core Web Vitals are about whether that content gives people a good experience. You need both.
A mobile site with all the right content that takes eight seconds to load will be indexed but rank poorly. One that loads instantly but hides half its content will be quick but invisible for whatever is missing.
Happily, fixing one usually helps the other. Compressing images speeds the site up and keeps them on the mobile version; responsive design improves the layout and keeps content visible.
For more on the speed side, read our Core Web Vitals Fix Guide and Why Website Speed Matters in 2026.
Frequently Asked Questions
What is mobile-first indexing in simple terms?
Google uses the mobile version of your website to decide where you appear in search results. It finished switching every site over in 2023. If your mobile site is slow or missing content, your rankings drop, even for people searching on a desktop.
Does mobile-first indexing mean Google only looks at my mobile site?
For indexing and ranking, yes. Google reads and stores the mobile version. If your site is responsive, the mobile and desktop content are the same anyway, so there's nothing extra to worry about.
My website looks fine on my phone. Is that enough?
Not necessarily. Looking fine and performing well aren't the same. A site can look normal but still take five seconds or more to load, jump about as images appear, or have links too close together to tap. Check the technical side in PageSpeed Insights, not just how it looks.
Should I build a separate mobile website?
No. Google recommends responsive design: one website that adapts to every screen. Separate mobile sites (m.example.com) are harder to maintain and often end up with less content, which hurts rankings.
How fast should my mobile site load?
Google's target for Largest Contentful Paint, the moment the main content appears, is under 2.5 seconds. Under two is better. Beyond four, you're losing a lot of visitors.
Does mobile-first indexing affect local SEO?
Very much. Local searches happen mostly on phones, often from people who need someone soon. When someone searches "plumber near me" or "solicitor in [your town]", a poor mobile site puts you behind competitors with better ones.
I have an old website. Do I need a complete rebuild?
Not always. Plenty of mobile problems can be fixed on an existing site: compressing images, adding the viewport tag, fixing the responsive CSS, better hosting. But if the site is more than five to seven years old with a fixed-width layout, rebuilding is often cheaper than patching.
How often does Google check my mobile site?
It depends on how often your content changes and how established your site is. Most small business sites are crawled every few days to every few weeks. After a big change such as a redesign, you can ask Google to recrawl key pages through Search Console.
In short
Mobile-first indexing isn't new, but many UK small business websites still haven't caught up. Most visits come from phones, and local searches even more so. If your mobile site is slow, cramped or missing content, most of your potential customers never see you at your best.
The fixes are straightforward: compress images, make the layout responsive, keep all your content on the mobile version and move to better hosting if yours is slow. Most of this is hours of work, not weeks.
If you're not sure where you stand, put your address into PageSpeed Insights and look at the Mobile tab. If you score below 50, or there are problems you don't know how to fix, that's where we can help.
Get a free website review from Daedalus
We'll check your mobile performance, identify the problems, and give you a clear plan to fix them.
Get Your Free Review