International URL Structure: ccTLDs, Subdomains, and Subdirectories
Last updated
The URL structure you choose for an international site is one of the most consequential technical decisions in any international SEO strategy. It determines how Google understands your regional targeting, whether link equity is consolidated or fragmented across your properties, and how much maintenance overhead you take on as you add markets.
The four options
Country-code top-level domains (ccTLDs)
Each country gets its own domain: example.co.uk for the UK, example.de for Germany, example.fr for France. Google automatically associates ccTLDs with their respective countries. This is the strongest geo-targeting signal available, and no additional configuration is needed.
The tradeoff is authority. Each ccTLD is a separate domain, which means a separate crawl budget, a separate link profile, and a separate Search Console property. A backlink to example.co.uk does not benefit example.de. For businesses entering a new market, starting from zero authority on a new ccTLD is a significant disadvantage against established local competitors.
ccTLDs make sense when:
- Legal or regulatory requirements mandate a distinct local domain
- The brand operates under genuinely different names or identities in each country
- The business can sustain separate SEO programmes for each domain
Subdomains
Each market gets a subdomain: uk.example.com, de.example.com. Google treats subdomains as separate properties for geo-targeting purposes (they can be targeted individually in Search Console), but they do not receive the automatic country association that ccTLDs do.
Link equity does not consolidate across subdomains as effectively as it does with subdirectories. Links pointing to de.example.com primarily benefit that property, not the root domain. Subdomains are a viable option when technical constraints make subdirectories difficult, but they offer no advantages over subdirectories for SEO purposes.
Subdirectories
All markets live under a single domain: example.com/uk/, example.com/de/. This is the recommended approach for most sites.
Advantages:
- Link equity accumulates on a single domain. A link to any page on
example.combenefits every international variant. - A single domain means one hosting setup, one SSL certificate, and one primary Search Console property (with sub-properties for each country).
- Country targeting can be applied per-subdirectory in Search Console under International Targeting.
- Lower operational overhead as markets scale.
The main disadvantage is a slightly weaker automatic geo-targeting signal compared to ccTLDs. This is mitigated by setting geo-targeting in Search Console and implementing hreflang annotations correctly.
URL parameters
example.com/?lang=de or example.com/?country=uk. This approach should be avoided for all new builds. URL parameters are harder for Googlebot to crawl consistently, the geo-targeting signal is weak, and the URLs are poor for users and for sharing. If you encounter an existing site using parameters for internationalisation, migrating to subdirectories is a worthwhile investment.
Choosing the right structure
| Structure | Geo-targeting strength | Link equity | Maintenance burden |
|---|---|---|---|
| ccTLDs | Very strong (automatic) | Fragmented | High |
| Subdomains | Moderate | Partially fragmented | Moderate |
| Subdirectories | Moderate (declared) | Consolidated | Low |
| URL parameters | Weak | Consolidated | Not recommended |
For most organisations: use subdirectories. The link equity benefit is significant, especially for sites in competitive markets where accumulating authority takes years. Consolidating that authority on a single domain rather than splitting it across multiple ccTLDs makes each individual page more competitive.
Use ccTLDs when distinct local domains are genuinely required: by legal structure, by brand architecture, or by compliance. Not because they feel more local to your audience.
URL structure and hreflang
Whichever URL structure you choose, it must be implemented consistently before hreflang annotations are added. Hreflang references specific URLs; if those URLs later change (for example, from subdomains to subdirectories), all hreflang annotations need updating simultaneously. Retrofitting a URL migration and a hreflang update at the same time increases the risk of errors considerably.
URL naming conventions
When using subdirectories, there are two main conventions:
Country codes: /uk/, /de/, /fr/. Clear for regional targeting. Use when one language per country.
Language codes: /en/, /de/, /fr/. Better when one language serves multiple countries (English for the UK, Australia, and Canada). Combine with hreflang to specify regional targeting.
Combined codes: /en-gb/, /de-de/, /fr-fr/. Most explicit; best for large sites with both language and regional variants.
Migrating between URL structures
Changing from one URL structure to another is a significant migration with real ranking risk. If moving from subdomains or URL parameters to subdirectories:
- Set up the new URL structure and test it before redirecting any traffic.
- Implement 301 redirects from every old URL to its new equivalent.
- Update hreflang annotations to use the new URLs.
- Update the XML sitemap.
- Update internal links throughout the site.
- Monitor Search Console for crawl errors and ranking changes for several weeks after migration.
Frequently asked questions
Can I mix URL structures across markets? Technically yes, but it creates maintenance complexity and makes hreflang harder to implement correctly. Consistency across all markets is strongly preferable.
Does Google ever ignore the URL structure signal? URL structure is one signal among many. A well-optimised subdirectory with strong local links and correct hreflang will outperform a neglected ccTLD. The structure sets the stage; content and authority determine rankings.
Should I buy all relevant ccTLDs even if I use subdirectories? Buying defensive ccTLDs to prevent brand squatting can be sensible depending on your market. Using them for SEO alongside a subdirectory strategy creates confusion and is unnecessary.