usdigitalmarketingindex.com SEO
When should multilingual sites use language folders rather than country-code domains?
Updated November 15, 2026
When the site is organized by language more than by country, when one team runs it on one platform, or when the business lacks the resources to operate separate sites for each market. Folders on a single generic domain, such as example.com/de/, keep everything on one host with one set of maintenance. Country-code domains, such as example.de, each tie a site to one country and each need their own registration, infrastructure, and upkeep. Google’s documentation lists both as valid structures with different pros and cons, and presents neither as better for ranking (Google’s guidance on multi-regional and multilingual sites). The choice is an operating decision about how the organization publishes, and the right answer is the one the organization can sustain.
Market organization
Start by separating two things the documentation distinguishes: a multilingual site offers content in more than one language, and a multi-regional site explicitly targets users in different countries. A site can be either or both.
| What varies | Example | Natural unit |
|---|---|---|
| Language only | The same articles in English, German, and Spanish, for readers anywhere | Language folder |
| Country only | One language, with different prices, stock, and legal terms per country | Country folder or country domain |
| Both | French for France and French for Canada, with different offers | Language-and-country units |
A country-code domain says “this site is for this country”. The documentation lists as a drawback that it “Can only target a single country”. That is a mismatch for content organized by language: Spanish content on a domain tied to Spain is positioned for Spain, and Spanish speakers elsewhere are outside its declared target. A folder such as /es/ makes no country claim.
Ask how the business is run. If each country has its own company, team, catalog, and legal obligations, the sites are separate in substance and separate domains reflect that. If one central team translates one body of content, a single domain with folders matches the work.
Hosting and maintenance
The documentation’s table gives the trade-offs. In its words:
| Structure | Listed pros | Listed cons |
|---|---|---|
| Country-specific domain, example.de | "Clear geotargeting"; "Server location irrelevant"; "Easy separation of sites" | "Expensive (can have limited availability)"; "Requires more infrastructure"; "Strict ccTLD requirements (sometimes)"; "Can only target a single country" |
| Subdirectories with gTLD, example.com/de/ | "Easy to set up"; "Low maintenance (same host)" | Users might not recognize geotargeting from the URL alone; "Single server location"; "Separation of sites harder" |
It lists a third option, subdomains on a generic domain, with its own balance, and a fourth, URL parameters, marked “Not recommended”.
What the listed points mean in practice:
| Concern | Folders | Country-code domains |
|---|---|---|
| Domains to register and renew | One | One per country, each under its registry's rules |
| Platform and hosting | One installation | One per site, or a multi-site setup |
| Security certificates, releases, monitoring | Once | Per domain |
| Analytics and Search Console | One property, with folder views | A property per domain |
| Local eligibility | None needed | Some registries require a local presence |
| Separating a market later | Harder | Already separate |
| Local team autonomy | Shared system | Independent |
Each country-code domain is a site that must be built up and maintained as its own property.
Geotargeting implications
On how Google determines a target locale, the documentation lists several signals.
- Country-code domains “provide a strong signal to both users and search engines that your site is explicitly intended for a certain country”.
- hreflang statements, in tags, headers, or sitemaps.
- Server location, which the documentation calls “not a definitive signal”.
- Other signals, including local addresses and phone numbers, local language and currency, and links from other local sites.
So a folder does not declare a country by its address, and a country-code domain does. A folder-based site states its targeting with hreflang and with the content itself.
The documentation also notes a cost to country targeting in general: it “can improve your page rankings in the target country, but at the expense of results in other locales or languages”. A business that wants one language version to serve many countries should weigh that before tying it to one.
Some cautions. The documentation says Google treats certain “vanity” country-code domains, such as .tv and .me, as generic. In its entry for subdomains it notes that users might not tell whether “de” is the language or the country, and a folder named /de/ has the same ambiguity, so name folders clearly, for instance /de-de/ and /de-at/ where both a language and a country are meant. And the country domain signal is described as a statement of intended audience. Nothing on the page presents it as a ranking advantage in itself.
Whatever the structure, the markets will not perform alike, because demand differs from country to country. Comparing them fairly is covered in the guide to comparing international organic performance while accounting for country-level demand.
Selection matrix
A two-country publishing architecture example. A hypothetical heating retailer sells in the United Kingdom and Germany.
| Factor | Its situation | Points toward |
|---|---|---|
| Legal entities | One company trading in both countries | Folders |
| Teams | One content team; a German translator | Folders |
| Catalog | Mostly shared; some country-specific products | Either |
| Prices, tax, delivery | Differ by country | Country units, as folders or domains |
| Platform | One store installation | Folders |
| Budget for separate operations | None | Folders |
| Future plan | May sell the German business | Domains would ease separation |
| Local trust | German customers recognize .de | Domain |
A reasonable outcome: example.com/en-gb/ and example.com/de-de/ on one platform, with hreflang connecting equivalent pages, local currency and contact details on each, and the option to move the German section to its own domain later, with redirects, if the business is separated.
Selection matrix:
| Condition | Folders | Country-code domains |
|---|---|---|
| Content organized by language, read across countries | Yes | No |
| One team, one platform | Yes | Costly |
| Each country a separate business | Possible | Yes |
| A language served to several countries | Yes | One domain per country needed |
| Local registration requirements can be met | Not relevant | Required |
| Resources to run several sites | Not required | Required |
| Markets may be divested | Harder | Easier |
| Clear country identity in the address matters to customers | Weaker | Stronger |
Decide with the people who will run the result, and record the reasons. Whichever structure is chosen, the same disciplines apply: one URL per language or country version, hreflang across equivalents, no automatic redirection that hides versions, and content that is truly localized.
Changing structure later is a migration, with redirects for every URL and a period of adjustment. That cost is a reason to choose with the next several years in view.
A related structural question for single-market sites, whether a section belongs on a subdomain or in a folder, is examined in the guide to when a publisher should place SEO content on a subdomain rather than a subfolder.
The criterion: use language folders when the organization publishes as one operation across languages, and country-code domains when each country is run, and should be seen, as its own site.
Add your comment to this answer