International SEO Site Structure: ccTLD vs Subdomain vs Subfolder

Filed November 10, 2026
Migrations and international sites, guide 3 of 4

No URL structure always ranks best internationally. Country-code domains, subdomains and subfolders each send different signals, cost different amounts to run and fit different organizations. Google’s multi-regional guide lists the options with their trade-offs rather than declaring a winner (Google’s guide to managing multi-regional and multilingual sites). The right choice depends on whether the site targets countries or only languages, how much local operation exists in each market, and how much separate maintenance the team can sustain.

The options

Structure	Example	Geotargeting signal	Maintenance	Notes
Country-code top-level domain (ccTLD)	<!–INLINECODE0–>	Strong	Highest: separate domains, hosting, certificates, Search Console properties	Some countries restrict who can register
Subdomain with gTLD	<!–INLINECODE1–>	Weaker; relies on other signals	Medium	Separate host; can run on separate infrastructure
Subdirectory with gTLD	<!–INLINECODE2–>	Weaker; relies on other signals	Lowest	Shares one host and its infrastructure
URL parameters	<!–INLINECODE3–>	Not recommended	Low	Hard to segment and to target

Google’s guide calls ccTLDs “a strong signal” for targeting, and notes that some countries restrict who can use their ccTLD. It also says vanity ccTLDs such as .tv or .me are treated as generic domains, not as country targets.

Signals Google uses besides the URL

Google lists the signals it uses to determine the target audience of a page:

ccTLDs;
hreflang statements in tags, headers or sitemaps;
server location, which Google says is “not a definitive signal”;
other signals such as local addresses and phone numbers on pages, local language and currency, links from other local sites, and Business Profile signals where available.

Google also says it ignores locational meta tags (such as geo.position) and geotargeting HTML attributes, and does not use code-level language information such as lang attributes or the URL to determine a page’s language; it uses the visible content.

Search Console’s country targeting setting is no longer available. Google’s help page says the International Targeting report was deprecated and that country targeting was “determined to have little value for the ecosystem, and is no longer supported” (Google’s deprecation note). Older advice that recommends setting a target country for a subfolder no longer applies.

A conditional decision matrix

Situation	Leaning	Reasoning
Separate legal entities, pricing, inventory and teams per country	ccTLD	Strong country signal; matches how the business operates; maintenance is already distributed
One business serving several countries with shared catalog and team	Subfolder	One host, shared authority and infrastructure, lowest overhead
Language versions without country differences (Spanish for all Spanish speakers)	Subfolder by language (<!–INLINECODE8–>)	Targeting is linguistic; hreflang handles language
Regions needing separate hosting or technical stacks (data residency, separate CMS)	Subdomain or ccTLD	Infrastructure separation drives the choice
Brand domain unavailable in some ccTLDs	Subfolder or subdomain	Avoids an inconsistent mix of domains
Small team, limited content per market	Subfolder	Fewer properties and systems to keep in sync

These are leanings, not rules. A large retailer with country entities may still choose subfolders for operational simplicity; a small company with a single overseas market may choose a ccTLD for local trust. The decision should be written down with its reasons so it is not revisited every year.

What every structure still needs

Localized content. A page targeting Germany with English content, US prices and a US phone number contradicts its own targeting, whichever URL structure it sits in. Google lists local language, currency, addresses and phone numbers as targeting signals.

Hreflang. Whatever the structure, language and regional versions need correct hreflang annotations so Google can show the right version.

One language per page. Google advises using a single language for content and navigation on each page and avoiding side-by-side translations; it also warns against translating only the boilerplate while leaving the main content in one language.

No forced redirects. Google advises against automatically redirecting users from one language version to another and says, “Don’t use IP analysis to adapt your content”. Let users choose, and offer a selector.

Duplicate same-language versions. When two regional versions in the same language are very similar, Google recommends picking a preferred version and using rel="canonical" and hreflang so the right URL is served.

Infrastructure limitations

ccTLDs multiply everything: registrations, renewals, certificates, DNS, analytics properties, Search Console properties and link building effort per domain.
Subdomains may be treated as separate sites by tools and need their own verification; cookies and analytics may need cross-domain configuration.
Subfolders share one server and one robots.txt; a problem on the host affects every market at once, and a CDN may be needed to keep response times reasonable for distant users.

Migrating between structures

Changing structure later is a site migration with URL changes: every international URL redirects, hreflang sets must be rebuilt, and rankings can fluctuate during reprocessing. Choose with a horizon of several years, and weigh the cost of a future move.

Choosing subfolders for a three-market expansion

As an illustration, take a US software company expanding into Germany, France and Japan with a shared product, one support team working in four languages and prices in local currencies.

Choice: subfolders by country-language (/de-de/, /fr-fr/, /ja-jp/) on the main domain.
Reasons: shared product and team, limited content per market at first, one infrastructure.
Requirements: full translation of product and pricing pages, local currency and payment options, reciprocal hreflang with x-default pointing to a language selector, no IP redirects.
Revisit trigger: if a market gets its own legal entity and team, reconsider a ccTLD for that market.
Limitation: the structure does not guarantee rankings in any country; local relevance and competition decide that.

The structure is the container. What goes into it (translated, localized, well-annotated content) is what each market’s searchers actually read, and no structure compensates for it.