International SEO: ccTLD, subfolder or subdomain?

International SEO starts with a decision that is expensive to reverse: where each country or language version of the site will live. A country-code domain, a subdomain and a subfolder can all work, and Google's own documentation lists the trade-offs of each rather than naming a winner. This article turns that documentation into a decision rule, so the choice follows your constraints instead of a rule of thumb copied from a vendor blog.

What Google actually documents

Google's guide to managing multi-regional and multilingual sites compares four URL structures. A country-specific domain (example.de) makes geotargeting unambiguous, is independent of server location and keeps sites easy to separate, but it can be costly, sometimes hard to obtain, needs more infrastructure, may carry strict registration requirements and can target only one country. A subdomain on a generic domain (de.example.com) is quick to set up, allows different server locations and keeps sites separate, but users may not tell from the URL whether "de" means a language or a country. A subdirectory (example.com/de/) is quick and cheap to maintain because it shares one host, but the geotargeting is less visible to users, it uses a single server location and the versions are harder to separate. URL parameters are marked as not recommended.

Two cautions in the same guide matter for the decision. Geotargeting is not an exact science, so plan for visitors who land on the wrong version, for example with a language or region selector. And you should not adapt content by analysing visitors' IP addresses. Whatever structure you pick, the guide says to tell Google which pages apply to which languages or locations with hreflang annotations or sitemaps. Notice what the guide does not do: it lists operating and signalling trade-offs, not ranking advantages.

Reading the trade-offs as constraints

The useful way to read the list is as constraints you either have or do not have. Choose a ccTLD when the country version must be a separate operation: its own legal entity, hosting, currency, catalogue or local team. The price is that every domain is its own site to maintain, secure, link to and monitor, and one domain serves one country. Choose subfolders when one brand, one team and one CMS serve several markets; you maintain a single host and rely on hreflang and localised content for the location signal. Choose a subdomain mostly when infrastructure forces it, for example a separate platform per market. In practice we rarely meet a content-driven reason for subdomains.

A four-question decision rule

1. Must the country version be a separate operation, with its own legal entity, hosting, prices or team? If yes, a ccTLD (or at least a separate site) fits.
2. Do you target one country, or one language across several countries? A language across countries cannot sit on a single ccTLD, which points to language subfolders.
3. Can your team maintain several domains, with their own certificates, analytics, Search Console properties and link profiles? If not, a multi-domain setup tends to decay.
4. Does your platform fix the URL structure, for example a separate stack per market? Then a subdomain may be the realistic option.

If none of the four applies, default to one subfolder per language (or language and country) on a single domain. The order matters: separation requirements come first because they are the ones you cannot negotiate later.

A worked illustration

Take a business with Turkish, English, Arabic and Persian audiences, one team, one CMS and no separate legal entity per country. Question one: no. Question two: languages across countries, so no single ccTLD can serve them. Question three: a small team, so several domains would be a burden. Question four: the CMS supports folders. The answer is language subfolders, which is the structure our own site uses: English under /en/, Arabic under /ar/, Persian under /fa/ and Turkish at the root. A group with a registered entity, warehouse and pricing in Germany would answer question one differently and could justify a German ccTLD.

Before you commit: a short checklist

• Map each market to a language, a currency and a legal owner, and note where they differ.
• Decide where hreflang lives: HTML tags, HTTP headers or the XML sitemap. Google treats the three as equivalent, so pick the one you can keep consistent.
• Define the fallback page for visitors whose language matches no version (x-default), often a language selector.
• Write down the structure decision and its reasons, so a later migration is argued from constraints rather than taste.

What the choice does not fix

The URL structure only decides where versions live. It does not make hreflang correct or translate the content well, and most of the practical problems arise there; our list of the most common hreflang errors shows how they are found. Changing structure later is a site migration with a redirect map, so it is worth deciding carefully once. The technical side of that work sits within our technical SEO service, and the wider market-entry picture within our international SEO service and the full services overview.

Sources

• Google Search Central — Managing multi-regional and multilingual sites: URL structure options, geotargeting and hreflang.
• Google Search Central — Localized versions of your pages: hreflang, x-default, reciprocal links and supported methods.