Multilingual site 2026 — picking a structure

Multilingual site structure has SEO and operational consequences. Three options:

1. Subdirectory: example.com/en/, example.com/de/, example.com/ for default.

• + Single domain — inherits SEO authority.
• + hreflang works cleanly.
• + One certificate, one analytics property, one Search Console.
• − All languages share global ranking — can't optimize each independently.

2. Subdomain: en.example.com.

• + Independent hosting per language.
• + Infrastructure flexibility.
• − Search engines see them as separate sites — separate SEO effort.
• − Multiple certificates, analytics, etc.

3. URL parameter: example.com/?lang=en.

• − Bad for SEO — Google doesn't reliably index parameterized URLs.
• + Easiest to implement.
• OK only for admin panels and SEO-irrelevant pages.

Required regardless of choice:

• hreflang tags linking translations.
• x-default for users outside targeted locales.
• Sitemap per language or unified with lang annotations.
• DON'T auto-redirect by IP. Google penalizes forced redirects. User chooses, you remember.

For most projects: subdirectory. Best balance of SEO and operational simplicity.