301 chain301 chain
Permanent redirects stacked one after another.
Found by Redirect checker →
302302
A temporary redirect on a page that moved for good.
Found by Redirect checker →
Technical SEOUpdated

Multilingual SEO

In short

Multilingual SEO makes equivalent content available in each reader’s language with distinct accessible URLs and annotations that help search engines understand language and regional variants.

Multilingual SEO makes equivalent content available in each reader’s language with distinct accessible URLs and annotations that help search engines understand language and regional variants.

Illustration of the mechanism discussed in Multilingual SEO.

Model language before markup

A multilingual site starts with a content decision: which languages and regional variants receive a real maintained version, and which page is the equivalent of which. A translated navigation label is not a language version. Each version needs content that answers the same task for its audience, including local terminology, currency, delivery limits or legal wording where those facts change.

Give every version a stable URL. Common patterns include country domains, subdomains or subdirectories; the architecture choice matters less than direct access and consistent internal links. Avoid changing the page solely from browser language without leaving the selected URL available.

Build reciprocal alternates

Use hreflang annotations for genuinely equivalent pages. Each member of the set should name itself and the other alternatives; an x-default can identify a suitable fallback where one exists. Hreflang is an annotation, not a redirect and not a substitute for a canonical tag. Canonicalise each version to itself unless there is a separate duplicate reason.

Example: an English product guide and its Spanish equivalent can reference each other when both explain the same product and audience task. An English page about a UK-only service and a Spanish global explainer may not be true alternates, even if they share a template.

Test a set, not one page

Create a small matrix with each locale URL, its declared language and region, canonical, reciprocal annotations and default behaviour. Fetch each route directly, including with a crawler user agent, and inspect the final HTML. Check that switcher links point straight to the alternative rather than through a geolocation redirect.

Then test the reader path: open a saved link, choose another language, refresh, return on a new visit and use a mobile viewport. The selected locale should remain usable even when a country or language inference is wrong. Keep translation coverage and release state explicit.

Operational limits

Do not assume hreflang guarantees a particular country ranking or that automatic translation is enough to make a page useful. Search engines can choose a different result based on their signals. The controllable work is accurate content, accessible URLs, coherent links, reciprocal annotations and ongoing checks when pages are added or retired.

FAQ

No. It identifies language or regional alternatives; each destination still needs suitable content.
No. Distinct translated pages normally need their own preferred URLs. Review genuine duplicates separately.