Why is Google ignoring your hreflang canonical, and how can you fix it?

How does Google determine the canonical version of a hreflang page?

Google doesn’t just read your canonical tags and apply them blindly. It analyzes all available signals: redirects, internal links, XML sitemaps, and especially the hreflang annotations themselves. When multiple language versions exist, the engine evaluates which one it finds most relevant for indexing reference.

The problem arises when your canonical declaration points to one URL, but Google favors another. Typically, you indicate that the French version is canonical, but Google decides that the English version is authoritative. The result: the wrong version appears in the French SERPs, sometimes showing English content to French-speaking users.

What's the difference between the declared canonical and the indexed canonical?

Your declared canonical is the one you specified via the <link rel="canonical"> tag or the corresponding HTTP header. It's your intention, your recommendation to Google. The indexed canonical is the one that Google has actually retained after cross-checking all its signals.

Mueller highlights here that this divergence is the root of display issues with hreflang. If you find that a wrong version appears in search results, it’s generally because Google has ignored your directive and chosen a different canonical. The verification is done through the URL Inspection Tool in Search Console, which explicitly displays the canonical retained by Google.

What signals may conflict with your canonical directives?

Several factors can lead Google to diverge from your choice. 302 redirects to another language, massive internal links pointing to one version over another, or poorly symmetrical hreflang annotations create ambiguities. Google then arbitrates according to its own logic, not necessarily yours.

Sitemaps also play a role: if you list a URL as canonical in your sitemap but the page itself points to another URL, Google must decide. The same goes if your hreflang tags are not reciprocal: the French version declares a link to the English version, but the reverse is not configured. These inconsistencies force Google to make an algorithmic choice, which is often unpredictable.

• Check the indexed canonical via the URL Inspection Tool in Search Console, not just the source code of your page
• Ensure complete symmetry of hreflang annotations across all language versions
• Avoid 302 redirects to other languages that suggest a canonical different from the declared one
• Align sitemap, internal links, and canonical tags to the same reference URL for each language cluster
• Test with a sample of representative URLs before deploying a large-scale hreflang structure

Is this statement consistent with real-world observations?

Absolutely. The divergences between declared canonical and indexed canonical are among the most frequent causes of hreflang malfunctions. Practitioners regularly notice that Google favors an unexpected language version, especially when the site presents conflicting signals. Mueller reveals nothing new here but emphasizes a reality often overlooked: checking the source code is not sufficient.

The weak point of this statement? It remains vague on which signals exactly tip the balance when multiple canonicals are in competition. Google does not publish a clear priority grid. It is empirically known that redirects and internal links carry significant weight, but it’s impossible to quantify their relative importance. [To verify]: how does Google arbitrate when hreflang, canonical, and sitemap all contradict each other? No official documentation details this decision tree.

What nuances should be added to this recommendation?

Mueller suggests correcting the declared canonical to match the one Google uses. But sometimes, it’s Google that is wrong. If your architecture is correct—symmetric annotations, no stray redirects, aligned sitemap—and Google continues to choose the wrong canonical, forcing alignment amounts to validating an algorithmic error.

In such cases, the solution is not to bend your structure to Google's will, but to identify and eliminate the ambiguous signal that misleads it. Typically, this might be a huge internal link to a deprecated version, a forgotten 301 redirect in a corner of the site, or an orphan hreflang tag on a satellite page. The diagnosis requires a comprehensive audit, not just a simple tag check.

When does this rule not apply?

If your multilingual pages are on separate domains (e.g., .fr, .de, .co.uk), canonicalization conflicts are less common. Each domain has its own natural canonical, and hreflang merely links linguistic equivalents without creating ambiguity. Problems mainly arise with subfolders (/fr/, /de/) or subdomains (fr.site.com, de.site.com) on the same root domain.

Another specific case: sites with partially translated content. If your French version has only 60% of the pages of the English version, hreflang becomes a puzzle. Some English URLs have no French equivalent, resulting in no hreflang tag. Google must then decide whether to display the English version to French speakers or nothing at all. In this context, canonical directives become even more important but remain fragile against conflicting signals.

How can you check which canonical Google has actually retained?

Open the Search Console, select the relevant property, and then use the URL Inspection Tool. Enter the URL of a language version (for example, your /fr/produit page). In the indexed page details, Google explicitly displays the canonical it has chosen. If this canonical differs from the one you declared in your code, you have identified the conflict.

Repeat this operation for a representative sample of pages in each language. Divergences are not always systematic: some pages may have the correct canonical while others do not. Document the discrepancies in a spreadsheet to identify patterns (for example, all pages of a specific category are affected).

What corrections should be applied once the conflict is identified?

Start by harmonizing your canonical tags: each language version should point to itself as canonical unless you are deliberately consolidating multiple URLs. Then, check that your hreflang annotations are perfectly symmetrical: if /fr/produit declares /en/product as the English equivalent, then /en/product must declare /fr/produit as the French equivalent.

Eliminate 302 redirects between language versions. If you need to redirect (for example, due to geographical detection), use 301 redirects only for definitive consolidations, never for language routing. Prefer a language selector without automatic redirection. Finally, ensure that your XML sitemap lists only canonical URLs, and that these match exactly your declared canonical tags.

What should you do if Google continues to ignore your directives?

Audit your internal links. A massive volume of links pointing to one language version over another may convince Google that this version is the reference, regardless of your tags. Use a crawler (Screaming Frog, Oncrawl) to map the internal link structure and identify imbalances. If 80% of your internal links point to /en/ while you want to canonicalize /fr/, Google will follow the links, not your tags.

Also check external backlinks. If the majority of incoming links point to a specific language version, Google might favor it as canonical. You cannot control these links, but knowing their distribution helps you understand Google's choices. In some cases, you must accept that the most linked version effectively becomes the canonical, and adjust your structure accordingly.

• Inspect in Search Console a sample of URLs from each language version to compare declared canonical and indexed canonical
• Harmonize canonical tags: each version points to itself unless voluntarily consolidated
• Check the complete symmetry of hreflang annotations between all language pairs
• Remove all 302 redirects between language versions, keeping only 301 for definitive consolidations
• Align the XML sitemap: list only canonical URLs, not variants
• Crawl the site to identify internal link structure imbalances between language versions