Should you really point the canonical tag to the desktop version in a mobile-first world?

Why does Google index mobile but request a canonical link to desktop?

Since the shift to mobile-first indexing, the bot primarily crawls and evaluates the mobile version of your pages. This version determines ranking, content signals, semantic structure—essentially, everything that matters for positioning.

However, Mueller points out that you should still configure the rel=canonical link to the desktop version. Why? Because Google needs to understand the relationship between the two versions and identify which URL to display in the SERPs based on user context. The canonical no longer necessarily points to the "true" indexed version, but rather the reference version to present.

What changes compared to the desktop-first era?

Before mobile-first, the canonical served to consolidate signals to the main version—generally desktop. We pointed mobile to desktop to avoid duplication and concentrate authority on a single URL.

Today, the indexing is reversed: the mobile is the source of truth, but the canonical remains directed to the desktop to maintain display consistency. It may seem contradictory, but it aligns with Google's logic: index what matters (mobile), display what is canonical (desktop in appropriate contexts).

Does this recommendation apply to all types of sites?

No. If you have a responsive site with a single URL for both mobile and desktop, this directive does not directly apply to you: there is only one URL, so there is no question of inter-version canonical issues.

However, if you have two distinct versions—typically a subdomain m.example.com or a directory /mobile/—then you are in the thick of it. You need to maintain the canonical from mobile to desktop so that Google knows which URL to prioritize in search results based on the user's device.

• Mobile-first indexing = Google uses the mobile version to evaluate and rank content
• Canonical to desktop = Google displays the desktop URL in desktop SERPs, mobile in mobile SERPs, but indexes the mobile
• Responsive sites = no inter-version canonical needed, one URL per page
• Sites with separate versions = maintain the rel=canonical mobile → desktop and alternate desktop → mobile
• Risk = if misconfigured, Google may index the wrong version or display inconsistent URLs based on the device

Is this directive consistent with real-world observations?

Yes and no. In practice, most modern sites use a responsive design, which renders this question irrelevant for them. Google indexes a single URL, period. No canonical dilemma.

But for the rare sites still using dual versions (m.example.com vs www.example.com), this guideline remains valid. The problem? Mueller does not specify what happens if you do the opposite—point the canonical from desktop to mobile. [To be verified]: does this break indexing? Probably not, but it could create confusion in URL display in SERPs.

What nuances should be added to this recommendation?

First point: the mention of "canonical version for indexing" in Mueller's statement is awkward. The canonical does not designate the indexed version, but the reference version for display. The mobile is what gets indexed, but the desktop remains the canonical URL to present.

Second nuance: if your mobile site is significantly different from the desktop (truncated content, missing features), Google may penalize you in mobile-first. The canonical will not save you—it's the mobile content that will matter. Let's be honest: if your mobile experience is poor, you're in trouble.

In what cases does this rule not apply?

If you have a responsive site, you can ignore this directive. One URL = no inter-version canonical to manage. This is the case for 90% of sites in 2020 and beyond.

If you have an exclusively mobile site (no desktop version), obviously, there is no canonical to point elsewhere. And if you have a mobile app indexed through App Indexing, that's another topic—the canonical only applies to classic web URLs.

What practical steps should be taken on a site with separate versions?

If you still have a distinct m.example.com from www.example.com, configure the rel=canonical on each mobile page to point to the corresponding desktop equivalent. Additionally, add a rel=alternate on each desktop page to indicate the corresponding mobile version.

Ensure that both versions display the same main content—titles, paragraphs, media, structured data. Google indexes the mobile, so if the mobile version is lacking, your ranking will suffer. The canonical does not compensate for deficient mobile content.

What mistakes should be absolutely avoided?

Never point the mobile canonical to a different desktop page— for example, mobile:/product/A to desktop:/category/. This breaks the matching logic and Google may completely ignore you.

Also, avoid leaving the mobile version without a canonical at all, thinking that "mobile-first" means "mobile independent." No. Google needs the explicit relationship between versions to manage SERP display based on the device. And above all, do not duplicate content between mobile and desktop without canonical/alternate tags: this opens the door to pure duplication.

How can you verify that your configuration is correct?

Use the Search Console to inspect a mobile URL and check that Google recognizes it as indexed in mobile-first. Look at the "User-declared canonical" section: it should point to desktop if you have two distinct versions.

Crawl your site with Screaming Frog or Oncrawl in mobile + desktop mode and extract the canonical and alternate tags. Check for consistency: each mobile should canonicalize to its desktop equivalent, and each desktop should have an alternate to its mobile version. Any asymmetry is a red flag.

• Configure rel=canonical on mobile → desktop for each pair of equivalent pages
• Add rel=alternate on desktop → mobile with the attribute media="only screen and (max-width: 640px)"
• Verify that mobile content is as complete as desktop (text, images, structured data)
• Inspect URLs in Search Console to confirm that Google is indeed indexing the mobile version
• Crawl the site in mobile and desktop mode to audit the consistency of canonical/alternate tags
• Remove any residual canonical or alternate if you are migrating to a single responsive design