ccTLD vs subfolder: what actually moves the needle

ccTLD vs subfolder: what actually moves the needle

The perennial structure debate. Rather than rehearse opinions, here's what we can and can't support with evidence.

What holds up:

— ccTLDs (example.de) carry an inherent, unambiguous geotargeting signal Google cannot override and users trust visually. The cost is real: separate authority pools, separate link equity, no Search Console country-targeting needed but also none available.

— Subfolders (example.com/de/) inherit the root domain's accumulated authority. For sites without decades of per-country link history, this is usually the pragmatic winner — one strong domain beats fifteen weak ones.

— Subdomains (de.example.com) sit awkwardly between. Google treats them as part of the same site for most purposes now, so they capture less of the "separate brand" benefit while still fragmenting some signals.

What we cannot honestly claim: that one structure ranks better holding all else equal. The confound is fatal — sites that can afford 30 ccTLDs differ systematically from sites on subfolders, so observational comparisons measure budget and brand, not architecture.

The defensible heuristic: choose ccTLD when local trust and legal separation justify rebuilding authority per market; choose subfolders when consolidating authority matters more. Both work with correct hreflang.

Caveat: this is structure for organic search. Local payment, hosting, and legal requirements can force ccTLDs independent of any SEO argument.