Should you really point mobile to desktop with rel=canonical?

Why does Google recommend canonizing mobile to desktop?

John Mueller's recommendation stems from a technical principle: the desktop version remains the reference for indexing in certain specific contexts. When a site maintains two separate URLs (m.example.com and www.example.com), Google must choose which version to index as the primary one.

By configuring rel=canonical from mobile to desktop, you explicitly inform Google that the desktop version is the canonical source. The search engine then consolidates all ranking signals (links, metrics) to this single URL. Mobile users see the mobile URL in the results, but it is the desktop version that accumulates authority.

Does this directive still apply with mobile-first indexing?

This is where it becomes tricky. Mobile-first indexing changes the game: Google crawls and indexes primarily the mobile version of your site. Mueller's recommendation concerns sites with separate URLs, a configuration that Google has been discouraging for years.

If you have a responsive site (one URL for both mobile and desktop), this directive simply does not apply to you. The rel=canonical makes no sense when there is only one URL. The confusion arises because many sites still maintain separate mobile URLs, often for legacy reasons or specific technical issues.

What is the difference between the indexed URL and the displayed URL?

Google can index one URL (desktop) while displaying another (mobile) in the SERPs depending on the user's device. This is a mechanism of URL substitution based on context. You won't see it in Search Console, but it's active on the user side.

Specifically: your desktop version accumulates the PageRank, backlinks are consolidated towards it, but a mobile user sees m.example.com/page in their results. Google automatically applies this logic when it detects the canonical tag and a correct mobile alternate annotation.

• Sites with separate URLs: rel=canonical mobile→desktop remains Google's recommended configuration to avoid duplication
• Responsive sites: no action needed, a single URL = no canonical issues
• Mobile-first indexing: the mobile version is crawled first, but the canonical can point to desktop if distinct URLs exist
• Signal consolidation: all ranking metrics accumulate on the canonical URL (desktop), not on the mobile variant
• SERP display: Google may display the mobile URL to smartphone users even if the desktop is indexed

Is this recommendation consistent with real-world observations?

Let's be honest: this directive from Mueller dates back to a time when separate mobile URLs were still common. Nowadays, the majority of professional sites are responsive. Maintaining two separate URLs has become an anti-pattern that Google actively discourages.

In practice, sites with m.example.com that properly apply this canonical mobile→desktop usually do not encounter major issues. However, maintenance complexity is real: cross alternate/canonical annotations, risk of loops, frequent configuration errors. SEO audits regularly reveal sites where this mechanism is broken, creating unintended duplication.

In what cases does this rule not apply?

If you have a responsive site (99% of cases today), forget this whole canonical mobile→desktop story. It simply does not apply to you. A single URL = no canonical to manage for mobile.

Furthermore, if you have separate URLs but the mobile version is richer or different in content, pointing to desktop via canonical can dilute relevance. Google will index the desktop, but if your mobile strategy is independent, you lose this granularity. [To be verified]: Google does not publish any data on the real impact of this configuration on mobile ranking in edge cases such as progressive web apps or mobile-only experiences.

What nuances should be added to this directive?

Mueller does not clarify how this recommendation aligns with the widespread mobile-first indexing. If Google crawls primarily the mobile version, but the mobile points in canonical to desktop, which version does it actually evaluate for ranking? The official documentation remains unclear.

In practice, Google appears to use the mobile content for initial indexing, then consolidate signals towards the canonical desktop URL. But no official case studies confirm this with supporting data. Inconsistencies are also noted: sites where Search Console indicates mobile-first is active, but ranking fluctuations suggest that Google still partially evaluates the desktop.

What should I do if I have separate mobile URLs?

First step: audit your current configuration. Verify that each mobile page (m.example.com/page) contains a <link rel="canonical" href="https://www.example.com/page" /> pointing to the desktop version. Simultaneously, the desktop version should contain <link rel="alternate" media="only screen and (max-width: 640px)" href="https://m.example.com/page" />.

Next, test with the URL Inspection tool in Search Console. Request indexing of a mobile page, then check that Google correctly identifies the canonical desktop. If Google ignores the canonical, it is often a consistency issue between mobile and desktop (content too divergent, intermediate redirects).

What errors should be avoided in this configuration?

The classic mistake: canonical loops. Mobile points to desktop, but desktop also points to another URL (www vs non-www, HTTP vs HTTPS). Google then abandons resolution and indexes what it wants, often duplicating.

Another common trap: canonical mobile→desktop, but mobile content is limited. If your mobile version hides entire sections (unexpanded accordions, content hidden in CSS), Google crawls the sparse mobile, indexes the desktop, and may consider there is inconsistency. Result: loss of ranking on certain queries.

How to migrate to a responsive site if I still have separate URLs?

If you are maintaining m.example.com only for legacy reasons, migration to responsive is the true solution. Plan a 301 migration of all the mobile URLs to their desktop equivalents, then implement a responsive design. Google follows the 301s, consolidates signals, and you eliminate all maintenance complexity.

During migration, monitor Search Console closely. 404 errors on old mobile URLs, unresolved canonicals, and crawl drops are frequent. Prepare a rollback plan if mobile traffic drops by more than 15% within 48 hours of deployment.

• Audit all mobile pages: presence and correct target of rel=canonical pointing to desktop
• Check for symmetry in annotations: desktop must contain rel=alternate pointing to mobile
• Test with Search Console Inspection: Google must identify the canonical desktop on mobile pages
• Eliminate canonical loops: one final canonical URL, no chain of redirects
• Ensure parity of mobile/desktop content: no important sections hidden on mobile
• Plan a responsive migration if possible: eliminating separate URLs remains the best long-term option