Mobile-first indexing: what changed, what most sites haven't fixed.

Google now indexes the mobile version of your site first. That sentence is the whole story—everything else is detail about why most sites still have not caught up, and what the gap costs you in search visibility.

Mobile-first indexing became the default for all new sites in 2019 and rolled out fully across the web by 2023. Google's crawler behaves like a smartphone user. It renders your pages the way a mobile browser would, reads what it finds, and uses that version to decide where you rank. If your mobile version is thinner, slower, or structured differently than your desktop version, you are being indexed on the worse version of your site—every single day.

What mobile-first indexing actually means

Mobile-first indexing means Google's primary crawler is Googlebot Smartphone, and the content it reads on mobile is what ends up in the index. It does not mean Google only ranks you for mobile searches. It means the mobile version of your page is the source of record for ranking across all devices—phone, tablet, and desktop alike.

This matters because many small and medium business sites were built desktop-first. The designer built a rich, full-content desktop layout. The mobile version was an afterthought—collapsed menus, hidden sections, images that do not load, or a separate m-dot site with stripped content. Before 2019, this was fine. Google's desktop crawler saw the full version. Now it does not.

If you have ever opened your site on your phone and noticed the testimonials section is gone, or the service description is cut short, or that comparison table is completely missing—Google has noticed too. That content is invisible to the index.

What most sites still haven't fixed

Three categories of unfixed problems show up repeatedly across SME sites.

Hidden content on mobile. Tabs, accordions, and collapsed sections often get implemented in a way that hides content from the mobile crawler even when the user can technically expand them. Google has said it can index content inside collapsed elements—but only reliably when the element is present in the DOM and the content is not explicitly removed from the rendered page. Many older theme implementations actually strip those blocks from mobile HTML rather than just hiding them visually. If you view source on your mobile page and the text simply is not there, it will not rank.

Structured data that only lives on desktop. Schema markup—LocalBusiness, FAQ, Review, Service—is sometimes added only to the desktop template. On mobile, it is absent. Google uses the mobile page to evaluate structured data eligibility for rich results. No schema on mobile means no rich results in search, period.

Images without proper mobile attributes. An image with a src pointing to a 3000-pixel-wide file will render on desktop and look fine. On mobile, the browser downloads the same file, renders it at 360 pixels wide, and the page load time suffers. Beyond performance, images without alt text on mobile lose any signal that text would have contributed. The Core Web Vitals: the three numbers that decide if Google bothers post covers how image weight drives Largest Contentful Paint scores—and how that connects directly to ranking.

Why responsive design is necessary but not sufficient

Responsive design is the correct starting point, but it does not solve the indexing problem on its own. A site can be fully responsive—one codebase, one URL, CSS media queries doing the layout work—and still have mobile-first indexing gaps.

Here is a common scenario. A law firm or accounting practice has a responsive site built on a page builder. On desktop, the homepage shows a full biography section, a list of practice areas with paragraph descriptions, and a block of client testimonials with names and service types. On mobile, the page builder theme collapses that biography into a button, replaces the practice area descriptions with icons only, and hides the testimonials to save vertical space. The CSS makes it look clean. The DOM still contains the text—or sometimes it does not, depending on how the theme handles the breakpoint.

The developer calls it responsive. Google sees a mobile page with significantly less content than the desktop version. The thin mobile version is what gets indexed. Rankings drop, not because of a penalty, but because the content simply is not there to rank for.

The fix here is not technical in a complex sense. You check the rendered mobile HTML—using Google Search Console's URL Inspection tool or Chrome DevTools in mobile emulation mode—and confirm the text you want to rank for is present. If it is not, you fix the template. That is the entire task.

How to audit your own site in under an hour

You do not need a consultant to run a basic mobile-first audit. Here is the order of operations.

Step one: Check Google Search Console. Go to Coverage > Index > Indexed. Click through to a handful of your most important pages. Use the URL Inspection tool on each one. Look at the crawled-as field—it should say Googlebot Smartphone. If it does not, your site has not finished the mobile-first transition, which is rare now but worth confirming.

Step two: Use mobile emulation in Chrome. Open Chrome DevTools (Cmd+Shift+I on Mac, F12 on Windows), click the device toolbar icon, set it to a common phone size—iPhone 12 or Galaxy S20 work well. Navigate through your key pages. Look specifically at your service descriptions, your about section, any testimonials or case studies, and your contact information. Read the text. Is it the same text that appears on desktop? Is any of it visibly absent or replaced by a collapsed element?

Step three: View the page source on mobile. With mobile emulation active, right-click and view page source. Use Ctrl+F to search for a phrase you know is on your desktop page. If you cannot find it in the source, it is not in the DOM—and Google will not index it.

Step four: Check your structured data on mobile. Go to Google's Rich Results Test and run it against your homepage and your key service pages. Confirm the markup appears. If you added schema manually or through a plugin that only targets desktop templates, it may be absent on the mobile-rendered version.

Step five: Run a Core Web Vitals check on mobile. Use PageSpeed Insights—paste your URL and look at the Mobile tab, not the Desktop tab. The scores are often dramatically different. A site that scores 85 on desktop can score 42 on mobile. That mobile score is what drives your ranking signal. The why your slow site is a sales problem, not an IT problem post explains why the performance gap is a revenue problem before it is a technical one.

The specific fix list for professional service sites

Most SME professional service sites have the same five gaps once you look.

1. Service page descriptions that collapse on mobile. Keep them in the DOM. If a user needs to tap to expand, fine—but the text must be present in the rendered HTML.
2. No LocalBusiness schema on mobile. Add it to your mobile template directly, or confirm your schema plugin renders on mobile. Check with Rich Results Test.
3. Phone number formatted as an image. Some older sites display the phone number as an image to prevent scraping. Google cannot read image text. Use real HTML text for your number and address.
4. Different H1 on mobile. Some builders swap out headings at breakpoints. Your H1 on mobile should match or closely mirror your H1 on desktop. Inconsistent heading structure confuses the index.
5. Missing meta descriptions on mobile pages. If you use a plugin like Yoast or RankMath, confirm it outputs meta tags on all device types. Some caching or minification setups strip meta tags from the mobile-optimised version inadvertently.

McShanes Solicitors, a Northern Irish family law firm, had a site that performed well in desktop audits but had lost significant local visibility over twelve months. When we ran the mobile audit, the practice area pages were missing their main descriptive paragraphs on mobile—hidden inside a collapsing element that did not render in the DOM. The structured data was desktop-only. Fixing both, alongside a tighter internal linking structure, restored their local pack visibility within six weeks. You can read more in the McShanes Solicitors case study.

What this doesn't fix

Fixing mobile-first indexing gaps will not rescue a site with fundamentally thin content. If your desktop pages are two-sentence service descriptions with no specificity, making them visible on mobile does not make them rank. The indexed content needs to be good content—clear, specific, and answering questions people actually search. Mobile-first indexing surfaces what you have built. It does not build it for you.

It also will not fix off-page problems: no links, no mentions, no authority signals from other sites. Mobile-first indexing is a technical floor. Clearing it puts you in the game. Ranking above competitors requires the full foundation—content, authority, and technical health working together.

If you want to see where your site stands across all three, Search Foundations is where that work starts.