What Is Mobile-First Indexing?

Mobile-first indexing means Google crawls, indexes and ranks your site using the mobile version of your pages, not the desktop version. Whatever the smartphone Googlebot sees is what gets indexed. Anything present only on desktop — text, links, structured data, images — effectively does not exist for search.

How we got here

Google started testing mobile-first indexing in 2016 and rolled it out gradually from 2018. In October 2023 it announced the transition was complete for all sites and retired the mobile-first indexing report in Search Console — there was no longer a set of "not yet migrated" sites to report on.

Then in July 2024 Google went further: from 5 July 2024, pages that aren't accessible from a mobile device are no longer indexed at all. Mobile rendering moved from a preference to a hard requirement.

Practically, this means mobile-first indexing isn't a project you complete. It's the permanent state of how Google sees your site.

What "the mobile version" actually means

Googlebot requests your pages with a smartphone user agent and renders them at a mobile viewport. The HTML it receives, plus whatever JavaScript execution produces, is your page as far as the index is concerned.

If your site is responsive — one URL, one HTML document, CSS adapting the layout — you're largely fine by default, because desktop and mobile deliver the same content. Responsive design is Google's recommended pattern for exactly this reason.

Where sites get into trouble is any setup where mobile and desktop deliver different content:

Separate m. subdomains. A dying pattern, but plenty of older sites still run one. The mobile version is what counts, so if m.example.com has trimmed copy, that trimmed copy is your page.
Dynamic serving. Same URL, different HTML depending on user agent. Same risk.
Conditional rendering. A React or Vue app that skips components below a breakpoint. This is the modern version of the same mistake, and it's easy to ship by accident.

The mistakes that quietly cost rankings

Content trimmed on mobile. Someone decides the mobile page is too long and hides three sections below a breakpoint with display: none in a way that removes them from the DOM. Those sections are now unindexed. This is the single most damaging mobile-first mistake.

Worth separating from a myth: content inside tabs and accordions on mobile is fine. Google has confirmed that collapsed content under mobile-first indexing is indexed and weighted normally — it's a legitimate response to a small screen. The problem is content that isn't in the mobile HTML at all, not content the user has to tap to expand.

Missing structured data. Schema is frequently added to a desktop template and forgotten on the mobile one. If your schema markup isn't in the mobile HTML, you lose rich-result eligibility entirely.

Different titles and meta descriptions. Shortened mobile titles become your titles. Write them once, for both.

Images that don't load for Googlebot. Lazy loading that only fires on a real user scroll event means Googlebot never triggers it and never sees the image. Use native loading="lazy", or an IntersectionObserver with a generous root margin. Also check that mobile images keep their alt text and aren't swapped for lower-resolution files too small to be eligible for Google Images.

Navigation and internal links stripped on mobile. Hamburger menus are fine — the links are in the HTML, just visually collapsed. What isn't fine is a mobile template that drops a footer or sidebar containing dozens of links. That changes your entire internal linking structure, and pages that were one click from the homepage on desktop can become orphan pages on mobile.

Blocked resources. If robots.txt blocks the CSS or JS your mobile layout depends on, Googlebot renders a broken page. Check your robots.txt isn't disallowing /assets/ or similar.

Intrusive interstitials. A full-screen popup that covers content immediately on arrival from search is a documented negative signal on mobile. Banners and slide-ins that leave the content readable are fine.

How to check your own site

Use the URL Inspection tool in Search Console and look at the rendered HTML and screenshot from the smartphone Googlebot — not what your phone shows you. This is the authoritative view.
Compare word counts. Fetch a page with a desktop user agent and a smartphone one, strip the markup, and compare. A large gap is the alarm.
Compare link counts. Same method, counting <a href>. This catches stripped navigation.
Diff the structured data. Run both versions through Google's Rich Results Test.
Load the page on a real phone. Rendering tools miss things like tap targets that are too close together and text at 11px.

What this doesn't mean

Mobile-first indexing is about which version gets indexed. It is not a separate mobile ranking algorithm, and it doesn't mean desktop traffic stopped mattering — plenty of B2B and SaaS sites still see the majority of conversions from desktop. Google indexes the mobile version and serves those results to everyone, including desktop searchers.

It also isn't a replacement for the rest of SEO. A perfectly rendered mobile page with no authority behind it ranks nowhere. Mobile-first indexing determines what Google can see; backlinks still determine a lot of where it puts you. Backlinkster covers the second half — one-for-one in-content swaps with owners of related sites, verified live by code, five free swaps a month to start. See the plans.

Frequently asked questions

Is mobile-first indexing still a thing in 2026? Yes, permanently. Google completed the transition for all sites in October 2023 and retired the migration report. Since July 2024, pages not accessible on a mobile device aren't indexed at all.

Does mobile-first indexing mean desktop rankings don't matter? No. Google indexes the mobile version and uses it to rank results shown on every device. Desktop searchers still see those results, and desktop still converts well for many businesses — it just isn't what gets crawled.

Is hidden content on mobile indexed? Content in tabs and accordions is indexed and weighted normally — Google has confirmed this repeatedly. Content that isn't in the mobile HTML at all is not indexed, which is a different problem with a different fix.

Do I need a separate mobile site? No, and it's actively discouraged. Responsive design — one URL serving one HTML document with CSS handling layout — is Google's recommended approach and removes the entire class of desktop/mobile mismatch problems.

How do I know if mobile-first indexing hurt my site? Use URL Inspection in Search Console to see the rendered mobile HTML. If content, links or structured data present on desktop are missing there, you've found the cause. Traffic declines from this are usually gradual rather than a single-day drop.

Does page speed matter more under mobile-first indexing? It's measured on mobile, which is the slower environment, so poor performance shows up more starkly. Speed remains a small ranking input — see Core Web Vitals for the thresholds that actually apply.

The bottom line

Mobile-first indexing has one practical rule behind it: the mobile version is the version. Every audit question reduces to "is this in the mobile HTML?" — the copy, the links, the schema, the images, the titles.

If you're on a responsive template and you haven't deliberately hidden anything below a breakpoint, you're probably fine. If you run a separate mobile experience, or a JavaScript app that conditionally renders components, spend an hour with URL Inspection comparing what Googlebot sees against what you think you published. That gap is where the rankings went.