Does mobile-first indexing really ignore the desktop version of your site?

What exactly does 'main indexed version' mean?

When Google says it primarily indexes the mobile version, it means that mobile content is what matters for ranking. The bot simulates a smartphone, crawls this version, and this version determines whether you rank or not.

The desktop version is not ignored — Google knows it and sometimes crawls it — but it takes a back seat. If a crucial element exists only on desktop, Google probably won't see it as a ranking signal. This is where many historical sites struggle, having neglected their mobile versions for years.

Why does Google count impressions only on the mobile version?

Data in Search Console now reflects the mobile version. When a user sees your site in the SERPs, regardless of whether they are on desktop or mobile, Google attributes the impression to the mobile URL. This is the URL that is 'canonical' for Google in its mobile-first logic.

This simplifies their internal accounting, but it can cause confusion. You might see mobile impressions for queries you thought were desktop-only. In fact, Google no longer really distinguishes between desktop and mobile for impressions once you are switched over. It's the mobile that counts.

What does it mean to 'exchange language URLs, but not desktop/mobile'?

Google can substitute a hreflang URL in the results based on the user's language/region. If you have a site in French and one in English with hreflang properly configured, Google will display the right version based on context. That's the 'exchange' Mueller refers to.

However, desktop and mobile URLs remain distinct in the index. Google does not automatically merge them. If you still have a separate desktop site (m.example.com vs www.example.com), both URLs coexist — but it is the mobile version that takes precedence for indexing. No automatic exchange here: if a desktop user clicks, they might end up on the mobile URL in the SERPs, and vice versa in some cases.

• Mobile version = reference version for ranking and indexing after mobile-first transition
• Search Console impressions counted on the mobile URL, even for desktop traffic
• Distinct desktop/mobile URLs in the index — no automatic merging, unlike language variants
• Hreflang works normally: Google can exchange language URLs, but not device URLs
• Content missing on mobile = invisible to Google, even if it exists on desktop

Is this statement consistent with what we observe in the field?

Yes, and this is indeed a recurring friction point. Audits regularly reveal gaps in mobile/desktop content that hinder ranking. A classic example: e-commerce sites that hide SEO text blocks in accordions on mobile 'for UX', which Google completely ignores.

We also observe that sites with separate desktop/mobile versions (m.example.com) continue to create inconsistencies in Search Console. Impressions are counted on m., but some backlinks point to www., and Google does not always transfer link juice transparently. [To be verified] the extent to which Google really consolidates signals between these two URLs — official statements remain vague on this point.

What nuances should be added to this statement?

Mueller says 'primarily', not 'exclusively'. Google can still crawl the desktop version, notably to check for consistency or explore related content. But don't be misled: if your mobile version is lacking, your flawless desktop won't save you.

Another significant nuance: sites with responsive design are not affected by this story of distinct URLs. A single URL serves the same content (adapted in CSS), so there is no possible confusion. The issue mainly arises for legacy architectures with mobile subdomains or separate domains. If you are still in this situation in 2025, it's an urgent task to plan for.

In what scenarios might this rule not apply strictly?

Google mentions that some sites will never be switched to mobile-first if their mobile version is catastrophic. In this case, indexing remains desktop-first by default — but this is a temporary lifeline, not a viable strategy. Google could very well decide to force you to switch one day, and that's when the fall begins.

Another observed exception: very specific desktop content (complex online tools, heavy web applications) that simply does not make sense on mobile. Google sometimes seems to tolerate these particular cases, but [To be verified] how much this tolerance applies — official guidelines do not detail these edge cases. In practice, it's better not to count on this and to plan for a minimally functional mobile version.

What should you prioritize checking on your mobile version?

Start with a desktop/mobile parity audit. Compare page by page: titles, meta descriptions, Hn tags, text content, images with alt attributes, structured data, internal links. Anything missing on mobile is potentially lost to Google. Crawl tools like Screaming Frog or OnCrawl can allow you to crawl both versions and generate difference reports.

Next, check that your critical elements are not hidden in CSS or JavaScript on mobile. Google has made progress on rendering JS, but content hidden behind a 'See more' or a tab can still pose a problem. Test with the URL inspection tool in Search Console to see what Googlebot mobile actually sees.

How to manage distinct desktop/mobile URLs if you still have them?

If you are on a m.example.com architecture, ensure that the rel="alternate" and rel="canonical" annotations are bidirectional and consistent. The desktop version should point to the mobile version with alternate, and vice versa with canonical. A mistake in this configuration, and Google can ignore one of the two versions or create duplication.

But let's be honest: this architecture is obsolete. Plan a migration to responsive or dynamic serving with a single URL. It simplifies maintenance, eliminates risks of duplicate content, and aligns your site with Google's expectations. It’s a technical undertaking, for sure, but it’s an investment that quickly pays off in SEO stability.

What to do if your traffic dropped after the mobile-first switch?

Analyze Search Console segment by segment: queries, pages, devices. Identify pages that have lost positions and compare their mobile version to the desktop. Often, the culprit is truncated content, missing images, or absent internal links on mobile.

Correct content discrepancies as a priority. Deploy the changes, force a re-crawl via the Indexing API or the inspection tool, and monitor the evolution over 2-4 weeks. Google does not reindex instantly, especially on large sites. If the situation does not improve, consider a thorough technical audit — sometimes the issue runs deeper (poorly rendered JS, catastrophic Core Web Vitals, etc.).

• Audit content parity between desktop/mobile page by page
• Check rel="alternate"/rel="canonical" annotations if distinct URLs
• Test mobile rendering with Search Console's inspection tool
• Eliminate hidden or deferred content in JavaScript on mobile
• Migrate to responsive design if separate mobile architecture
• Monitor server logs to confirm effective mobile-first switch