Which canonical should a page in an hreflang cluster use?

Definition: For a page that uses hreflang, Google recommends a canonical URL in the same language as that page. If no canonical page exists in that language, Google recommends the best possible substitute language.

Key facts

• Google's canonicalization documentation gives the same-language recommendation for pages using hreflang.
• Google describes rel="canonical" as a strong signal that the specified URL should become canonical, while sitemap inclusion is a weaker signal in its comparison of canonicalization methods.
• Google's localized-versions documentation says that each language version lists itself and every other language version.
• Alternate URLs in the cluster must be fully qualified, including http or https, according to the same localized-versions guidance.
• If two pages do not point to each other, Google says the hreflang tags are ignored, as described in the reciprocal-link guideline.

What does the same-language recommendation mean?

Google's canonicalization documentation says that an hreflang implementation should specify a canonical page in the same language, or the best possible substitute language when a same-language canonical does not exist. The choice is therefore made for each localized page. A German page points to a German canonical when that version exists, while an English page points to an English canonical.

The canonical link identifies the representative URL for duplicate or very similar pages. Google describes rel="canonical" as a strong signal, and recommends a self-referential canonical link on the canonical page itself. A translated page can therefore carry a canonical URL for its own language while its hreflang annotations identify the other language and regional versions.

How does canonicalization work with hreflang?

Google's localized-versions documentation describes hreflang as a way to identify localized variations of the same content. It also states that Google determines a page's language with algorithms instead of using the hreflang value or the HTML lang attribute as the detector.

The two signals have different jobs in this setup. The canonical element gives Google a preferred representative URL for the page. The hreflang set connects the localized URLs so Google can match a page variation to a language or region. Each version includes the complete set, including its own URL. A pair of pages must point to each other for the annotation to be processed.

What should the page markup contain?

Google's canonical example places a rel="canonical" link in the HTML head and recommends the same self-referential element on the canonical page:

<html>
<head>
<title>Explore the world of dresses</title>
<link rel="canonical" href="https://example.com/dresses/green-dresses" />
<!-- other elements -->
</head>
<!-- rest of the HTML -->

The localized-versions example puts the same alternate set in the head of each regional page:

<head>
 <title>Widgets, Inc</title>
  <link rel="alternate" hreflang="en-GB"
       href="https://en-gb.example.com/page.html" />
  <link rel="alternate" hreflang="en-US"
       href="https://en-us.example.com/page.html" />
  <link rel="alternate" hreflang="en"
       href="https://en.example.com/page.html" />
  <link rel="alternate" hreflang="de"
       href="https://de.example.com/page.html" />
 <link rel="alternate" hreflang="x-default"
       href="https://www.example.com/" />
</head>

Google documents three equivalent ways to declare localized versions: HTML links, HTTP headers, and XML sitemaps. The HTML form is useful when the site can edit the page head; the HTTP form also supports non-HTML files such as PDFs.

How can a team check the cluster?

Start with the canonical URL on each language page. Confirm that its language matches the page, then check the head for one hreflang link to every variant, including the current URL. Confirm that every href is an absolute URL with its transport method and that each pair of language pages points in both directions.

For several regional pages in one language, Google's guidance gives en-IE, en-CA, and en-AU as examples and recommends a generic en page for geographically unspecified English-language users. A language or country selector can use x-default as its fallback URL. These checks apply whether the annotations are delivered in HTML, an HTTP header, or a sitemap.

Related terms

• Canonical URL
• hreflang
• Should translated pages have separate URLs?

FAQ

Should every translated page canonicalize to the default language?

No. Google recommends a canonical in the page's same language when one exists. The best possible substitute language is used when that same-language canonical is unavailable.

Should the canonical URL also appear in hreflang?

Yes. Google says each language version must list itself as well as the other language versions. The self URL belongs in the hreflang set even when the page also has a self-referential canonical.

What if one translation omits a return link?

Google says the tags are ignored when two pages do not point to each other. The localized-versions guidance also says Google can process the pairs that do point to each other when a complete set is difficult to maintain.

Sources

1. Google Search Central, "How to specify a canonical URL with rel="canonical" and other methods", 10 July 2026
2. Google Search Central, "Tell Google about localized versions of your page", 21 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer