International site structure: ccTLD, subfolder or subdomain

When a business expands to new countries or languages, one of the first technical questions is where the new versions should live. example.de? example.com/de/? de.example.com? The choice affects how search engines understand which audience each version is for, how authority flows between versions, how much it all costs to run, and how painful it will be to change later. There is no single correct answer, but there are clear trade-offs.

The options

Structure	Example	Strengths	Weaknesses
Country-code domain (ccTLD)	example.de, example.fr	Clearest country signal; local trust; legal and brand separation	Each domain builds authority from scratch; costly to run; some ccTLDs have registration requirements; domain may be unavailable
Subfolders on a generic domain	example.com/de/	Shares authority across versions; one site to maintain; easy to launch new markets	Weaker country signal on its own (hreflang and content compensate); one platform for all markets
Subdomains	de.example.com	Can run on separate infrastructure; clear separation	Authority sharing less straightforward in practice; more setup than subfolders
Separate generic domains	example-germany.com	None that the others do not offer better	No country signal; splits authority; confusing for users
URL parameters	example.com/?lang=de	Easy to bolt on	Not recommended by Google; poor for crawling, sharing and targeting

How search engines work out the target audience

Search engines combine several signals to decide which country and language a page is for:

• The domain: a country-code domain is a strong signal that the site targets that country. Generic domains (.com, .org, and some country codes widely used generically, such as .io or .co) carry no country signal.
• hreflang annotations linking equivalent versions; see hreflang implementation.
• Language of the content, detected from the text itself. The lang attribute helps browsers and some search engines.
• Local signals: currency, local addresses and phone numbers, local references, links from sites in that country.

Search Console's old international targeting setting, which let site owners assign a country to a generic domain, was retired in 2022. hreflang and local content now do that job.

Choosing: questions that decide it

1. Language or country? If you serve languages rather than countries (Spanish for all Spanish speakers), subfolders by language (/es/) on one domain are usually simplest. If prices, products, laws or delivery differ by country, you need country versions, which can still be subfolders (/de-at/, /de-ch/) or ccTLDs.
2. How much authority does the main domain have? A strong .com lends its reputation to new subfolders immediately. A new ccTLD starts from zero.
3. How many markets, and how fast? Launching in twenty markets is far cheaper with subfolders. Twenty ccTLDs means twenty sites to build links for, monitor and keep secure.
4. Who runs each market? Independent local teams with their own platforms and budgets may be better served by ccTLDs or subdomains. A central team usually prefers one site.
5. Do local customers expect a local domain? In some countries, shoppers trust a local domain noticeably more. This is a business judgement worth testing with real customers.
6. Legal or brand requirements? Some businesses need separate entities, payment providers or data storage per country, which can push towards separate domains.

Whatever you choose, write the decision and its reasons down. International structures outlive the people who chose them, and a short note explaining why the site uses subfolders saves a future team from an expensive "fix". For most small and mid-sized businesses expanding into a few markets, subfolders on a generic domain are the pragmatic default. Large brands with strong local operations often use ccTLDs, and pay for it in effort.

Making subfolders work well

• Use a consistent pattern: /de/ for language, /de-at/ for language-country. Do not mix patterns.
• Keep each version complete: navigation, footer, legal pages and checkout in the local language.
• Implement hreflang across all versions, with self-referencing canonicals on each.
• Give each version local contact details, currency and delivery information.
• Add each subfolder as its own URL-prefix property in Search Console as well as the domain property, so you can see performance per market. See properties.

Making ccTLDs work well

• Link versions with hreflang, even though they are on separate domains.
• Build local links for each domain: local media, partners, associations. A ccTLD with no local links has little advantage.
• Keep templates, structured data and technical standards consistent; drift between country sites is a common source of problems.
• Monitor each domain separately. A technical problem on one country site can go unnoticed for months if reporting focuses on the main one. A scheduled check per domain, such as DeskSEO's monitoring, catches that drift; the plans cover several domains.

When subdomains make sense

Subdomains are a reasonable choice when a version genuinely needs to be separate: a market served by a different e-commerce platform, a local partner running its own content system, or a version hosted in another region for legal reasons. Search engines can handle them well. The practical cost is that each subdomain tends to be treated more like its own site in reporting and tooling, and teams often forget to give it the same care as the main site: it ends up with an outdated template, missing hreflang, or no monitoring. If you choose subdomains, treat each one as a site with an owner.

Details that apply to every structure

• One version per URL. Do not show different languages at the same URL based on cookies or browser settings; crawlers will see only one of them.
• A visible language and country switcher on every page, linking to the equivalent page in other versions rather than to each version's home page.
• No forced redirects by IP address. Suggest the local version with a banner instead; the hreflang guide explains why.
• The lang attribute on each page's html element, matching its content.
• Fast delivery everywhere. A CDN removes the need to host each version in its own country.

A worked example

A hypothetical maker of merino base layers sells from merino-example.com in English to the US and UK. It plans to add Germany, France and the Netherlands with a three-person marketing team and one e-commerce platform. Country domains would mean three new sites with no links and three times the maintenance; the team cannot support that. Instead it launches /de/, /fr/ and /nl/ as full language versions with euro pricing and EU delivery details, splits the English site into /en-us/ and /en-gb/ because prices, sizes and returns differ, and connects everything with hreflang. Native-speaking freelancers localise the top fifty pages per language before launch; the rest of the catalogue follows over three months. If Germany later grows into a large market with its own team, a move to a ccTLD remains possible, as a planned migration.

Languages and machine translation

Whatever the structure, the content decides whether a version succeeds. Machine-translated pages left unreviewed read awkwardly to native speakers, often miss how people actually search, and convert poorly. The localizing keywords guide explains why translation alone is not enough. A smaller number of well-localised pages beats a full machine translation of everything.

Changing structure later

Moving from ccTLDs to subfolders, or the reverse, is a full migration for every version: redirects for every URL, updated hreflang, new Search Console properties, and a period of instability. It can be worth it, for example to consolidate authority after years of thin country sites, but plan it like any other migration; see the migration checklist. The cheapest structure change is the one you avoid by choosing carefully at the start.

A starter decision table

Situation	Usual choice
One business, a few languages, central team	Subfolders by language
Prices and delivery differ by country, central team	Subfolders by language-country
Strong local brands with separate teams and budgets	ccTLDs
Separate product or platform per market	Subdomains or ccTLDs
Testing a single new market cheaply	One subfolder, expand later