Mobile-first indexing: what still trips sites up
Google now crawls and ranks with your mobile page almost everywhere. Here is what mobile-first indexing means today and the mistakes that still cost rankings.
Google decides how to crawl, index, and rank your site almost entirely from the mobile version of your pages now. That is mobile-first indexing, and most sites cleared the transition years ago without noticing. The mistakes that still cost rankings are the quiet ones: mobile pages that show less than desktop, structured data that only lives on one version, or content that never finishes loading before Googlebot moves on.
What mobile-first indexing means now
Mobile-first indexing is not a setting you turn on. It is how Googlebot behaves by default: it fetches your mobile page, or your responsive page rendered at a mobile viewport, extracts content, links, and structured data from that version, and uses it to build the index entry that ranking runs against. Google said the migration was effectively complete for the sites it crawls back in 2023, and retired the standalone mobile usability report in Search Console along with it. If your site still has a separate desktop-only view that Googlebot rarely sees, that is the version that matters least for ranking.
The content parity trap
The most common failure is subtraction. Teams trim a mobile layout to cut clutter and end up cutting paragraphs, related-article links, or entire sections that only render on desktop. Every word and link that disappears on mobile disappears from what Google indexes, even if the desktop version still has it in full.
- Author bios, methodology notes, or citations that only appear in a desktop sidebar
- Internal links buried in a desktop-only footer or related-posts widget
- Product specs or FAQ answers collapsed into a link that mobile never shows
- Reviews or comment sections rendered only above a certain screen width
None of this fixes itself. A page can look complete on a desktop browser and still lose the content that actually gets indexed, because nobody checked what the mobile viewport renders.
Structured data has to match too
Schema markup, hreflang tags, and meta robots directives all need to exist on the mobile version, not just desktop. It is an easy gap to introduce: a redesign adds Product or Article schema to the desktop template and the separate mobile template gets missed, or a canonical tag on the mobile page points somewhere the desktop version disagrees with. Google reads the mobile page for indexing, so structured data missing there is structured data Google never sees, no matter how complete the desktop markup is.
What is fine, and what isn't
Content hidden behind tabs, accordions, or a read-more toggle is fine. Google has treated that content the same as fully visible text for years, because on mobile especially, tucking secondary content behind a tap target is normal design, not an attempt to hide it.
The problem is content that never loads at all without a real interaction Googlebot will not perform, or that depends on a viewport check that skips execution on narrow screens. If a section only renders after a hover event, or a script checks window width and cuts the render short on mobile, it is invisible to the index, not just visually collapsed.
How to check your own site
- Use Search Console's URL Inspection tool and read the rendered HTML, not just the live test screenshot. Compare it against a desktop crawl of the same URL.
- Search for a sentence that only appears in desktop-sidebar content, using a site search plus an exact phrase. If it does not surface, Google likely never indexed it from mobile.
- Check structured data on the mobile-rendered page with a structured data testing tool, not the desktop URL.
- If you still run separate m.example.com URLs instead of responsive design, confirm the canonical and alternate tags are correct on both versions. That setup is increasingly rare, and worth migrating away from if you still have it.
If a fact, link, or schema field only exists on desktop, it does not exist to the index.
Responsive design mostly makes this a non-issue, which is why most teams stop thinking about mobile-first indexing once they adopt it. The sites still losing rankings to it are running older adaptive templates, or ones that quietly diverged during a redesign nobody re-audited. Pull up your own mobile render and read it the way Googlebot does. Whatever is missing there is what you are actually being ranked on.