Check language, region, and equivalent page versions

Explanation

Each language version should be a separate page with content in that language. Google recommends separate URLs for language versions and hreflang links between equivalent pages; the language is better identified by visible content rather than relying only on the lang attribute. Localization signals do not replace translation and do not guarantee that every user will see the desired URL.

Fictional example

https://learn.example.test/ru/robots is one language version of the same training page. In this exercise, its switcher leads to the wrong equivalent URL, and its form has a field label in another language plus a contact example that does not match that page’s region. These are localization defects. The team compares the language versions, corrects the interface and equivalent-page mapping on staging, then checks lang, canonical, and reciprocal hreflang links. All contact details remain synthetic.

Practice

On staging or a local mockup, make a matrix for the two versions of the same page, /robots and /ru/robots: language of the heading, text, buttons, and form; synthetic contact details; equivalent URL in the switcher; lang; canonical; and hreflang. Do not publish changes or submit the fictional URLs to external tools.

Checklist

• Headings, text, navigation, forms, errors, and footer use the selected language.
• Phone numbers, addresses, and examples fit the page’s region or are marked as fictional.
• The switcher leads to an equivalent page if one exists and explains its behavior.
• The hreflang set is reciprocal and does not point to missing versions.
• Each language version’s canonical agrees with its URL.

Common mistake

Adding hreflang while leaving half the interface in another language or pointing every language to one canonical page. Metadata does not fix the content.

Primary sources

• Managing multi-regional and multilingual sites
• Localized versions of pages and hreflang