Hreflang connects localized versions of a page. A canonical tag identifies a preferred URL when duplicate or substantially similar URLs need consolidation. You can use both on the same page, but they should support the same publishing plan.
Decide which URLs deserve separate localized search results before generating either tag. A tool can format an address; it cannot decide whether two pages represent useful regional alternatives or ordinary duplicates.
Start with the relationship between the pages
Page relationship
Decision to investigate
English page and a complete French translation
Keep suitable preferred URLs for each language and connect them as alternatives
UK and US pages with meaningful market differences
Assess separate localized URLs and compatible canonical signals
Tracking URL and clean URL for the same audience
Consolidate duplicate signals toward the preferred URL
Substantially identical regional pages in one language
Review Google's regional duplicate guidance before selecting canonicals
A French translation is not merely a tracking variation of an English page. Conversely, adding a country label to an ordinary duplicate does not automatically justify another indexable page.
Use compatible markup for translated pages
Suppose English and French support pages are intended to remain available as separate localized results. The English page can use:
<link rel="canonical"
href="https://example.com/en/support/">
<link rel="alternate" hreflang="en"
href="https://example.com/en/support/">
<link rel="alternate" hreflang="fr"
href="https://example.com/fr/assistance/">
The French page can use:
<link rel="canonical"
href="https://example.com/fr/assistance/">
<link rel="alternate" hreflang="en"
href="https://example.com/en/support/">
<link rel="alternate" hreflang="fr"
href="https://example.com/fr/assistance/">
Here, the canonical changes with the page, while the alternate list remains the same. Each translation identifies its preferred URL and acknowledges the other language version.
Recognize a cross language canonical conflict
If the French page instead declares the English URL as canonical, it asks for consolidation toward English while its hreflang entry identifies French as an alternative. That is inconsistent with the stated goal of maintaining separately indexed translations.
Investigate how the incorrect canonical was generated. A shared template may have hard-coded the English address, a translation plugin may have inherited it, or an SEO setting may override the expected output. Correct the source of the error so the next update does not restore it.
Avoid changing tags repeatedly based on one search result. Canonicals are signals, and Google may choose a different canonical from the one declared. Check the indexed URL and the Google-selected canonical in Search Console's URL Inspection data before deciding what happened.
Treat regional duplicates as a separate decision
Regional pages written in the same language can be more complicated than translations. Pages with distinct delivery terms, availability or pricing may serve different market needs. Pages with almost identical content may require a preferred canonical alongside the regional annotations.
Google's multi-regional guidance discusses canonicalization and hreflang together for same-language regional duplicates. Do not turn the translated-page example above into a universal rule that every regional URL must self-canonicalize.
Record the intended outcome for each URL: separate localized result, consolidated duplicate, or retired address. Then check that canonicals, internal links, redirects and sitemap entries support that outcome.
Resolve the underlying signals together
Review one representative group before changing a sitewide template. Compare the declared canonical on each page with its actual destination, the alternate list and the indexing state. Include redirects and non-indexable variants in the investigation so an old URL does not remain in the hreflang group unnoticed.
When the pattern is correct, extend it through the CMS and check another sample. The Degates hreflang guide explains the wider implementation; use this decision process to keep canonical selection aligned with the localized pages you actually want people to find.

Leave a Reply