ccTLD

Three ways to structure international sites

Architecture	Example	Geographic signal	Authority
ccTLD	example.de, example.fr	Strongest	Split across domains
Subdirectory	example.com/de/, example.com/fr/	Moderate (via hreflang + GSC targeting)	Consolidated on one domain
Subdomain	de.example.com, fr.example.com	Moderate	Mostly separate (Google treats subdomains as ~half-separate)

When ccTLDs win

• Strong local trust matters — Japan, Korea, parts of Europe prefer local-domain brands
• Long-term commitment to a market with dedicated team, content, customer service
• Legal/regulatory requirements (.de has compliance benefits for German operations)
• Brand protection — owning .de prevents squatters

When ccTLDs lose

• Limited budget / team — running 5 ccTLDs means 5 separate SEO programs
• Short-term market entry — subdirectory is faster to launch and easier to retract
• Cross-market authority sharing — content authority on .com doesn’t transfer to .de
• Tech complexity — separate hosting, separate analytics, separate everything

Hybrid approaches

Some enterprises run ccTLD for top markets + subdirectory for others:

• example.com — US (primary)
• example.de — Germany (dedicated team, high priority)
• example.com/fr/ — France (lower priority, faster launch)
• example.com/es/ — Spain

This is a defensible mid-ground but adds architecture complexity.

hreflang implications

Regardless of architecture, hreflang annotations are essential to tell Google which version to serve which user. ccTLDs need hreflang too — Google doesn’t infer language equivalents automatically just because two sites share a brand name.

Resocial perspective

Country domain strategy is one of the most consequential international SEO decisions — reversing it later is expensive. We treat it as a multi-stakeholder discussion (SEO + legal + finance + product) and document the rationale, not just the choice.