Check multilingual hreflang: equivalent pages, return links and canonicals

Separate language, region and page equivalence

A language version changes the language of the content. A regional version addresses a particular market, which may use the same language as another market. A page relationship says which URLs provide corresponding versions of the same subject or task.

Google’s multilingual-site guidance recommends different URLs for different language versions, a clear language on each page and links that let people choose another version. Google determines page language from content rather than relying on the URL or an HTML language declaration alone.

Suppose a fictional bicycle workshop has an English maintenance guide and its French translation. Those pages form one candidate pair. Its French booking page is not the alternate for the English maintenance guide simply because both discuss bicycles.

Open each proposed counterpart and compare the purpose, central content and visitor action. Local contact details or examples may differ without changing the underlying task. If the supposed translation is a short placeholder, unrelated category or generic homepage, resolve the content mapping before adding a relationship.

Check supported codes and the returned annotation set

Google’s localized-version documentation supports HTML head links, HTTP Link headers or XML sitemap annotations; the methods are equivalent for Google, so one maintainable method is sufficient. Use fully qualified URLs and include each version itself. Corresponding versions need return links.

Use language codes deliberately: en is English, while en-GB targets English for the UK. A region alone is invalid; UK and EU are not supported region identifiers for this purpose. x-default identifies a fallback for languages not explicitly matched, rather than naming another language.

Read the actual output used by the site. For HTML, inspect the public head; for a header implementation, inspect the response; for a sitemap implementation, inspect the relevant sitemap entries. Do not diagnose an absent head tag as a failure before establishing which method is intended.

For the fictional guide pair, compare the English and French records side by side. Each should describe the same intended pair, including itself. A one-way reference from English to French leaves the relationship incomplete. Record unexpected URLs exactly so the responsible component can be identified.

A site can use more than one method, but maintaining parallel hand-edited lists creates more opportunities for disagreement. Identify the translation system or integration that owns the mapping, and correct that source rather than adding a second list over the first.

Keep hreflang and canonical decisions consistent

Hreflang describes localized alternatives. Canonical signals indicate a preferred URL among duplicate or very similar versions. They do not perform the same job.

Google’s canonical guidance recommends a canonical in the same language when using hreflang, or the best substitute where that language has no canonical. It also recommends self-referential canonicals on canonical pages and consistent sitemap and internal-link signals. Google can still select a different canonical.

For a genuinely translated French guide with its own preferred URL, a canonical pointing to the English original deserves investigation. Do not automatically rewrite every canonical: first establish whether the French address is a duplicate alias of another French URL or whether a template has incorrectly copied the original language’s value.

Regional pages with substantially similar content in the same language need a considered canonical policy. Google’s multilingual guidance explicitly discusses combining canonical and hreflang for those duplicates. A blanket rule that every region must always be self-canonical would ignore that case.

Check hostname and HTTPS consistency too. The www and canonical-address guide covers the underlying address choice. Language annotations should not conceal a separate hostname or redirect error.

Open every destination and check its intended access

Visit the candidate URLs without an administrator session and record the final address and content. A link can have a plausible language path while redirecting to the original language, showing a sign-in screen or returning a missing-page message.

Investigate the access issue before treating the annotation as verified. Use the broken-link audit workflow to distinguish an absent destination from a temporary or restricted response. Update the mapping when a real page moves; do not replace every missing translation with the homepage.

Inspect indexing restrictions on versions intended to be public. Google’s noindex documentation explains that noindex prevents indexing and that Google must be able to crawl a page to see the directive. Hreflang is not permission to index a deliberately excluded page.

Keep private staging and unpublished translations protected. Test their mapping locally or in the protected review environment; do not remove privacy controls just to make an external tool report a clean result. Public-launch eligibility is a separate decision.

Test the visitor’s language choice

From the English guide, use the visible language switcher and check that it opens the French guide. Return to English and confirm the reverse trip. Then open each address directly in a fresh session. Record whether the chosen version remains available without requiring a particular cookie or administrator state.

Google’s link guidance identifies ordinary anchor elements with href destinations as crawlable links. Check the actual destination behind a flag or language name rather than relying on its appearance.

When no counterpart exists, use an honest visitor route: for example, explain that the article is available only in English and offer navigation to the French section. Do not make the menu imply a French translation exists when it leads to unrelated content.

Also inspect the page’s HTML language. W3C’s language-declaration guidance describes setting lang on the html element and marking changes of language where appropriate. That helps software interpret the text; it is separate from mapping alternate URLs for Search.

Read Search Console evidence with its date attached

For a public page in an authorised property, inspect the exact URL. The URL Inspection guide distinguishes indexed data from a live test and exposes the user-declared and Google-selected canonical. The live test cannot predict Google’s eventual canonical choice.

Compare the recorded crawl time with the correction time. If Google last crawled the earlier implementation, an old report does not establish that the current output is still wrong. Conversely, correct current markup does not prove Google has processed or indexed it.

Keep the evidence page-specific: URL, expected relationship, current output, crawl time and observed canonical. “The multilingual site is fixed” is too broad when only its homepage was checked. No tool screenshot guarantees future language selection or rankings.