The short answer: subdirectories consolidate link equity under one domain and are simpler to manage. Subdomains give you more separation and control per market. Neither is inherently better for international SEO – the right choice depends on your team structure, how different your markets are, and whether you need technical independence between regions. ccTLDs are the third option, but they’re the most expensive and complex to maintain.
Most advice on this topic lists generic pros and cons and leaves you to figure out the rest. This guide goes further. It covers how each structure affects link equity, crawling, hreflang implementation, and content workflows – then gives you a decision framework built specifically for international SEO, not recycled from a “subdomains vs subdirectories” post that’s really about blog hosting.
What’s the Actual Difference?
Three URL structures are used for international sites. Here’s what each looks like in practice:
Subdirectory (subfolder): `example.com/de/`, `example.com/fr/`, `example.com/us/`
Subdomain: `de.example.com`, `fr.example.com`, `us.example.com`
ccTLD (country code top-level domain): `example.de`, `example.fr`, `example.us`
Subdirectories sit within your main domain. Everything lives under one roof. Subdomains are technically separate sites that share a root domain but operate independently in most respects. ccTLDs are entirely separate domains registered per country.
Google has stated repeatedly that it can handle all three structures. John Mueller has said on record that Google doesn’t inherently prefer one over another – they’re all valid signals for geotargeting. The differences aren’t about what Google can process. They’re about how each structure affects your SEO operations in practice.
How Does Each Structure Handle Link Equity?
This is where the subdirectory argument gets its strongest ammunition.
With subdirectories, every backlink to any regional version of your site strengthens the same domain. A link to `example.com/de/resource/` benefits `example.com` as a whole. Domain authority (or whatever proxy you use for it) accumulates in one place. For businesses entering new markets with limited regional link profiles, this is a genuine advantage. Your German pages benefit from the authority your UK site has already built.
Subdomains don’t consolidate equity in the same way. Google treats subdomains as largely separate entities for ranking purposes. A backlink to `de.example.com` primarily benefits `de.example.com`. Your main domain gets some indirect association, but the subdomain needs to build its own authority. That’s a harder starting position if you’re launching into a competitive market from scratch.
ccTLDs take this further still. Each domain is fully independent. `example.de` shares nothing with `example.co.uk` unless you actively build cross-referencing signals. The upside is a strong geotargeting signal baked into the domain itself. The downside is maintaining authority across multiple domains from day one.
What About Crawlability and Indexing?
Subdirectories keep everything in one crawl scope. A single robots.txt, a single sitemap (or sitemap index), and one domain for Googlebot to crawl. This simplifies technical SEO significantly. Crawl budget is shared, but for most sites that aren’t running millions of pages, this isn’t a real constraint.
Subdomains each need their own robots.txt, their own sitemap, and their own Google Search Console property. That’s more configuration, more monitoring, and more places for things to go wrong. But it also means you can control crawling per market independently. If your Japanese site has a fundamentally different structure to your UK site, separate crawl management is actually useful.
ccTLDs multiply this again. Each domain is a fully independent entity in GSC, in your CDN configuration, in your hosting, and in your monitoring tools. The overhead is substantial.
How Does Hreflang Work Across Each Structure?
Hreflang tags tell search engines which version of a page targets which language and region. They work with all three structures, but implementation complexity varies.
With subdirectories, hreflang is relatively straightforward. You’re referencing URLs on the same domain, and you can manage all hreflang annotations in a single sitemap or set of HTTP headers. Debugging is simpler because everything’s in one GSC property (though you can still create separate properties per directory).
With subdomains, each hreflang tag references a different host. You need to ensure each subdomain’s sitemap includes the full set of hreflang annotations pointing to all other subdomains, and each subdomain must reciprocate. If `de.example.com` declares `uk.example.com` as its English alternative, `uk.example.com` must confirm the reverse. When these fall out of sync – and they do, especially during deployments – Google ignores the annotations entirely.
ccTLDs have the same cross-referencing requirement as subdomains, with the added complication that you’re managing annotations across entirely separate domains. Any change to your URL structure on one domain requires updating hreflang on all of them.
When Should You Use Subdirectories?
Subdirectories work best when:
You’re entering new markets without an established presence. The inherited domain authority gives regional pages a head start they wouldn’t get on a standalone subdomain or ccTLD.
Your content is largely the same across markets, with translation and localisation rather than fundamentally different offerings. Subdirectories handle this neatly – same structure, different language folders.
Your team is small or centralised. One CMS instance, one deployment pipeline, one set of technical configurations. Less can go wrong, and fewer people need access to fewer systems.
Budget is a constraint. No additional domain registrations, no separate hosting or CDN configurations per market, no multiplied tooling costs.
Wikipedia is the most prominent example. Every language version sits under the same domain (en.wikipedia.org is technically a subdomain, but their content structure within each version uses subdirectory logic). HubSpot uses subdirectories for its regional content – `hubspot.com/de/`, `hubspot.com/fr/` – keeping everything under one authoritative domain.
When Do Subdomains Make More Sense?
Subdomains are the stronger choice when:
Your markets need genuine independence. Different product lines, different regulatory requirements, different content strategies. If your German site needs a completely different CMS setup or tech stack to your UK site, subdomains give you that separation without the cost of ccTLDs.
You have dedicated teams per region. Subdomains let each team deploy, configure, and manage their site without risking changes to other markets. When your Brazilian team pushes a code update, it doesn’t affect your UK site.
Branding varies between markets. If your US offering is positioned differently to your UK one – different services, different messaging, different competitive environment – subdomains make that separation cleaner.
You want independent GSC data and analytics without having to rely on filtered views or regex segments to isolate regional performance.
And yes, we use subdomains at Gorilla Marketing – `us.gorilla.marketing` and `uae.gorilla.marketing` sit alongside the main UK site. The trade-off in link equity is real, but the operational independence matters when you’re running genuinely distinct market strategies.
When Are ccTLDs Worth the Investment?
ccTLDs send the strongest geotargeting signal. A `.de` domain tells both Google and German users that this site is for them. If brand trust in local markets is a priority and you have the budget to build authority on separate domains, ccTLDs are worth considering.
They make most sense for large businesses with established brand recognition, dedicated teams, and the marketing budget to run link acquisition in each market independently. If you’re a mid-sized business testing international expansion, ccTLDs are almost certainly overkill.
Some businesses use a hybrid approach: ccTLDs for their primary markets (where they’ve built brand recognition and links over years) and subdirectories or subdomains for newer or smaller markets. This balances strong local signals in key regions against the cost efficiency of consolidated structures elsewhere.
What Does Each Structure Actually Cost?
The cost differences extend well beyond domain registration.
Subdirectories are the cheapest to run. One hosting environment, one SSL certificate, one CDN configuration, one set of monitoring tools, one CMS. The incremental cost of adding a new market is essentially the content and translation work.
Subdomains add moderate overhead. Each subdomain may need its own SSL (though wildcard certificates handle this), its own GSC property and verification, and potentially separate analytics configurations. If you’re running different CMS instances per subdomain, hosting costs scale too. For 2-3 markets this is manageable. For 15+, it adds up.
ccTLDs are the most expensive at every level. Domain registration fees per country (and some ccTLDs have residency requirements or premium pricing), separate hosting, separate SSL, separate tooling, and fully independent link building campaigns for each domain. Budget accordingly.
How Do You Handle Migration Between Structures?
Switching structures mid-flight is possible but painful. If you’re currently on subdirectories and want to move to subdomains (or the reverse), expect:
A full technical migration with 301 redirects from every old URL to its new equivalent
Temporary ranking fluctuations while Google reprocesses the new structure
Hreflang annotation rewrites across all regional versions
Updated canonical tags on every page
GSC property changes and historical data loss in the old properties
Broken internal links if your content references absolute URLs
The key lesson: pick the right structure before you launch, not after you’ve built authority on the wrong one. A migration isn’t the end of the world, but it’s expensive, time-consuming, and disruptive enough that you want to avoid it.
What About Content Management at Scale?
This is the question most guides skip, but it’s often the deciding factor.
With subdirectories, translation workflows are simpler. Your content team works in one system, and translated versions mirror the original URL structure with a language prefix. Plugins and translation management systems integrate cleanly. Updating a page means updating it once and pushing translations through the same pipeline.
With subdomains, each site can diverge. That’s powerful if your markets need different content, but it also means changes don’t automatically propagate. If you update your pricing page on the UK site, someone has to remember to update it on the US and German sites too. Without strict processes, content drift is inevitable.
ccTLDs amplify this problem. Fully separate sites mean fully separate content management. Unless you’ve built automation to sync content across domains, each site operates in isolation.
For international keyword research, the structure you choose affects how you organise and prioritise. Subdirectories encourage a centralised keyword strategy with regional variations. Subdomains and ccTLDs push you toward independent keyword strategies per market, which may be exactly what you need if search demand differs significantly between regions.
A Decision Framework for International SEO
Rather than defaulting to whatever your CMS makes easiest, run through these questions:
1. How different are your markets? If you’re selling the same products with translated content, subdirectories. If each market has different products, pricing, regulations, or customer journeys, subdomains or ccTLDs.
2. How big is your team? Centralised team managing everything? Subdirectories. Regional teams with their own developers and content managers? Subdomains or ccTLDs.
3. What’s your existing domain authority? Strong domain with years of links? Subdirectories let new markets inherit that authority. Starting fresh in every market regardless? The equity argument matters less.
4. How many markets are you targeting? Two or three? Any structure works. Ten or more? Subdirectories scale most efficiently. ccTLDs across 15 countries require serious operational investment.
5. Do you need technical independence? Different tech stacks, different deployment schedules, different hosting requirements per region? Subdomains. Same setup everywhere? Subdirectories.
6. What’s your budget? Subdirectories are cheapest. Subdomains sit in the middle. ccTLDs cost the most and require the most ongoing investment.
If you answered “subdirectories” to four or more of those questions, start there. If “subdomains” or “ccTLDs” came up repeatedly, you likely need the separation they provide. And if you’re genuinely unsure, subdirectories are the safer default – you can always migrate later if the limitations start to bite.
Getting the Structure Right From the Start
The subdomain vs subdirectory debate doesn’t have a universal winner. It has a right answer for your specific situation – your team, your markets, your budget, and your growth plans. Get it right at the outset and you’ll save yourself a painful migration down the line.
If you’re planning international expansion and aren’t sure which structure fits, it’s worth getting an SEO audit before you build. The URL structure decision cascades into everything else – hreflang, content cannibalisation, internal linking, analytics, and crawl management. Better to make the call once, with the full picture, than to rebuild later.
