Should you duplicate hreflang tags for mobile and desktop versions?

Why does Google favor desktop URLs in hreflang tags?

The reasoning behind this recommendation revolves around the principle of mobile-first indexing. Since switching to this mobile-first indexing, Google considers the mobile version as the reference but maintains a unified approach for international signals.

The hreflang tags serve to indicate relationships between language versions of the same page. By instructing to point to the canonical desktop URLs, Google avoids the complexity of a dual hreflang linking (one for mobile, one for desktop) which would create redundancy and configuration error risks.

Does this directive apply only to sites with separate mobile URLs?

This question arises mainly for architectures with distinct mobile subdomains (m.example.com) or dedicated directories (/mobile/). For responsive sites with identical URLs across all devices, this issue does not arise: there is only one URL, hence only one hreflang implementation.

On configurations with separate URLs, the temptation is to create hreflang annotations pointing to m.example.fr, m.example.de, etc. Google discourages this approach and advises directing the tags from the mobile version to the desktop equivalents (www.example.fr, www.example.de).

What is the relationship between hreflang and canonical in this context?

The canonical and hreflang tags address two distinct but complementary issues. The canonical tag indicates which version of a page (mobile or desktop) is the reference for a given language. The hreflang tag establishes links between language versions.

On a mobile page m.example.com/page, you should have a canonical pointing to www.example.com/page (the reference desktop version) AND hreflang tags pointing to www.example.fr/page, www.example.de/page, etc. These two types of tags coexist without conflict and serve orthogonal functions.

• Hreflang tags should point to the canonical desktop URLs, even from a mobile page
• This configuration primarily applies to sites with distinct mobile URLs (subdomains or dedicated directories)
• Responsive sites with unique URLs only have one hreflang implementation to manage
• The canonical tag and hreflang tags work together without substituting for each other
• This approach simplifies maintenance and reduces international configuration errors

Is this recommendation consistent with on-the-ground observations?

On paper, Google's directive indeed simplifies management. In practice, it raises questions for sites that have migrated to mobile-first without removing their separate mobile URLs. Some historical sites still maintain m.example.com architectures for technical or internal political reasons.

Tests show that Google generally tolerates configurations with hreflang pointing to mobile URLs, as long as reciprocity is respected and the canonical signals are coherent. However, adhering to the official recommendation removes any ambiguity for the crawler. [To be verified]: the actual impact on international ranking when hreflang points to mobile URLs instead of desktop ones remains difficult to quantify precisely.

What are the practical limitations of this approach?

The main limitation concerns sites with substantially different content between mobile and desktop. If your mobile version displays a simplified product page while the desktop version offers enriched content, pointing to the desktop via hreflang can create a dissonance between what Google indexes (the mobile version) and what the international tags describe.

In this scenario, logic dictates that hreflang should reflect the URLs actually indexed. Google does not provide clear guidance for these edge cases. My approach: prioritize absolute consistency between mobile and desktop versions, thus eliminating the problem at the source. If this harmonization is impossible, precisely documenting implementation choices becomes critical.

Are there configurations where this rule does not apply?

For sites that have completely abandoned their separate mobile URLs in favor of a responsive design, the question becomes moot. Similarly, sites using dynamic serving (same URL, different HTML based on user-agent) only have one URL to reference in hreflang tags.

The specific case of mobile applications deserves attention. App indexing tags and deep links use different mechanisms. Hreflang remains in the web domain and does not directly apply to native apps. If you offer an app + web experience, hreflang only concerns the canonical web URLs.

What should you check about your current configuration?

First diagnosis: identify your mobile architecture. Responsive site, mobile subdomain, or dedicated directory? For responsive sites, you only have one hreflang implementation to manage. For separate URLs, audit all mobile pages to ensure their hreflang tags point to the desktop equivalents.

Use Google Search Console to identify existing hreflang errors. Internationalization reports indicate reciprocity issues, unreachable URLs, and conflicts. Cross-reference this data with a filtered Screaming Frog or Oncrawl crawl on mobile pages for a comprehensive view.

How to correct a hreflang configuration pointing to mobile URLs?

If your current hreflang tags point to m.example.fr, m.example.de, etc., plan a gradual correction. Start with the priority templates: homepage, main categories, best-selling product pages. Modify the tags to reference www.example.fr, www.example.de.

Test on a limited sample before global deployment. Monitor Search Console for 2-3 weeks to detect any regression in international impressions. If your mobile pages generate direct organic traffic (users typing the m.example.com URL), ensure that 301 redirects to the desktop versions are in place and functioning.

What mistakes should be avoided during implementation?

The classic mistake: mixing references in hreflang tags, some pointing to mobile, others to desktop. This inconsistency confuses Google and dilutes international signals. Adopt a strict rule: all hreflang tags point to canonical desktop URLs, without exception.

Another common pitfall: forgetting about reciprocity. If www.example.com/page declares a French version www.example.fr/page, the latter must reciprocally declare the English version. Hreflang validation tools (like the Merkle validator) detect these breaks in reciprocity. Also, do not neglect the x-default tag that indicates the default version for users outside geographic targeting.

• Audit your current mobile architecture (responsive, subdomain, dedicated directory)
• Verify that all hreflang tags from mobile pages point to the canonical desktop URLs
• Check the reciprocity of hreflang annotations across all language versions
• Test the configuration on a sample before global deployment
• Monitor Search Console for 2-3 weeks post-modification to detect anomalies
• Document the implementation logic to facilitate future maintenance