Should you really use rel=canonical pointing to the desktop for your separate mobile pages?

Why does Google recommend this canonical setup?

Google aims to simplify its crawling and indexing. When a site maintains two distinct versions (desktop at www.site.com and mobile at m.site.com), the risk is twofold: crawl budget dilution across two different URLs and duplicate content since the content is generally the same.

The rel=canonical directive from the mobile page to the desktop page clearly indicates that the desktop version is the referenced version for indexing. Google can then concentrate its crawl resources on a single URL while understanding that the mobile version exists for user display. It’s a signal of consolidation, not exclusion.

How does this directive align with mobile-first indexing?

This is where it gets tricky: Google indexes from the mobile version of your content since the shift to mobile-first indexing. But if you have separate mobile URLs with a canonical pointing to the desktop, Google will still index the desktop version (the one pointed to by the canonical) while evaluating content from the mobile version.

In practice, Googlebot crawls your m.site.com, detects the canonical to www.site.com, and indexes www.site.com. However, it uses the content and technical signals from m.site.com to assess that page. It seems counterintuitive but aligns with their logic of consolidation.

What is the alternative to this setup?

The modern alternative is responsive design or dynamic serving on a single URL. A single URL that adapts its display based on the device completely eliminates the canonicalization issue between versions.

If you absolutely maintain two separate URLs, the reverse setup (canonical from desktop to mobile) is technically possible but not recommended as it complicates crawl budget management and conflicts with historically expected behaviors from Google. Mueller confirms here the expected canonical direction.

• Use rel=canonical from mobile to desktop to concentrate indexing on a single version
• Serve the mobile version to mobile user-agents via server detection or 302 redirection
• Ensure that both versions have equivalent content to avoid indexing inconsistencies
• Opt for responsive design if you are revamping your site to eliminate this complexity
• Check that Google is correctly following your canonical via Search Console (Coverage tab, User-defined canonical section)

Is this recommendation still relevant today?

Let’s be honest: maintaining two distinct URLs for mobile and desktop is a legacy architecture that dates back before 2015. Most modern sites have migrated to responsive design. This guidance from Mueller remains valid for sites that have not yet made this transition, but it should not encourage you to create separate mobile URLs.

The issue with this setup is that it adds a layer of technical complexity: you have to maintain two templates, manage content consistency between versions, and monitor that canonicals are correctly in place across all pages. It’s a common source of errors, especially on large e-commerce sites generating thousands of pages.

What inconsistencies are observed in practice?

In practice, we regularly see Google not respecting the canonical defined by the site. If the mobile version has stronger relevance signals (direct backlinks, higher user engagement, better Core Web Vitals), Google may decide to index the mobile version despite the canonical pointing to the desktop. [To be verified] Officially, Google claims to follow canonicals, but crawl logs often show different behaviors.

Another field observation: sites with mobile versions that have poor content (truncated text, missing images) while canonicalizing to the desktop often see their positions decline. Google evaluates from the mobile but indexes the desktop, creating an inconsistency between the evaluated content and the served content. It’s a classic pitfall.

In what cases is this configuration still justified?

It makes sense for sites with heavy technical constraints that prevent a responsive overhaul in the short term: old proprietary CMS, complex architectures with dozens of templates, small technical teams. In this context, the mobile→desktop canonical setup allows for time savings before migration.

Another case: sites that deliberately provide radically different experiences based on the device (progressive web app on mobile, feature-rich desktop version). But beware, this approach requires constant monitoring of indexing to prevent Google from favoring the wrong version.

What should you prioritize checking on your site?

First instinct: open Search Console and filter by device type. Look at which URLs are indexed. If you see a mix of desktop and mobile URLs in the index, your canonical configuration is not working correctly. Google should only be indexing the desktop versions if your canonicals are appropriately followed.

Second check: crawl your site using Screaming Frog in mobile and desktop mode separately. Export the detected canonicals. Each mobile page should systematically point to its desktop equivalent. A single mobile page that points to itself or lacks a canonical creates a leak that dilutes your crawl budget.

How can you fix a faulty canonical configuration?

If your canonicals are absent or inconsistent, the correction depends on your technical setup. For a site using WordPress, check your mobile detection plugin (WPtouch, etc.) and make sure it correctly injects the canonical pointing to the desktop version. For custom development, add the tag in the of your mobile template.

Beware of the self-referential canonical trap: some CMSs automatically generate canonicals that point to the current URL. On a page m.site.com/page/, this would give you a canonical pointing to m.site.com/page/ instead of www.site.com/page/. It’s a common mistake that needs correction at the template level or through server rewriting.

Should you migrate to a responsive architecture?

Yes, if your technical roadmap allows for it. Responsive design eliminates all this complexity: a single URL, one content to maintain, no risk of misconfigured canonical. It’s the approach recommended by Google for years and the one that requires the least SEO maintenance.

Migration requires rigorous planning: auditing content differences between versions, preparing 301 redirects from mobile URLs, testing Core Web Vitals on the new responsive version. It’s a significant task, but it permanently removes the risk of indexing dilution between URLs. For complex sites with thousands of pages and critical business stakes, enlisting a specialized SEO agency can help secure this transition and avoid traffic losses during the migration.

• Check in Search Console that only desktop URLs are indexed
• Crawl the site in mobile mode and ensure that each mobile page contains rel=canonical pointing to desktop
• Test 10-15 random pages with the URL inspector in Search Console to validate that Google correctly detects the canonical
• Compare the visible content between mobile and desktop versions: they must be equivalent (text, images, links)
• Check that user-agent detection or 302 redirection to mobile functions correctly for visitors
• Plan a gradual migration to responsive design if resources allow