Skip to content

Mobile-first indexing

Mobile-first indexing means Google indexes the mobile version of a page. What it changed, what breaks under it, and why it is now simply how indexing works.

Definition

Mobile-first indexing means Google uses the mobile version of a page for indexing and ranking. It became the default for all sites, so the content, links and markup present on mobile are what Google evaluates, regardless of what the desktop version shows.

Illustration representing mobile-first indexing

Why it matters

Mobile-first indexing stopped being news some time ago, which is exactly why it still causes problems. It is assumed to be handled, and the failure mode is silent: content that exists on desktop and not on mobile is content Google does not see.

The practical rule is one sentence. If it is not on the mobile version, it does not count.

How it works

Google's documentation on mobile-first indexing describes crawling predominantly with the smartphone agent and using what it finds there for indexing and ranking.

For a responsive site, which serves the same HTML to every device and adapts with CSS, this changes nothing. Google's SEO starter guide treats responsive design as the default recommendation. The content is identical by construction, and that is why responsive design is the recommended configuration.

The problems arise when mobile and desktop differ in substance:

Content hidden or removed on mobile. A section dropped from the mobile layout to save space is a section Google does not index. Content inside tabs or accordions is fine, because it is in the HTML; content removed from the HTML is not.

Fewer internal links on mobile. A simplified mobile navigation that drops links changes the internal linking graph Google sees, and with it how link equity flows.

Structured data only on desktop. Schema markup present on one version and not the other is markup Google does not read.

Different metadata. Titles and descriptions that differ between versions mean the mobile ones are what appear.

Separate m-dot sites. The older pattern of serving m.example.com is the configuration most likely to diverge over time, and the one that needs the most care.

Worked example

The check takes a minute and is more reliable than opinion:

  1. Open the page on a phone, or in a device emulator.
  2. View the rendered HTML, not the desktop source.
  3. Confirm every section, internal link, piece of structured data, title and description is present.
  4. Compare against desktop. Differences are the risk list.
Two technical drawings pinned side by side, the smaller missing three components, each absence ringed
Compare the mobile rendering against the desktop one. The differences are the risk list.

The URL inspection tool in Search Console shows the rendered HTML Google actually received, which settles any argument about what is or is not there.

Common mistakes

  • Assuming responsive means done.
    Usually true, and worth verifying rather than assuming, particularly where components conditionally render.
  • Hiding content to simplify mobile.
    Collapsing it is fine. Removing it from the HTML is not.
  • Thinning mobile navigation to the point of dropping links.
    The links are part of what is indexed.
  • Testing only on desktop.
    The desktop version is not what is assessed.
  • Confusing it with Core Web Vitals.
    One is which version is indexed, the other is how that version performs. Both are mobile questions and they are not the same question.

Where it still bites

Sites with a separate mobile template, and single-page applications that render different content by viewport. Both are worth an explicit check in any mobile SEO review, because when this fails it fails quietly and the symptom is simply that pages never rank for terms the desktop content would have covered.

Let's build

Got something to build?

Tell us what you're making. We'll tell you - honestly - if we're the right team, and how we'd do it.