Technical SEO
International Site Structure and Locale Targeting
A practical guide to choosing ccTLDs, subdomains, subdirectories, language-country paths, x-default pages, canonicals, sitemaps, and locale routing.
International site structure decides where each language or market version lives and how users, crawlers, canonicals, sitemaps, and hreflang find the right URL.
There is no perfect structure for every site. The right choice balances market needs, operations, authority, localization, CMS support, analytics, and long-term maintenance.
Structure options
| Structure | Example | Best Fit | Watchouts |
|---|---|---|---|
| ccTLD | example.de | Distinct country brand, legal entity, or local operations. | Separate domains, migrations, authority split, more overhead. |
| Subdomain | de.example.com | Operational separation or platform limits. | Can fragment ownership and reporting. |
| Subdirectory | example.com/de/ | Centralized management and shared domain authority. | Requires clean routing and governance. |
| Language-country path | example.com/es-mx/ | Same domain, market-specific language and country targeting. | Needs consistent code rules and content maintenance. |
| Parameter | example.com?lang=de | Temporary or utility language switching. | Usually weaker for crawling, sharing, and governance. |
Choose the simplest structure that supports the business reality.
Language and country codes
Use valid codes consistently.
- Language-only pages can use language codes such as
en,es, orfr. - Region-specific pages can use language-region combinations such as
en-gb,es-mx, orfr-ca. - Country and language are not interchangeable.
- Region codes should not be invented.
- URL paths, hreflang, analytics, and sitemaps should use the same locale model.
A clean code convention prevents avoidable hreflang and reporting errors.
x-default decisions
Use x-default when a page is a global fallback, market selector, or default page for users who do not match a specific locale.
Good x-default candidates:
- Global homepage with language selector.
- Market selector page.
- Default English/global page when no localized version exists.
Weak x-default candidates:
- A random market page.
- A page that automatically redirects without user choice.
- A page that is not equivalent to the alternate cluster.
The fallback should be useful when the site cannot confidently choose a localized page.
Canonicals and locale URLs
Localized pages should usually self-canonicalize.
Avoid:
- Canonicalizing every locale to the source-language page.
- Canonicalizing regional versions to a generic language page when regional versions should be eligible.
- Including noindexed pages in hreflang clusters.
- Pointing hreflang to redirected URLs.
Canonicals consolidate duplicates. Hreflang connects alternates. They should support different parts of the same plan, not contradict each other.
Sitemaps
International sitemaps should include canonical, indexable locale URLs.
Options include:
- One sitemap per locale.
- One sitemap per page type with hreflang alternates.
- A sitemap index that groups locale/page-type sitemaps.
Whichever structure is used, it should be easy to audit by locale and page type.
Language switchers
Language and country switchers should:
- Use crawlable links.
- Link to equivalent pages when available.
- Offer a global selector or fallback where appropriate.
- Avoid trapping users with automatic redirects.
- Let users choose another locale even when geolocation suggests one.
- Preserve page context instead of sending everyone to a homepage when equivalents exist.
Switchers are both UX and discovery infrastructure.
Automatic redirects
Use automatic redirects carefully.
Risks:
- Crawlers may not access alternate versions.
- Users traveling or using VPNs may be forced to the wrong market.
- Hreflang validation can become harder.
- Shared URLs can redirect away from the intended page.
If geolocation is used, provide a visible option to change locale and make alternate URLs crawlable.
Migration risks
International restructuring can affect many signals at once:
- URL paths.
- Canonicals.
- Hreflang.
- Internal links.
- Sitemaps.
- Search Console properties.
- Analytics segments.
- Backlinks to old locale URLs.
Use redirect maps and launch QA by locale. International migrations are rarely safe with only a global spot check.
Common mistakes
- Choosing ccTLDs without resources to maintain each domain.
- Using subdirectories but mixing locale conventions.
- Treating language pages as country pages.
- Auto-redirecting users and crawlers away from alternate URLs.
- Using invalid language-region codes.
- Leaving old locale URLs in sitemaps.
- Forgetting localized internal links.
- Measuring all markets as one site.
For implementation checks, use Hreflang QA Checklist and the International SEO Launch Matrix.