Multilingual sites and hreflang
Four address structures are documented for a site targeting several countries, and each is presented with its trade-offs rather than recommended. Two practices are, however, explicitly discouraged: adapting content based on IP address analysis, and automatically redirecting a visitor from one language version to another.
Two questions people take for one
A site in several languages and a site targeting several countries are two distinct problems. Language is a property of the content; the country targeted is a commercial intention. You can have one without the other — a single-language site targeting two countries, a three-language site targeting the whole world — and the documentation handles both in the same document precisely because they get confused.
The practical consequence: decide first whether you are targeting countries, then how you file the languages. Choosing the address structure first means settling the first question without noticing you asked it.
The four structures, with their trade-offs
Four address structures are presented with their trade-offs: a domain per country, a subdomain, a subdirectory, and a URL parameter — the last of which is discouraged.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
What is notable here is that no general recommendation is given for the first three: they are presented with advantages and drawbacks, which is the shape of a trade-off and not of an instruction. A source claiming there is one absolutely best structure would therefore contradict its own reference document.
A domain per country offers clear geographic targeting and makes the server location irrelevant, at the cost of higher expense and being limited to a single targeted country.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
A subdirectory is easy to set up and cheap to maintain since it shares the host, but it implies a single server location and makes separating the sites harder.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
Two sentences are enough to see the real choice: a domain per country buys clarity and pays in cost and rigidity; a subdirectory buys simplicity and pays in separation. The subdomain sits in between, with a drawback stated from the reader’s point of view — geographic targeting is not recognisable from the address alone. Only the URL parameter is explicitly discouraged.
Filing languages as subdirectories on a single domain
hypothesis
- Effort
- moderate
- Time to effect
- weeks
- Risk
- low
- Durability
- lasting
The one place where the documentation plainly says no
Twice, and on the same subject: automatic detection.
The documentation asks that IP address analysis not be used to adapt content: such analysis is difficult and generally unreliable, and the engine may be unable to crawl the site's variants properly.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
It asks that automatically redirecting visitors from one language version to another be avoided, since it could stop them, and the engines, from seeing all versions of the site.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
Those two sentences are worth knowing, because they condemn the most requested feature in every multilingual project: “detect the visitor’s language and send them to the right version”. The reason given is not even primarily technical — it is that the visitor, like the engine, ends up prevented from seeing the other versions. An automatic redirect does not provide a service, it removes a choice.
The replacement is trivial and is visible on this very site: a language selector present on every page, pointing at the equivalent version. The reader chooses; both versions stay reachable; the engine can crawl both. Nobody loses, and that is rare.

Declaring the versions to one another
Every page must declare all its alternate versions, including itself.
officialSource : Google Search Central, “Tell Google about localized versions of your page”
“Including itself” is the part that gets forgotten, and forgetting it breaks the reciprocity of the declaration: a page announcing its neighbours without announcing itself leaves an incomplete arrangement, where each version describes a different set. The practical rule that follows is easy to check: the declarations of all versions of the same page must be identical to one another.
Two common errors come down to the same failure of reciprocity. A version declaring a twin that does not declare it back does not form a pair. And a declaration pointing at an address that redirects or does not exist names no version at all: it names an intention.
For content that is similar from one region to another, the documentation points to the canonical and the language annotations so that the right regional or language version reaches the reader.
officialSource : Google Search Central, “Managing multi-regional and multilingual sites”
In other words, two close regional variants are not a fault to make disappear: it is a foreseen case, to be declared properly. What remains to be settled is editorial — do two versions differing only by a currency and a phone number deserve to be two pages? That question is not the engine’s, it is the reader’s.
What does not work
Detect the browser language or the visitor's country, and redirect them automatically to the matching version: it is the best possible experience.
One last pitfall, invisible in staging: translating the content but not the addresses, the titles and the descriptions. A language version whose addresses stay in the original language is still usable, but it shows the reader, in the results as in the address bar, text they do not read. That cannot be repaired later without a migration — that is, without the project the neighbouring guide describes.
Sources
- Managing multi-regional and multilingual sites — Google Search Centralaccessed on
- Tell Google about localized versions of your page — Google Search Centralaccessed on
- How to specify a canonical URL with rel="canonical" and other methods — Google Search Centralaccessed on
Block revalidated on
Frequently asked questions
- Should you redirect a visitor to the version in their language?
- The documentation asks that this automatic redirect be avoided, with a written reason: it can stop visitors and engines alike from seeing all versions of the site. A language selector visible on every page does the same job without confiscating the reader's choice.
- Subdirectory, subdomain or a domain per country?
- The documentation names no winner and publishes the trade-offs of each. A domain per country gives clear targeting but aims at one country and costs more; a subdirectory is simple and light to maintain but separates sites poorly. The choice depends on the project.
- Should a page declare itself among its versions?
- Yes, and it is explicit: every page must list all its alternate versions, including itself. It is the detail most often missed, and forgetting it makes the arrangement incoherent, since the declaration then stops being reciprocal between the versions.
- Are two very similar versions seen as duplicate content?
- The documentation handles that case and points to the language annotations and the canonical, whose job is to help serve the right version to the right reader. It therefore does not present the situation as a fault to fix, but as a case to declare correctly.