Mobile-First Indexing: What It Actually Means
Google ranks your desktop site based on what your mobile site contains. If the two differ, the smaller one is the one that counts — which is the opposite of how most sites are built and reviewed.
Google uses the mobile version of a page for indexing and ranking, including when serving desktop results. Content, headings, structured data or links that appear only on desktop are effectively invisible. The rule is content parity: the mobile page must contain everything that matters.
What Changed, and Why It Still Catches People
Mobile-first indexing means Googlebot crawls as a mobile device and indexes what it finds there. The desktop version is not a fallback and is not consulted — if content exists only on desktop, it does not exist for ranking purposes.
This is old news technically and still causes problems, because of how sites are built and reviewed. Designs are made on large screens, reviewed on large screens, and signed off on large screens. The mobile version is a derived artefact that fewer people look at carefully, which is exactly the wrong way round given which one Google reads.
The failure mode is rarely a broken mobile site. It is a mobile site that quietly contains less — a section hidden to reduce clutter, a table dropped because it did not fit, a block of supporting text removed because the page felt long on a phone. Each decision is defensible in isolation and collectively removes the substance that earned the ranking.
Responsive design mostly solves this, because there is one set of content reflowed rather than two versions. Problems concentrate in sites with a separate mobile version, or responsive sites that hide content at small breakpoints by removing it from the DOM rather than restyling it.
What Has to Match
Content parity does not mean identical layout. It means the mobile page must contain everything Google needs, which is a smaller list than it sounds.
The main content, in full
The same text, in the same depth. Reflowed, restyled and reordered is fine; shortened is not. This is where most parity problems live.
Headings
The same heading structure. A page whose mobile version drops half its H2s loses the structural signal that told Google what the page covers.
Structured data
The same markup on both. It is common for schema to be attached to a desktop-only template, which means the version Google indexes carries none of it.
Internal links
If your mobile navigation exposes fewer links, discovery and internal link equity both shrink. Collapsed behind a menu is fine — absent from the HTML is not.
Images and their alt text
Images serving a real purpose should be present on mobile with the same alt text. Dropping them entirely removes both the content and the accessibility.
Metadata
Titles, descriptions and canonical tags identical across versions. Divergence here produces conflicting signals about what the page even is.
How to Check Yours
Four checks that take a few minutes and cover nearly every parity problem.
- 01
Inspect a live URL in Search Console
Look at the rendered HTML and screenshot from Google's own mobile crawl. This is what is actually being indexed, and it settles arguments that testing on your own phone cannot.
- 02
Compare word counts between versions
Load the page at a desktop width and at 375px and compare the visible text. A large discrepancy means content is being removed rather than reflowed, which is the problem in a nutshell.
- 03
Check the mobile HTML for your schema
View source at a mobile viewport and confirm the structured data is present. This one is easy to miss because the desktop page validates perfectly.
- 04
Test at 360px, not 390px
Test at the smallest width your traffic actually uses. Many layouts hold together at 390px and break at 360, and a substantial share of Indian mobile traffic is on the smaller end.
Common Questions
What people ask about mobile indexing.
Does hidden content on mobile still count?
Content in the HTML but visually collapsed behind an accordion or tab is indexed and counts normally. Content that is not in the HTML at all — removed at that breakpoint, or loaded only on interaction — does not. The distinction is presence in the markup, not visibility.
Do I need a separate mobile site?
No, and it is the harder path. Responsive design serves one set of content at every width, which removes parity problems by construction and halves the maintenance.
My audience is mostly desktop. Does this still apply?
Yes. Indexing is mobile-first regardless of who your visitors are — Google crawls as mobile and ranks desktop results from what it found. Your traffic mix does not change which version is indexed.
Is 'mobile-friendly' the same as mobile-first?
No. Mobile-friendly is about usability — tap targets, readable text, no horizontal scrolling. Mobile-first indexing is about which version Google reads. A site can be perfectly usable on mobile and still fail parity by omitting content.