Indexation
Part of International and multilingual SEO
Checking canonical signals across language variants
Check canonical preferences and Google’s selected URLs across translated and same-language regional pages without confusing them with hreflang.
Check which URL should represent each page's content in Google Search. Then check the separate hreflang map of language or regional alternatives.
A translated page does not need to point its canonical annotation to the source-language URL merely because it was translated from it.
Classify the page relationship
Record important locale URLs, their main-content language, intended region and preferred representative. Classify these cases before changing a tag.
| Relationship | Canonical question |
|---|---|
| Main content is translated into another language | Does each language page have its own intended, accurate URL? |
| Regional pages share a language and have very similar main content | Which URL should be preferred, and how will regional alternatives be identified? |
| A parameter, host or other technical variant repeats a page | Which one URL should represent that duplicate? |
Google considers language versions duplicates only when their primary content remains in the same language, such as when only the template changes. Same-language regional pages require closer canonical review. Similarity does not automatically mean every regional page should be removed or redirected.
Compare the actual signals
For each sampled URL, follow redirects to its final address. Inspect the canonical annotation in the delivered HTML or response, then compare it with the intended URL.
A page intended as its own representative can declare itself canonical. A technical duplicate can point to the preferred page.
Compare sitemap entries and internal destinations for conflicting preferences.
Google treats redirects and canonical annotations as strong signals and sitemap inclusion as weaker. These express preferences; Google can still select another canonical. Do not use noindex merely to steer that selection, because it blocks the page from Search when Google can read it.
Inspect the hreflang set. Its URLs should identify corresponding locale pages at their final addresses.
For regional variants in the same language, Google recommends using canonicalisation and hreflang together to help Google understand which regional URL to show in search results.
Investigate a mismatch
In a Search Console property you control, the URL Inspection tool can show which page Google considers canonical.
If the selected URL is unexpected, compare content and signals before editing. A CMS template could point every locale to one URL; a redirect could replace a version; or very similar regional pages could be grouped. Treat these as causes to investigate, not conclusions from a tag alone.
Record the intended relationship, observed signals and proposed correction for each pair. After a change, recheck the delivered pages, then allow time for Google to process them. The immediate check is whether readers can reach the intended local answers and the site sends consistent signals.
