The decision shouldn’t be based on an assumption that Google technically prefers one structure over the others, because Google’s own international and multi-regional sites documentation is explicit that it doesn’t. All three structures, country-code top-level domains (ccTLDs, like example.de), subdirectories (example.com/de/), and subdomains (de.example.com), are described as viable and capable of being understood and treated appropriately by Google’s systems once properly configured with correct locale signals (hreflang, localized content, and clear market targeting). The real decision drivers are business ones: how you want domain authority to consolidate, organizational and legal requirements in specific markets, and how much ongoing maintenance overhead your team can sustain across 30-plus markets.
Why “Google prefers X” is the wrong starting frame
This question often gets approached as if there’s a hidden technical ranking advantage to one structure, and that framing needs to be corrected first. Google’s documentation on locale-specific URL structures states plainly that it doesn’t have an inherent preference among ccTLD, subdirectory, and subdomain approaches; all three are supported patterns, provided the implementation correctly signals to Google which content targets which market/language (via hreflang annotations, and ideally through content that’s genuinely localized rather than machine-translated placeholder text). Choosing based on a supposed Google ranking preference is choosing based on something Google itself says isn’t the deciding factor.
What actually should drive the decision
Domain authority consolidation. Subdirectories inherit and consolidate the root domain’s overall authority most directly, since the entire international structure lives under one domain, and links, brand signals, and historical authority built on the root domain extend to every market subdirectory without needing to be rebuilt separately per market. This is the strongest practical argument for subdirectories at scale: a new market subdirectory launched under an established, authoritative root domain starts from a materially stronger position than a brand-new ccTLD would, which has to build its own independent domain authority essentially from zero. Subdomains sit in between; historically treated by search engines with somewhat more independence than subdirectories (closer to, though not identical to, a separate site in terms of authority signals), though Google has stated its systems have gotten better at understanding subdomains as part of the same overall site over time. ccTLDs are the most independent of the three in authority terms, each one is its own separate domain from Google’s perspective, with its own accumulation of links, trust signals, and history, built up market by market rather than inherited.
Organizational and legal factors. Some markets have practical or legal reasons that push toward a ccTLD regardless of the authority-consolidation tradeoff, certain countries have regulatory environments, local business registration requirements, or user trust conventions (some users in some markets specifically look for and trust a local ccTLD over a foreign parent domain with a subdirectory) that make a ccTLD the operationally necessary choice independent of what the SEO consolidation math would otherwise suggest. This is a genuine business/legal consideration that sits outside the ranking-technical question entirely.
Operational and maintenance capacity at scale. This is the factor that becomes most acute specifically at the 30-plus-market scale the question describes. A ccTLD-per-market strategy multiplies infrastructure and maintenance overhead substantially: 30-plus separate domains each need their own hosting/DNS management, their own SSL certificates, their own link-building and authority development essentially from scratch, and their own technical SEO monitoring (each is, from Google’s perspective, an independent site requiring independent crawl budget, independent Search Console property setup, independent technical health monitoring). A subdirectory structure keeps all of this consolidated under one domain and one technical infrastructure, which is dramatically more sustainable to maintain correctly across dozens of markets with a finite SEO/engineering team.
A practical decision framework
| Factor | ccTLD | Subdirectory | Subdomain |
|---|---|---|---|
| Domain authority consolidation | Weakest: each market builds independently | Strongest: fully inherits root domain authority | Moderate: partial inheritance, Google's understanding of subdomain-as-part-of-site has improved over time |
| Local market trust/legal fit | Strongest: clearest local signal, often legally required in some markets | Weaker local signal, though hreflang and localized content mitigate this | Moderate |
| Maintenance overhead at 30+ markets | Highest: separate infrastructure, certs, monitoring per market | Lowest: single consolidated infrastructure | Moderate |
| Implementation complexity | Highest | Lowest | Moderate |
For most multinational enterprises operating at real scale (30-plus markets) without a specific legal or market-trust reason forcing a ccTLD in a given country, subdirectories are the more operationally sustainable default given the authority-consolidation and maintenance advantages, with ccTLDs reserved for the specific markets where legal, regulatory, or demonstrated local-trust factors genuinely require them, rather than applied uniformly across the whole portfolio out of an assumption that ccTLDs carry some universal SEO edge Google’s own documentation doesn’t support.
