Can Google still index mobile-first even with a canonical pointing from mobile to desktop?

What exactly is a mobile-to-desktop canonical?

A mobile→desktop canonical annotation indicates to Google that the mobile page is not the reference version — the desktop version should be indexed instead. This setup was common during the era of m-dot sites (m.example.com) or sites with separate mobile URLs.

In this classic configuration, Google primarily indexed the desktop version and largely ignored the mobile version, except for searches conducted from a mobile where it could serve the mobile URL while relying on the indexed desktop content.

Why would Google choose to index mobile-first despite this canonical?

With the rollout of mobile-first indexing, Google has gradually reversed the logic: it now crawls and primarily indexes the mobile version of the site. But what happens when the mobile page itself says, "index the desktop instead"?

Mueller clarifies that if the mobile and desktop content is relevant and identical, Google may decide to index the mobile version despite the canonical. In short: Google demonstrates technical flexibility when it detects an inconsistency between the canonical annotation and the actual content.

What is the risk of this hybrid configuration?

This flexibility serves as a security for the end user, but it creates a gray area for SEO. You can't be sure which version will be indexed or how Google will arbitrate in case of subtle differences between mobile and desktop.

Sites with a mobile-dot and a mobile→desktop canonical face a risk of unpredictable indexing, with potentially fluctuating rankings depending on whether Google decides to honor the canonical or ignore it. This is why Mueller recommends transitioning to responsive.

• A mobile→desktop canonical normally indicates that the desktop version should be indexed
• Google can still choose to index the mobile version if the content is identical and relevant
• This technical flexibility avoids blatant inconsistencies but creates an uncertainty for SEO
• Transitioning to responsive eliminates this ambiguity by unifying mobile and desktop under the same URL
• Sites with m-dot or separate mobile URLs remain the most exposed to this fluctuation

Is this statement consistent with observed practices?

Yes, and it's actually reassuring. For years, we have seen that Google does not mechanically apply all technical annotations. Canonicals are "hints" — suggestions — not absolute directives. If Google detects an inconsistency between what the canonical states and what it sees in the content, it makes a decision.

In this case, it means that Google is willing to over-index mobile-first a site that technically asks for the opposite, to prevent relevant mobile content from being ignored. It's a form of safeguard that protects poorly configured — or transitioning — sites.

What nuances should we add to this claim?

Mueller speaks of "relevant and identical" content. What does that mean precisely? [To be verified] — Google provides no quantitative threshold. Is it a strict equivalence tag by tag, or a global semantic equivalence? Can we have 10% content difference without it blocking?

In practice, m-dot sites often have truncated content on mobile: lighter menus, different ad blocks, shortened text for mobile UX reasons. In such cases, does Google consider the content "identical"? Nothing is stated. This is where the recommendation to switch to responsive makes perfect sense: it eliminates this gray area.

In what cases does this configuration still pose problems?

If your mobile version is significantly impoverished compared to the desktop — reduced text content, missing images, absent structured data — then even if Google indexes mobile-first, you lose ranking potential. The mobile→desktop canonical will not save you.

Another problematic case: sites with conditional JavaScript that display different content based on the user-agent. Google crawls mobile-first with a mobile user-agent, and if your JS code detects this to serve a lighter version, you end up indexing this light version even if the canonical points to the desktop.

What should one do concretely if still on m-dot?

First step: audit content equivalence. Crawl your mobile version and your desktop version using Screaming Frog or an equivalent tool, and compare structural elements: title tags, meta description, Hn, text content, images, structured data. If you detect significant gaps, address them as a priority.

Second step: check in Search Console which version Google is actually indexing. Go to "Settings" > "Indexing" and check if your site is marked as "Mobile-first indexing enabled." If so, Google crawls and indexes your mobile version, regardless of the canonical.

What errors should be avoided in this hybrid configuration?

Do not assume that the mobile→desktop canonical "protects" you from underwhelming mobile indexing. Google can very well ignore this canonical if your content is deemed equivalent — and you end up indexed on an incomplete mobile version without realizing it.

Another classic mistake: leaving contradictory canonical tags in place. If your mobile page points to the desktop in canonical, but your desktop page points to itself (self-referencing canonical), Google has to arbitrate. The result: unpredictable behavior, possibly even partial indexing of both versions.

How to properly migrate to a responsive design?

Switching to responsive eliminates all ambiguity: one URL, one content, one canonical (self-referencing). This is the solution recommended by Google and the one that drastically simplifies SEO management.

Concretely: unify your URLs by keeping the desktop version as the canonical URL, redirect all mobile URLs in 301 to the corresponding desktop URLs, and switch the design to responsive using CSS media queries. Then test the mobile rendering with Google's "Mobile Optimization Test" tool and verify that the content is equivalent.

• Crawl and compare mobile vs desktop contents to identify discrepancies
• Check in Search Console if your site is already on mobile-first indexing
• Remove any contradictory canonical annotations between mobile and desktop
• Prioritize the transition to responsive to unify technical management
• Redirect m-dot URLs in 301 to desktop URLs during migration
• Test mobile rendering post-migration with the dedicated Google tool