Subdomains and subdirectories are the two primary URL structures for organizing international content, and the choice between them affects how search engines crawl, index, and distribute authority across your regional pages. A subdomain (us.example.com) creates a separate host under your root domain. A subdirectory (example.com/us/) adds a folder path to your existing domain. Both work for international SEO. Neither is universally better. The right answer depends on your technical resources, organizational structure, and how much domain authority you can afford to split.
At Gorilla Marketing, we run our own international presence on subdomains across three markets: UK, US, and UAE. We’ve also built subdirectory-based international sites for clients. Both structures rank. Both have trade-offs that matter long before launch day. This guide walks through the differences that actually affect performance and gives you a framework to make the right call.
What’s the Actual Difference Between a Subdomain and a Subdirectory?
The distinction is structural, but the SEO implications run deeper than the URL itself.
A subdirectory (also called a subfolder) lives on your main domain:
example.com/uk/
example.com/us/
example.com/de/
All regional content shares one domain. One set of backlinks. One crawl budget allocation. One domain authority profile.
A subdomain places each region on its own host:
uk.example.com
us.example.com
de.example.com
Each subdomain is treated by Google as a largely separate entity. It builds its own authority, has its own crawl patterns, and can be verified as its own property in Google Search Console.
There’s also a third option: country-code top-level domains (ccTLDs) like example.co.uk, example.de, or example.com.au. These send the strongest geo-targeting signal but require purchasing and maintaining separate domains entirely. Amazon uses this approach. For most businesses, the cost and complexity of managing multiple domains rules ccTLDs out, which is why the subdomain vs. subdirectory debate gets most of the attention.
How Does Google Actually Treat Subdomains vs. Subdirectories?
Google’s John Mueller has addressed this directly: “Google Search handles subdomains and subdirectories equally, so do whatever works best for your setup.” That’s the official line, and for basic indexing purposes, it’s accurate. Google can crawl and rank content in either structure.
But “equally” doesn’t mean “identically in practice.” The mechanics differ in ways that affect real-world performance.
Domain authority distribution. Subdirectories consolidate all link equity under one domain. Every backlink to any regional page strengthens the whole domain. Subdomains don’t get this benefit automatically. A link to us.example.com builds authority for that subdomain. It doesn’t directly boost uk.example.com or the root domain. Over time, this means subdirectory sites tend to accumulate domain-level authority faster, while subdomain sites need independent link-building campaigns for each regional property.
Crawl budget. With subdirectories, Googlebot allocates crawl budget to one domain and discovers all regional content during the same crawl session. Subdomains each receive their own crawl allocation. For large sites, this can be an advantage. A subdomain for your German market won’t have its crawl budget consumed by your English site’s 50,000 product pages. For smaller sites, separate crawl budgets just mean slower discovery across each property.
Google Search Console. Subdirectories can be segmented using the URL prefix property in GSC, but you’re still working within one property. Subdomains get their own verified properties, which gives you cleaner data separation, independent sitemaps, and the ability to use GSC’s international targeting settings per property.
When Does a Subdirectory Make More Sense?
Subdirectories are typically the stronger choice when you want to maximize the SEO value of a single domain, and your team structure supports centralized management.
You have existing domain authority you don’t want to dilute. If your root domain has years of backlinks and established rankings, putting international content in subdirectories lets every regional page benefit from that foundation. New markets start with a head start instead of from zero.
Your international content shares significant overlap. When regional pages differ only in currency, phone numbers, and some localized copy, subdirectories keep the architecture simple. Internal linking between regional versions happens naturally within one domain.
You have a small to mid-size site. Under a few thousand pages per region, subdirectories keep everything in one crawlable structure without needing separate server configurations, analytics setups, or GSC properties.
Your team is centralized. One CMS, one dev team, one deployment pipeline. Subdirectories fit neatly into this model. HubSpot is a well-known example of this approach, running all international content under subdirectories on a single domain.
The trade-off: everything is coupled. A server issue affects all regions. A bad deployment can break every market at once. And as you add more languages, the single domain accumulates complexity that can slow down development cycles.
When Does a Subdomain Work Better?
Subdomains earn their complexity when your international operations are genuinely distinct, not just translations of the same pages.
Each market operates semi-independently. Different content teams, different CMSs, different hosting requirements. If your US team ships features on a Tuesday cadence and your German team deploys on Thursdays, subdomains let each market run its own infrastructure without coordination overhead.
You need geo-specific server locations. Subdomains can be pointed to different servers or CDN nodes. If latency matters for your product (think: e-commerce checkout, SaaS applications), hosting de.example.com on European servers and us.example.com on US servers gives you cleaner performance optimization.
You want clean data separation from day one. Separate GSC properties, separate analytics views, separate Search Console sitemaps. If you’re reporting to different regional stakeholders who care about their market’s performance in isolation, subdomains provide that structural separation without workarounds.
You plan to scale significantly. Wikipedia runs subdomains for each language (en.wikipedia.org, de.wikipedia.org). That’s an extreme case, but the principle holds. When each regional site will eventually have tens of thousands of pages, subdomains prevent the root domain from becoming unmanageably large.
The trade-off: authority building starts fresh for each subdomain. You’re running what are effectively separate SEO campaigns for each regional property.
How Does Internal Linking Differ Between the Two?
Internal linking is where the subdirectory advantage is most tangible.
With subdirectories, a link from example.com/us/seo-guide/ to example.com/us/technical-seo/ is a standard internal link. It passes full link equity and keeps users within one domain. Cross-regional links (example.com/us/guide/ linking to example.com/uk/guide/) are also internal links. The entire site is one interconnected structure.
With subdomains, a link from us.example.com/seo-guide/ to uk.example.com/seo-guide/ is technically a link between separate hosts. Google doesn’t treat it as a purely external link the way it would a link to a completely different website, but it also doesn’t carry the same weight as a true internal link. The equity transfer is muddied.
This has practical implications for content strategy. If you write a comprehensive guide on your US subdomain and link to it from your UK subdomain, the link value is diluted compared to the same link within a subdirectory structure. Subdomain architectures need stronger independent content strategies per market, because cross-market linking doesn’t compound as effectively.
How Do Hreflang Tags Work With Each Structure?
Hreflang implementation is required regardless of which structure you choose. The syntax is identical. Each page points to its regional equivalents using tags. What changes is the operational complexity.
With subdirectories, all hreflang tags reference URLs on the same domain. Deployment is simpler since one CMS generates all the tags. Validation is faster since one crawl covers everything. When a page is added or removed, updating the hreflang cluster happens in one place.
With subdomains, hreflang tags cross between separate hosts. Each subdomain’s CMS or template system needs to generate tags pointing to every other subdomain. If different teams manage different subdomains, coordinating hreflang updates becomes a communication problem, not just a technical one. Missing return links (where Page A points to Page B but Page B doesn’t point back) are the most common hreflang failure, and subdomains multiply the chances of it happening.
For a deeper breakdown of hreflang implementation methods and common mistakes, we’ve covered that fully in our hreflang tags guide.
What About Canonical Tag Considerations?
Both structures need self-referencing canonical tags on every page. With subdirectories, this is straightforward since the canonical URL and the page URL share the same domain. With subdomains, the critical rule is the same: each page’s canonical must point to itself, not to the equivalent page on another subdomain. A canonical tag on us.example.com/pricing/ pointing to example.com/pricing/ would tell Google your US page is a duplicate of the root domain page, effectively wiping the US page from the index.
This is a mistake that happens more often with subdomains than subdirectories, because the mental model of “one main site with regional versions” leads teams to treat the root domain as the canonical source. Each subdomain is its own site. Canonicals stay self-referencing within each one.
How Do You Decide? A Practical Framework
Stop thinking about which structure is “better for SEO.” Think about which one your organization can actually maintain.
Choose subdirectories if:
You have strong existing domain authority and want every market to benefit
Your team is centralized with one CMS and deployment process
Your regional content is similar with localized variations
You don’t need independent server infrastructure per market
You want the simplest possible hreflang and canonical management
Choose subdomains if:
Each market operates with different teams, CMSs, or hosting needs
You need clean data separation for reporting to regional stakeholders
Your regional content is substantially different, not just translated
You’re willing to invest in independent authority building per market
Scale will eventually require infrastructure isolation
Choose ccTLDs if:
Brand trust in local markets is paramount (financial services, government-adjacent)
You have the budget for separate domain purchases and maintenance
Local search engines beyond Google are a significant traffic source
For most mid-market companies expanding into one or two new regions, subdirectories are the path of least resistance. For enterprises with regional teams and substantial content differences across markets, subdomains provide the operational flexibility that outweighs the authority consolidation trade-off.
What About Migration Between Structures?
If you’ve already launched with one structure and you’re questioning whether to switch, the answer is almost always: don’t. Migration between subdomains and subdirectories is functionally a site migration. Every URL changes. Every backlink needs a redirect. Every hreflang tag needs updating. Rankings will fluctuate during the transition, and recovery isn’t guaranteed to be complete.
The SEO cost of migration only makes sense if your current structure is actively preventing growth. If your subdomain sites can’t build authority despite sustained link building, or your subdirectory setup is creating deployment bottlenecks that slow content production across all markets, those are valid reasons to move. “I read that subdirectories are better for SEO” is not.
For guidance on handling URL changes without destroying your rankings, our website migration SEO guide covers the full process.
What Does a Hybrid Approach Look Like?
Some organizations use both structures. The main commercial site runs in subdirectories (example.com/uk/, example.com/de/) while a support portal or community forum runs on a subdomain (support.example.com). This works when the content types are genuinely different, not when it’s an attempt to get the best of both worlds for the same content.
A true hybrid for international SEO, where some markets use subdirectories and others use subdomains, creates maintenance complexity that rarely pays off. Hreflang management becomes harder. Internal linking rules differ by market. The team has to maintain expertise in both architectures. Pick one structure for your international content and apply it consistently.
Getting the Structure Right Before You Scale
The URL structure question matters most at the start. Once you’ve built content, earned backlinks, and established rankings under one structure, switching carries real cost. Spend the time upfront to match your structure to your organization’s resources, team model, and growth plans.
Both subdomains and subdirectories can rank well internationally. Google doesn’t preference one over the other. What Google does reward is consistent implementation: clean hreflang, self-referencing canonicals, strong internal linking, and content that’s genuinely localized for each market. Get those right, and the URL structure becomes the container, not the constraint.
If you’re planning an international expansion and need help choosing and implementing the right structure, our technical SEO team can audit your current setup and build a foundation that scales with your business.
