Why does Google ignore your desktop structured data after switching to mobile-first indexing?

What exactly happens when a site migrates to mobile-first indexing? <\/h3>

Before the switch, Google primarily crawled and indexed the desktop version of your site. The structured data from the desktop served as a reference for all displays, both mobile and desktop. After migrating to mobile-first indexing, the strict reverse is true: Google only uses the source code of the mobile version for everything.<\/p>

This includes schema.org tags, JSON-LD, microdata, everything that serves to generate rich snippets. If a Product markup with price and rating exists on desktop but not on mobile, Google will not see it anymore—even to display a rich result to a user on a desktop screen.<\/p>

Why does this rule exist? <\/h3>

Google now indexes only one version of each page, the one it considers primary. For the majority of global traffic that comes from mobile, this primary version is logically the mobile one. Duplicating the indexing between two versions would create inconsistencies and waste crawl budget.<\/p>

The underlying idea: if information isn't important enough to appear on mobile, it isn't important at all. Google thus forces sites to align their content and structured metadata across all platforms.<\/p>

What does the transition period with two active crawlers mean? <\/h3>

While Google is preparing to switch a site to mobile-first indexing, both user-agents (Googlebot desktop and smartphone) may crawl simultaneously. This testing phase allows Google to verify that the mobile version contains all the necessary content and metadata before definitively cutting off desktop indexing.<\/p>

Once the migration is complete, only the mobile crawler remains active for that site. Logs then show a sharp drop in requests from the Googlebot desktop. From that moment on, any changes to the desktop structured data have no impact on the SERP.<\/p>

• Google exclusively uses the structured data from the mobile version after MFI
• The rich snippets displayed on desktop come from the mobile markup, not the desktop markup
• During the transition, two crawlers may coexist, but only one actually indexes after migration
• The alignment of metadata between mobile and desktop becomes mandatory, not optional
• Any structured data missing from mobile disappears from indexing, regardless of the viewing device
<\/ul>

Is this rule really applied strictly across all sites? <\/h3>

Field: Yes, with no exceptions observed. As soon as a site switches to MFI—and this applies to nearly the entire indexed web today—only the mobile version matters. We have documented dozens of cases where rich snippets for Product, Recipe, or FAQ disappeared on desktop after migration, simply because the markup existed only in the desktop code.<\/p>

The classic trap: sites that serve a lightweight mobile version with less content, fewer modules, and therefore less structured markup. Google does not compromise on this. If JSON-LD is missing on mobile, it's missing everywhere. [To verify]: Some ultra-optimized responsive sites hide content in CSS on mobile—does Google really ignore these hidden blocks, or does it parse them anyway? The guidelines say 'yes, it ignores them', but large-scale tests are lacking.<\/p>

What are the unexpected consequences of this rule? <\/h3>

First point: many sites still have divergent implementations between mobile and desktop, often due to different templates or separate caching systems. The schema.org markup becomes fragmented. Result: rich results that flicker between presence and absence based on recrawls.<\/p>

Second point: Google testing tools (Rich Results Test, Schema Markup Validator) sometimes crawl in desktop mode by default if you don't force the user-agent. You validate a markup that will never be taken into account. It’s essential to always test with the mobile URL or force the smartphone user-agent to see the truth.<\/p>

Caution: If you use a third-party tool that injects JSON-LD client-side via JavaScript only on desktop, Google will likely never see it after MFI. JS must also run on the mobile version and be detectable by the smartphone crawler.<\/div>

Should I absolutely duplicate all markups on mobile? <\/h3>

Yes, but with nuance. Duplicating doesn't mean 'pasting the same 150-line JSON-LD everywhere'. What matters is that the critical properties for rich results are present on mobile: price, rating, datePublished, author, etc. Some optional properties can be omitted if they do not influence the enriched display.<\/p>

Let's be honest: no one manually checks 10,000 URLs. You must audit by stratified sampling (product pages, articles, landing pages) and automate the detection of discrepancies between mobile/desktop versions. A script that compares the extracted JSON-LD from both user-agents saves weeks. [To verify]: Does Google really take into account structured data injected via Google Tag Manager in asynchronous mode on mobile? Officially yes, in practice rendering delays may pose problems.<\/p>