Mobile first indexing means Google crawls and indexes the mobile version of your pages rather than the desktop one. As Search Engine Journal reported when Google completed the switch, the move began in 2016 and was finished in October 2023. Seven years of advice about “getting ready” is now out of date. There is nothing left to get ready for.
What remains is a single practical test. If something exists on your desktop page and not on your mobile page, Google is working from the version without it. Most of this post is about finding those gaps.
What mobile first indexing means in 2026
The timeline is short and worth having straight, because a lot of older guidance still circulates as if the switch were optional or partial.
| When | What happened | What it means for you |
|---|---|---|
| 2016 | Google begins moving to crawling mobile pages rather than desktop | The mobile version starts to become the one that counts |
| October 2023 | Google completes the switch to mobile-first indexing | No site is waiting to be moved; all are on it |
| After 5 July 2024 | Google said remaining sites crawled with desktop Googlebot would be crawled with Googlebot Smartphone only | The desktop crawler is no longer the fallback |
| Same 2024 statement | Content not accessible at all on mobile would no longer be indexable | Missing on mobile means missing from the index |
The last row is the one that changes behaviour. Before July 2024, a site that kept some content desktop-only could still have it indexed through the desktop crawler. Google’s 2024 statement removed that safety net.
It also changes how you should read older audits. A report from before the switch that marked a desktop-only section as “fine because desktop Googlebot still sees it” was describing a fallback that no longer exists. If your site was built or last audited before 2024, the parity check below is worth running again rather than taking the old result on trust.
Mobile-unfriendly is not the same as inaccessible
This is the distinction most articles on the topic blur. A page that is awkward to use on a phone, with small text, cramped buttons or a layout that needs zooming, is mobile-unfriendly. That is a user experience problem, and it can cost you visitors, but it does not stop the page being indexed.
A page that is inaccessible on mobile is a different matter. If the content is not there when a smartphone crawler requests the page, it cannot be indexed from that page. The received wisdom says a responsive theme solves mobile-first indexing. It solves the friendliness problem. It does not guarantee the content is all there.
Content usually goes missing in one of three ways. A separate mobile template, or an m. subdomain, carries a slimmed-down version of each page. A theme setting drops sections, sidebars or related links below a certain screen width. Or a developer decides that long copy, tables or reviews are “too much” for a phone and removes them from the mobile markup entirely.
The more serious failure is blocking. Server rules, firewall settings or bot protection that treat the smartphone user agent differently from desktop can serve Googlebot Smartphone an error, a challenge page or nothing at all. Because desktop Googlebot no longer fills in, that is the whole page gone. If you run bot rules, check them for anything keyed to mobile user agents, and read our guide on how to get indexed by Google if pages have already dropped out.
Mobile-first indexing best practices: check for parity
The practical work is a parity check: does the mobile version carry everything the desktop version does that you care about for search? Four things need to match.
- Main content. The same body copy, headings, tables and media, not a summary.
- Structured data. The same markup on both versions, pointing to mobile URLs where they differ.
- Metadata. Equivalent titles, meta descriptions and robots directives.
- Images and links. Crawlable on mobile, with the same internal links available.
Start with the URL Inspection tool in Search Console on a handful of templates: a category page, a typical article and your most valuable commercial page. Look at the rendered HTML for the smartphone crawler and compare it with what you see on desktop. You are looking for absence, not styling.
Structured data is the item most often dropped. Mobile templates built separately, or plugins that output markup only in certain layouts, can leave the mobile page without the schema the desktop page carries. Since the mobile page is the one indexed, that markup effectively does not exist. Our guide to schema markup covers what to check.
Images deserve their own pass. Lazy loading that waits for a user to scroll or tap, rather than loading as the image enters the viewport, can leave images undiscovered on mobile. Links matter for the same reason: if the mobile menu removes links to whole sections, those sections lose internal links from every page on the version Google crawls.
What mobile-first indexing does not mean
It does not mean Google ranks only mobile searches with your mobile page, or that desktop users see something different in results. The index is built from mobile; the ranking is still about the query and the page.
It also does not mean page speed or Core Web Vitals are an indexing issue. They are related to mobile experience and worth working on, and our post on a failed Core Web Vitals assessment covers that. But a slow mobile page is still indexed. Treat speed and parity as two separate jobs, and do parity first, because it is the one that can remove pages from the index outright.
Here is the limitation. A parity check on a few templates tells you how those templates behave, not how every page behaves. Sites with conditional content, personalisation or A/B tests can serve the smartphone crawler something you never see in a manual check. Search Console’s indexing reports will show pages that drop out, but only after the fact. If your site has many templates, sample each one rather than assuming the homepage speaks for the rest.
For most sites built on a modern responsive theme, the check will come back clean. That is the honest finding: the work is usually small. The cost of skipping it is what makes it worth an afternoon, because a missing section on mobile does not throw an error. It simply never ranks. More checks of this kind sit in our technical SEO checklist.
Frequently asked questions
Does Google use mobile-first indexing for every site?
Yes. Google completed the switch in October 2023, and said that after 5 July 2024 remaining sites would be crawled with Googlebot Smartphone only.
How does mobile-first indexing affect your website?
Google indexes what the mobile version contains. Content, structured data or links missing from mobile are effectively missing from the index.
Will a site that is not mobile-friendly still be indexed?
Yes. Being mobile-unfriendly is a usability problem. Being inaccessible on mobile, through blocking or missing content, is what stops indexing.
Is a responsive design enough?
It usually solves layout. Check that the theme does not drop sections, links or markup at smaller screen widths.
The takeaway The switch is finished. Stop asking whether your site is ready and check whether the mobile version carries the same content, markup and links. Absence is the risk; looks are not.
