Mobile-First Indexing Explained: What Google Reads, and Why It Matters on Desktop Too

Most people still think of mobile-first indexing as a future change to prepare for. It finished years ago.

What remains is a quieter problem. Sites whose mobile and desktop versions differ are often ranked on the weaker of the two, and nobody notices because they check their site on a laptop.

What mobile-first indexing actually means

Google uses the mobile version of a page as the version it indexes and ranks. It crawls with Googlebot Smartphone, reads the content and links that appear on mobile, and uses that for results on every device.

• It is not a separate mobile index. There is one index, built from mobile versions.
• It is not a ranking boost for mobile-friendly sites. That was a different, older idea, since folded into Google’s wider page experience signals.
• It applies to desktop searches too. A desktop searcher sees results ranked on what your mobile pages contain.

The timeline

Date	What happened
November 2016	Google announces it is experimenting with mobile-first indexing
March 2018	The rollout begins for sites that are ready
1 July 2019	Mobile-first becomes the default for new sites
31 October 2023	Google declares the switch complete
5 July 2024	All remaining sites move to the smartphone crawler; content not accessible on mobile becomes unindexable

The last step matters most for older sites. In June 2024 Google said that after 5 July it would crawl and index the remaining sites with Googlebot Smartphone only, and that a site whose content could not be reached on a mobile device would no longer be indexable.

You may still see Googlebot Desktop in your server logs. Google uses it for a few features, such as product listings and job listings, but not for normal indexing.

Three ways sites serve mobile visitors

• Responsive design. One URL and one HTML document that adapts to the screen. Google recommends it, and it makes mismatches between versions almost impossible.
• Dynamic serving. One URL, but the server sends different HTML depending on the device. It works, but every template change has to be made twice, and differences creep in.
• Separate mobile URLs. A mobile site on its own address, such as an m-dot subdomain, linked to the desktop pages with annotations. This is the setup most prone to missing content, broken links and mismatched tags.

If you run either of the last two, assume there are differences until you have checked. Moving to a responsive design removes the whole category of problem.

Where mobile and desktop versions usually differ

On a single responsive site the two versions are the same page, so problems are rare. They appear when mobile visitors are served something different.

• Content cut from mobile. Sections, tables or reviews removed to shorten the page on phones simply do not exist for Google.
• Internal links missing on mobile. A simplified mobile menu can leave whole sections of a site poorly linked.
• Structured data only on desktop. Markup added to a desktop template but not the mobile one is not seen.
• Different titles, descriptions or robots tags. A noindex on the mobile template removes the page entirely.
• Images that do not load on mobile, often because of lazy loading that never triggers for the crawler.
• Separate mobile sites on an m-dot address, where every one of these mismatches is easy to introduce.

Content inside tabs and accordions is fine. Google treats it as part of the page as long as it is in the HTML. The problem is content that is not there at all.

A parity checklist

For each main template, these should match between mobile and desktop:

• The main content, including tables, reviews and comments you want indexed
• Headings and their order
• Internal links, especially navigation to important sections
• Structured data, with the same values
• The title and meta description
• Robots directives, so mobile pages are not accidentally set to noindex
• Canonical tags pointing to the right version
• Images and their alt text
• Hreflang annotations on international sites

How to check what Google sees

1. Inspect a key URL in Search Console and confirm it was crawled by Googlebot Smartphone.
2. View the crawled page and its rendered HTML, and check your main content, links and structured data are present.
3. Compare it with the desktop page, section by section, for anything missing.
4. Repeat for one page of each template: home, category, article, product.

Templates are where differences hide. If one article template drops a section on mobile, every article on the site loses it.

When you find a difference, fix the template rather than individual pages. Then inspect one affected URL again and request indexing, so you can confirm Google now sees the corrected version before assuming every page is fixed.

What happens to pages that only work on desktop

A desktop-only design is not automatically a problem. If the page loads on a phone and its content can be read, even awkwardly, Google can still crawl and index it.

What fails is content a phone cannot reach at all: pages that block mobile browsers, redirect phone visitors to the homepage or an app store, or hide everything behind a full-screen message. Since July 2024, that content is simply not indexable.

Mobile-first indexing and traffic drops

The switch itself is long finished, so it rarely explains a new drop. What does cause drops is a change that breaks the mobile version without anyone noticing.

• A redesign that trims mobile content or simplifies navigation.
• A plugin or theme update that changes the mobile template.
• A pop-up or interstitial that covers content on phones.
• A mobile-only error, such as a script that fails on small screens.

A drop that appears on mobile and desktop at once, starting on the day a template changed, points here. Device-specific drops are covered in traffic dropped on mobile but not desktop, and redesign problems in traffic dropped after a website redesign.

Mobile usability still matters for people

Google retired its mobile usability report and test in late 2023, but your visitors did not change. On most sites the majority of search traffic comes from phones, so a page that is hard to use on a small screen loses people even when it ranks.

The Core Web Vitals report in Search Console still splits its data by mobile and desktop; how much those figures matter is covered in Core Web Vitals and rankings. If the mobile figures are much worse, that is where real visitors are struggling.

Common myths

• “Desktop rankings use the desktop version.” They use the mobile version, like everything else.
• “Hidden mobile content does not count.” Content in tabs and accordions counts in full.
• “A mobile-friendly badge means I am fine.” Google retired its mobile usability report and test in late 2023. Parity of content is the real test.
• “Mobile-first is a ranking factor.” It describes which version Google reads, not a bonus for being mobile-friendly.

How mobile indexing fits alongside Google’s other systems is covered in Google’s ranking systems explained.