Multilingual, multi-regional, or both
Google's documentation separates the two cases. A multilingual site offers content in more than one language, possibly for the same country (a Swiss site in German, French and Italian). A multi-regional site targets different countries, possibly in the same language (a UK and an Australian edition in English, with different prices, stock and law). Many sites are both. The distinction matters because the problems differ: multilingual sites worry about translation quality and language detection; multi-regional sites worry about near-duplicate content across editions and about geotargeting.
The first decision is which markets actually justify a version. A version is a commitment: translated or localised content, local pricing and fulfilment, local support, local links, and ongoing maintenance in parallel with the primary edition. Markets that will get a machine translationTranslation produced by software or a language model, now fluent enough for first drafts but used with human post-editing applied by content type. and nothing else are usually better served by the primary edition with clear shipping information. Where a market does justify a version, the tutorial on deciding which content to localise first scopes a first wave that is localised properly and leaves the rest out of the edition.
URL structure
Google documents the URL structures it recognises for geotargeting, and the practical trade-offs are well established:
| Structure | Example | Geotargeting | Pros | Cons |
|---|---|---|---|---|
| Country-code top-level domain | example.fr | Strong, automatic for the country | Clearest signal to users and engines; legal separation | Separate domains to build authority on; cost; availability; not for languages |
| Subdomain | fr.example.com | Settable per subdomain | Separate hosting possible; one domain | Weaker authority sharing in practice; easily confused with language |
| Subdirectory | example.com/fr/ | Settable per directory | One domain's authority; simplest to maintain | Harder to separate hosting; must be structured consistently |
| URL parameter | example.com?loc=fr | Not recommended | None | Google documents parameters as not recommended for this |
Google's Search Console once offered an international targeting setting for subdomains and subdirectories on generic domains; that report was retired, and geographic targeting now rests on the structure, the hreflang annotations, the content's own signals (currency, address, language) and links. The documentation is explicit that country-code domains are the strongest geographic signal and that the engine ignores location-signalling tricks in page code.
For languages rather than countries, the structure must still be consistent: one directory or subdomain per language-region combination, the same path pattern across all of them, and never a mix where some versions live in directories and others on parameters. The site architecture guide covers the hierarchy; adding a locale is a layer on top of it.
Translation versus localisation
Google's guidance asks that each version be in one language — navigation and content alike — and advises against automatic translation presented as indexable content without review, which can count as auto-generated content under its spam policies. Beyond that minimum, the difference between a translated site and a localised one is what the market notices: currency, units, date formats, spelling, product names, regulatory text, examples, local contact details, local payment methods, and the keywords people in that market actually use, which are rarely literal translations. The keyword research section applies per market; the intent behind a query can differ by country even in the same language.
Telling the engine which version is which
Three mechanisms, which work together:
- Structure declares the target at the domain or directory level, as above.
- hreflang (hreflangAnnotation for language/region versions.) annotates each page with its alternates by language and region,
including a default for unmatched visitors. The hreflang guide covers
syntax, placement, reciprocity,
x-defaultand the errors Search Console (GSCGoogle's search performance and indexing tool.) reports. - Canonical tags (Canonical TagTells search engines the preferred URL.) remain per version: each localised page is its own canonical, never canonicalised to the primary edition, or the alternates disappear from the index. The interaction is the most common international mistake and the hreflang guide spells it out.
Google also documents that it does not use IP-based redirection as a signal and recommends against forcing visitors to a version by location: its crawler fetches mostly from one country and a redirect would hide the other editions. The documented pattern is to show a non-intrusive suggestion and let the person choose.
Duplicate content across editions
Two English editions that differ only in currency are near-duplicates. Google documents that hreflang is precisely the mechanism for this case: it tells the engine that the pages are intended alternates rather than copies, and the engine can show the right one. What hreflang does not do is make thin or identical editions rank; a regional edition earns its place with localised content and local links, and the crawling and indexing guide explains why near-duplicate sets are otherwise folded together.
The guides in this section
- hreflang, explained — the mechanism for declaring alternates in full:
syntax, placement, reciprocity,
x-defaultand the errors Search Console reports. - Keyword research for a new market — a tutorial for researching search demand in a new country or language from that market up, not by translating keywords: native research, local results pages, intent and pages.
Common international problems
| Symptom | Usual cause |
|---|---|
| The wrong country's page ranks in a market | Missing or non-reciprocal hreflang; canonical pointing to the primary edition; no localised signals |
| Editions compete with each other | Same language, no hreflang distinguishing regions |
| A new edition is not indexed | Blocked, canonicalised away, or thin machine translation |
| Visitors from abroad never see their edition | Forced redirects; no language switcher; no x-default |
| Search Console reports "no return tags" | One-directional annotations |
| Mixed-language pages | Navigation or boilerplate untranslated |
| The wrong country version ranks in a market despite fixes | Locale signals disagree: hreflang, canonicals, redirects or internal links |
Launching or restructuring editions is a migration; the site migrations guide applies in full. The international SEO expertise page describes the author's working approach and includes an hreflang generator.
