A decision tree for subfolder vs subdomain vs ccTLD

A decision tree for subfolder vs subdomain vs ccTLD

The "which structure?" debate generates more heat than rigor. We prefer a constrained decision procedure over ideology:

— Is local trust/legal a hard requirement (banking, gov-adjacent, strong local-brand expectation)? If yes, ccTLD — its built-in geotargeting and local credibility outweigh the consolidation cost. Stop here.
— Otherwise, do you have the engineering to run one codebase with path-based localization? If yes, subfolders (/de/). They inherit domain authority most directly and are simplest to wire for hreflang.
— Constrained to separate hosting/CDN/teams per market, or a platform that forces it? Subdomains (de.) — a defensible middle path, but treat each subdomain as needing its own authority-building; consolidation through them is weaker than folders.
— Whatever you pick, geotargeting still comes from hreflang + content + (for non-ccTLD) explicit GSC settings. Structure alone targets nothing.

The evidence base here is thin and contested — Google has repeatedly said it handles all three, and case studies cut both ways because they rarely isolate structure from execution quality. We'd caution against citing any single "subfolders won +X%" study; the confound is almost always migration hygiene, not the structure itself.

Our honest position: for most multi-market sites without legal/trust constraints, subfolders minimize total risk. But the structure matters less than the discipline you bring to canonicals, mappings, and hreflang reciprocity.