Information checked on 19 November 2026 in the Google Search Central documentation.
Languages or countries: the first question.
Google distinguishes two situations. A multilingual site offers the same content in several languages: a Belgian agency in French and Dutch. A multi-regional site targets different countries, sometimes in the same language: a shop that sells in France and Switzerland. The two can be combined.
The answer changes everything else. If you target languages, one site is enough. If you target countries, each with its own prices, delivery or legal notices, you need one version per country.
Three URL structures, three real cases.
One folder per language.
All versions live on the same domain name: example.com/en/, example.com/es/. It is the easiest structure to maintain, and every link you earn benefits the same domain.
Frédéric François's website works this way, in French, English, Spanish and Italian. His audience is defined by language, not by country: one folder per language is enough.
Immo Chrysalide follows the same logic on a .be domain, in French, Dutch and English. The agency works in Belgium, so its tags specify the country: fr-BE and nl-BE. Every property is published automatically in all three languages.
One domain name per country.
Each market has its own extension: .nl, .de, .es. It is the strongest geographic signal for Google, and the most reassuring one for buyers. The trade-off: each domain has to build its reputation on its own, and links earned by one do not benefit the others.
Geek Collector made this choice: .be in French, .nl in Dutch, .de in German, .es in Spanish and .co in English. For a shop that ships abroad, a local address matters at checkout.
Subdomains and parameters.
A subdomain (fr.example.com) is a middle-ground option, less common for a small business. URL parameters (example.com?lang=fr) are not recommended by Google.
Hreflang tags, without mistakes.
An hreflang tag tells Google that a page exists in another language, and at which address. Four rules avoid most mistakes:
- Each version lists all the others, and itself.
- References are reciprocal: if the French page lists the English page, the English page lists the French page.
- The code names a language (fr) or a language and a country (fr-BE), never a country on its own.
- An x-default value names the version to show visitors whose language is not covered.
These tags do not lift a page in the results. They show the right version to the right person.
What Google actually reads.
Google works out a page's language from its visible text, not from its address or its code. A page whose menu is translated but whose content stays in French is a French page.
Google also advises against automatically redirecting visitors based on their country or browser language: its crawler mostly crawls from the United States and may never see the other versions. A visible language switcher on every page works better.
To work out the target country, Google combines several signals: the domain extension, hreflang tags, a local address and phone number, the currency, links from sites in that country and the Google Business Profile.
Translating is not enough.
Words change from one market to another, even within a single language. A British shopper searches for "trainers", an American for "sneakers". Keyword research has to be redone for each market.
Everything gets translated, not just the visible text: titles, descriptions, image alt text, page addresses, automated emails. On Immo Chrysalide's website, confirmation emails go out in the visitor's language.
Finally, a single French version is enough for the whole French-speaking world. Identical copies per country compete with each other. A per-country variant is only worth it if the page really changes: prices, currency, delivery, legal notices.
Where to start.
- Decide whether you are targeting languages or countries.
- Choose the URL structure, and stick with it.
- Have a native speaker translate, keywords included.
- Add the hreflang and x-default tags, then check that they are reciprocal.
- Track results country by country in Search Console, in the Performance report.
Frequently asked questions.
Do you need a domain name per country?
No. One folder per language on a single domain is enough in most cases. A domain per country makes sense for a shop that genuinely sells in each country and can build each site's reputation.
Do hreflang tags improve rankings?
No. They are used to show the right language version in the results. Rankings depend on the content and links of each version.
Should you redirect visitors to their language?
No. Google advises against it. Offer a visible language switcher and let visitors choose.
Can you translate your website automatically?
Machine translation can serve as a first draft. It must be reviewed by a native speaker, because the words people search for differ from one market to another.
Can a .com or .co domain target a country?
Yes. Google treats these extensions as generic: the site can rank anywhere. The target country is then inferred from the content, hreflang tags, local contact details and links.
Nelty builds Next.js websites and Medusa stores in several languages, including those of Frédéric François, Immo Chrysalide and Geek Collector. The URL structure, hreflang tags and redirects are part of every project.