If you are launching a site in multiple countries, your single biggest structural decision is how to arrange those versions: a separate country domain (ccTLD like example.de), a subdirectory on one domain (example.com/de/), or a subdomain (de.example.com). For most sites, subdirectories on a single strong domain are the safest default because they consolidate authority and are easiest for both search engines and AI systems to treat as one trusted entity. But the right answer depends on your resources and how local you need to appear.
The three structures, compared
A ccTLD is a country-code top-level domain such as .de, .fr, or .co.uk. It sends the strongest possible geo-targeting signal and often builds the most local trust with users, who recognize their national extension. The cost is steep: each ccTLD is effectively a separate site that must earn its own authority, links, and reputation from zero. Ten countries can mean ten domains to promote.
A subdirectory keeps every market under one domain, in folders. All the links, age, and authority your domain has earned flow to every language version. This is the most efficient way to build authority once and share it everywhere, and it is the structure Google itself uses for many of its international properties. You set country or language targeting through hreflang and content rather than the URL host.
A subdomain sits in the middle. It is technically a distinct host, which historically meant authority did not flow as freely as with subdirectories, though the gap has narrowed. Subdomains make sense when different markets run on genuinely separate infrastructure or CMS instances, but for pure SEO efficiency they rarely beat subdirectories.
How to choose
- Choose subdirectories if you want maximum authority consolidation, have limited link-building resources, and can serve all markets from one platform. This is the right call for the large majority of sites.
- Choose ccTLDs if local trust is business-critical (finance, health, government-adjacent), you have the budget to build each domain independently, or legal and hosting requirements demand a country-specific presence.
- Choose subdomains when technical or organizational separation forces it — different teams, platforms, or hosting per region — and you accept the added authority-management overhead.
Whatever you pick, commit early. Migrating between structures later is a full site migration with real risk to rankings and AI citations, so it is far cheaper to decide correctly up front than to move house after you have grown.
Why structure shapes your AI visibility
AI answer engines build a model of who is authoritative on a topic and attribute content to entities. A single domain with clean subdirectories presents one strong, coherent entity: all your topical authority, backlinks, and brand signals reinforce each other, making you a more confident pick for citations across every language. Ten thinly-linked ccTLDs fragment that signal — each one has to earn recognition separately, and a young country domain may simply lack the authority to be cited even when its content is excellent. If you go the ccTLD route, plan explicitly for how each domain will build independent authority, and lean on strong internal and external linking. The relationship between consolidated authority and getting cited is the same principle behind building topical authority with content clusters.
Don't rely on structure alone
No URL structure targets languages by itself. Whichever you choose, you still need correct hreflang annotations so engines serve the right version to the right audience, native-quality localized content rather than machine translation, and consistent canonicals. Structure decides how authority flows; hreflang and content decide who sees what. Get both right and you present a clean international footprint that search and AI can navigate without guessing.
Ready to check whether your international setup reads cleanly to crawlers and AI — correct hreflang, consolidated signals, no accidental duplication? Run your site through the CheckMy.site scanner and fix what it surfaces.