International URL architecture

Multilingual URL structure: subdirectories, subdomains, and country domains

Compare /fr/page, fr.example.com/page, country domains, root English, and /en/ so you can choose a URL model that fits your product and SEO goals.

Build with Altified Read the docs

/ The short answer

There is no universal best multilingual URL structure. Subdirectories are usually the simplest way to consolidate authority; subdomains provide stronger separation; country domains can support regional strategy but add operational cost. Choose one model deliberately and apply it consistently.

/ 01

Subdirectories

Use /fr/page when one domain should own the language set

Subdirectories keep language versions under the same domain and are usually straightforward to route, deploy, measure, and connect with hreflang. They are a strong default for many product teams.

Example: example.com/fr/pricing.
Simple to share one deployment and analytics property.
Easy to generate from a locale segment in Next.js.

/ 02

Subdomains

Use fr.example.com when languages need stronger separation

Subdomains can make regional ownership, infrastructure, or operational separation explicit. They require DNS, certificates, origin, cookie, analytics, and Search Console decisions for each host.

Example: fr.example.com/pricing.
Useful when regional sites have distinct teams or infrastructure.
Treat each host as part of the same hreflang cluster.

/ 03

Country domains

Use country domains when regional targeting is strategic

Country-code domains can communicate a market commitment and support region-specific operations, but they add domain, redirect, content, legal, and measurement complexity.

Example: example.fr/pricing.
Best when country operations and content are genuinely distinct.
Do not use a country domain only as a cosmetic language switch.

/ 04

English policy

Decide between root English and /en/ once

Both example.com/pricing and example.com/en/pricing can work. Root English is shorter; an explicit /en/ prefix makes the locale model symmetrical and can simplify route logic. Avoid publishing both without a redirect and canonical policy.

Pick one canonical English pattern.
Redirect duplicate variants.
Make the language switcher preserve the current content path.

Two valid route policies

// One consistent choice:
/en/pricing
/fr/pricing
/de/pricing

// Or hide the default locale:
/pricing
/fr/pricing
/de/pricing

/ Production checklist

Verify the language experience before launch.

The URL model matches hosting and team ownership.
Every language has a stable URL.
Root and locale-prefixed duplicates redirect consistently.
Canonical and hreflang rules are documented.
The sitemap uses one canonical URL per page version.
Language switching preserves the current path and content identity.

/ Frequently asked questions

Questions teams ask before implementing multilingual SEO.

Are subdirectories better than subdomains for multilingual SEO?

Subdirectories are often simpler and consolidate one domain, while subdomains can provide stronger operational separation. The best choice depends on your infrastructure, team ownership, and regional strategy.

Should English use /en/?

Either root English or /en/ can work. Choose one canonical policy, redirect the duplicate, and apply it consistently across routes, canonicals, hreflang, and sitemaps.

Can country domains and subdirectories coexist?

They can, but avoid publishing duplicate regional versions without a clear canonical and hreflang strategy. The more URL models you combine, the more important your ownership and redirect policy becomes.

/ Continue exploring

Build a localization workflow your application can own.

Request access