Study first
Review the ideas behind the questions
Review the launch checks that keep localized pages clear. Focus on whether each audience can reach the right language or region page, and whether the page signals match what readers actually see.
Separate language and region versions
Localized content work starts by knowing whether the site is serving different languages, different regions, or both.
- A multilingual site offers content in more than one language.
- A multi-regional site explicitly targets users in different countries or regions.
- Use different URLs for different language versions instead of changing the language on one URL with cookies or browser settings.
In Practice
Name the audience split first
Before drafting, decide whether the page changes because of language, country, region, currency, product availability, or a mix of those needs.
Keep one page from doing every locale job
If the same URL changes language silently, a reader may share one page while another reader sees a different version.
Common mistakes
Treating translation and country targeting as the same planning decision.
First decide whether the content changes by language, by region, or by both, then choose URLs and signals that match that split.
Q&A
Can one site be both multilingual and multi-regional?
Yes. A site can have language versions and country or region versions when both audience needs exist.
Why avoid changing the language only with browser settings?
A separate URL for each language version gives users and search systems a clearer page to reach and reference.
Make switching and targeting explicit
Readers should not be trapped on a guessed locale page. Search systems also need explicit signals instead of hidden location logic.
- If a page has multiple language versions, language or region annotations can help Google point users to the most appropriate version.
- Automatic redirects based on guessed language can prevent users and search engines from viewing all versions.
- Explicit links can let users choose a different region or language when the first page is not right for them.
In Practice
Do not hide the other version
A language switch link is useful because it gives control back to the reader when the guessed version is wrong.
Mark alternates for the actual variants
When the main content is translated or region-specific, the alternate signal should describe that real language or region difference.
Common mistakes
Redirecting every visitor to a guessed locale and removing links to other versions.
Offer visible links to other language or region versions so users and search engines can reach them.
Q&A
Does Google always need alternate-page signals to find translated pages?
No. It might find alternates without them, but explicit language or region signals are usually the better setup.
Keep language signals honest
Technical signals work best when they describe the page a reader can actually see. A localization quality check should catch mixed-language pages, weak URL choices, and duplicate regional pages.
- Google uses visible page content to determine language, so the content and navigation should make the language clear.
- The HTML language declaration identifies the default language of the page for tools that process the page.
- For similar same-language regional pages, choose a preferred version and use canonical plus alternate signals together.
In Practice
Do not make code fight the page
If the page says one thing in visible copy and another thing in metadata, fix the visible page and the supporting signal together.
Avoid parameter-only locale plans
A locale in a query parameter is harder for users to recognize and is not Google's recommended URL structure for geotargeting.
Common mistakes
Assuming the page-language code alone fixes mixed-language visible content.
Make the visible content and navigation language clear, then use the HTML language declaration for page-language metadata.
Q&A
Does the HTML language declaration replace visible language clarity?
No. It helps tools process the page language, but Google Search still looks at visible page content to determine language.