hreflang and International Domains: How to Structure Multilingual Sites
Expanding a site to serve multiple languages or regions requires a decision upfront: how will the URL structure reflect that? The choice affects both implementation complexity and SEO performance, and it is difficult to change later.
The Three URL Structures
1. Country-Code TLDs (ccTLDs)
Each country gets its own domain:
example.com— USexample.co.uk— UKexample.de— Germanyexample.fr— France
SEO signal: strongest country-targeting signal available. Google and other search engines treat ccTLD as a hard geographic signal.
Cost: registering and maintaining each ccTLD, plus managing separate hosting, deployments, and link-building per domain. PageRank does not automatically flow between them — each domain starts with zero authority and must build independently.
When it makes sense: large organisations with dedicated teams per market, where local brand presence and strong geo-targeting justify the overhead.
2. Subdomains
Regional content sits on subdomains of the main domain:
us.example.comuk.example.comde.example.com
SEO signal: Google officially treats subdomains as separate sites for international targeting when combined with hreflang, but they do not benefit as strongly from ccTLD geo-signals.
Cost: simpler than ccTLDs — one domain registration — but Google Search Console requires separate property verification per subdomain to set geographic targeting.
When it makes sense: mid-size organisations that want geo separation without the domain acquisition and SEO rebuilding cost of ccTLDs.
3. Subdirectories
All regional content lives under the main domain:
example.com/us/example.com/uk/example.com/de/
SEO signal: all paths benefit from the main domain's authority. Link equity is shared. This is the fastest path to international ranking for sites with existing domain authority.
Cost: one domain, simpler infrastructure, but less precise geo-targeting signal than ccTLDs.
When it makes sense: most growing businesses and content sites. The authority consolidation benefit usually outweighs the weaker geo-signal, particularly outside of hyper-competitive local markets.
hreflang — What It Does and Doesn't Do
hreflang is an HTML/sitemap attribute that tells search engines which version of a page to serve to which audience:
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" />
What it does: prevents duplicate content penalties when the same page exists in multiple versions. Signals to Google which URL to rank for which locale.
What it doesn't do: guarantee the right version ranks in every market. It is a hint, not a directive. If your German page has weak content and no local backlinks, hreflang alone won't make it rank in Germany.
Common implementation errors:
- Missing the reciprocal — every alternate URL must reference all other alternates including itself
- Mismatched
hreflangvalues (en-GBin link buten-gbin sitemap — case inconsistency) x-defaultpointing to a redirect rather than a canonical page- Not including
hreflangin XML sitemaps for large sites (page-level tags are preferred but sitemaps scale better)
Domain Acquisition for International Expansion
Before launching a new regional TLD, verify:
- The ccTLD is available for your brand name
- No prior registration that could cause brand confusion
- Registration rules for the ccTLD — some require local presence or entity registration (
.derequires a German postal address;.carequires Canadian presence)
BatchDomain can check your brand name across multiple ccTLDs simultaneously. A single run across .co.uk, .de, .fr, .es, .com.au, .ca gives you the availability picture before you commit to a ccTLD strategy.
Note: some ccTLDs return "no RDAP server" in batch results — that means RDAP is not yet supported for that TLD and availability needs to be verified directly at the relevant registry.