Can Google ignore your desktop canonical in mobile-first indexing?

Why might Google ignore the canonical you specified?

In mobile-first indexing, Google first analyzes the mobile version of your site to determine which content to index and what ranking to assign. In this context, the engine might decide that the mobile URL is the canonical version, even if your canonical tag points to the desktop URL.

This behavior can be explained by the very principle of mobile-first: since Google crawls and prioritizes the mobile version, it makes sense for it to consider it as the primary reference. The canonical tag you put in place then becomes a guideline, not an absolute directive. Google reserves the right to choose the URL it considers most relevant as canonical, regardless of your stated preference.

When does this canonical substitution pose a problem?

John Mueller emphasizes that this choice is not an issue if the content is identical across both versions. The nuance is critical: if your mobile and desktop versions display exactly the same text content, the same meta tags, and the same structured data, then the fact that Google chooses one or the other as canonical has no impact on your SEO.

However, if you maintain content differences between mobile and desktop—for example, truncated text on mobile, hidden sections, or different title tags—then choosing the mobile URL as canonical could lead to indexing a diminished version. This is where the risk arises: you thought you controlled which version would be indexed, but Google decided otherwise.

How does Google make this decision in practice?

The official documentation does not detail the specific criteria that determine when Google chooses the mobile URL over the desktop URL as canonical. It can be assumed that several signals come into play: content consistency, URL structure, user engagement signals, and how both versions relate to one another.

What is clear is that the canonical tag is no longer a strict command but rather a strong recommendation that Google can ignore if it deems the mobile URL to be more representative. For the SEO practitioner, this means you can no longer rely solely on the canonical tag to ensure which version will be indexed—you need to check in real conditions what Google has actually chosen.

• Google can select the mobile URL as canonical even if you specified the desktop URL in the canonical tag
• This behavior is acceptable if the content is identical between mobile and desktop
• The canonical tag becomes a guideline, not an absolute directive in mobile-first indexing
• Content differences between mobile and desktop versions create a risk of indexing a diminished version
• It is essential to check in Search Console which URL Google has actually chosen as canonical

Is this statement consistent with field observations?

Since the gradual rollout of mobile-first indexing, many SEOs have noted discrepancies between the declared canonical and the one retained by Google. This statement from John Mueller confirms a reality observed over several years: Google takes the liberty to reevaluate the choice of canonical based on its own criteria.

What is new—or at least explicit—is the assertion that this behavior is intentional and considered normal by Google. Previously, it could be assumed that these were bugs or misinterpretations. Now, it's official: the canonical tag is a suggestion, not an order. [To be verified]: Google does not provide quantifiable data on the frequency of this behavior, nor on the specific criteria that trigger this choice.

What nuances should be added to this claim?

The statement "it is not a problem if the content is identical" deserves scrutiny. What does Google mean by "identical content"? Is it only visible text? Meta tags? Structured data? The full set of loaded resources? This lack of precision leaves significant room for interpretation.

In practice, even with identical textual content, there may be technical differences between mobile and desktop: resource URLs, image sizes, loaded scripts, loading times. If Google indexes the mobile URL, these differences may impact the Core Web Vitals and thus influence ranking. The statement "not problematic" should therefore be nuanced: technically maybe, but in terms of performance and user experience, it is debatable.

In what situations this rule may not apply as expected?

Several configurations can create ambiguous situations. For instance, a site with distinct URLs for mobile (m.example.com) and desktop (www.example.com): if the canonical points to desktop but Google chooses mobile, you end up with two indexed versions and a risk of poorly managed duplicate content.

Another problematic case: sites that display CSS-hidden content on mobile but visible on desktop. Google may consider that the content is "identical" since it is present in the HTML, but the user experience differs radically. If Google indexes the mobile URL with this hidden content, it may affect the perceived relevance of the page.

What should you do concretely to maintain control?

The first action is to check in the Google Search Console which URL Google has actually selected as canonical for each of your important pages. Use the URL inspection tool and consult the "Coverage" section to identify discrepancies between your declared canonical and the one retained by Google.

If you find that Google consistently selects the mobile URL while you prefer the desktop URL, ask yourself: why maintain two distinct URLs? In mobile-first, it is often simpler and safer to adopt a responsive architecture with a single URL for all versions. This eliminates any risk of canonical divergence and simplifies technical management.

What mistakes should absolutely be avoided?

Never assume that your canonical tag will be respected 100% by Google. Too many SEOs discover months after transitioning to mobile-first that Google is indexing the mobile URL when they thought they controlled the process via the desktop canonical.

Also, avoid maintaining substantial content differences between mobile and desktop while hoping that Google will always index the desktop version. If your mobile version is diminished (truncated text, missing images, removed sections), you risk Google indexing this diminished version and harming your ranking. Content parity is not optional; it is a requirement in mobile-first.

How to verify that your site is properly configured?

Set up a regular audit comparing the declared canonical and the canonical retained by Google. Automate this check via the Search Console API or crawling tools that compare both versions. Quickly identify pages where Google makes a choice different from yours.

Test also for content parity: crawl your site using both mobile and desktop user agents, then compare the extracted content. Differences should be minimal—ideally none for primary text content, title tags, meta descriptions, and structured data. If you detect discrepancies, correct them before Google penalizes them.

• Check in Search Console which URL Google retains as canonical for your strategic pages
• Systematically compare mobile and desktop content to ensure strict parity
• Favor a responsive architecture with a single URL rather than separate mobile/Desktop URLs
• Automate monitoring of the retained canonical via API or SEO monitoring tools
• Regularly test the mobile rendering via Google's URL inspection tool
• Document cases where Google chooses a different canonical and analyze possible reasons