Multilingual site 2026 — picking a structure
/en/, en.example.com, or ?lang=en — three approaches to multilingual sites. SEO and ergonomics differ.
Adding a second language to a site looks like a translation task. In practice the first decision is structural: where the translated pages live in your URL scheme. That choice affects how search engines index each version, how much infrastructure you maintain, and how painful it is to change later. Moving languages to a different structure after launch means redirects, lost signals and weeks of recrawling.
Most projects choose between three options. A fourth one is for large international businesses.
Option 1: subdirectories
example.com/en/, example.com/de/, with the main language at the root or in its own folder.
- + One domain, so every language version builds on the same domain reputation and links.
- + hreflang is straightforward to set up.
- + One certificate, one analytics property, one Search Console property.
- − All languages share one server and one deployment. You can't easily host the German version in Germany and the English one elsewhere.
- − A technical problem on the domain hits every language at once.
This site uses that scheme: Russian at the root, English under /en/.
Option 2: subdomains
en.example.com, de.example.com.
- + Each language can live on its own hosting, even on its own stack.
- + Handy when different teams own different regions.
- − Search engines tend to treat subdomains as more separate than folders, so each version may need more SEO work of its own.
- − More setup: certificates, analytics and Search Console properties for each.
Option 3: URL parameters
example.com/?lang=en.
- + The easiest to implement in many frameworks.
- − Google's own guidance on multilingual sites recommends against it. Parameter URLs are easy to duplicate, easy to lose in links, and harder to segment in reports.
- Acceptable for admin panels, internal tools and pages that don't need to rank.
Option 4: country domains
example.de, example.fr. A country-code domain clearly tells search engines which country a site targets, and it can build local trust. It also means separate domains to buy, renew and grow from scratch. It makes sense for companies with real operations in each market, rarely for a small business adding English.
Required regardless of structure
- hreflang annotations on every translated page, listing all language versions including the page itself. They must be reciprocal: if the English page points to the German one, the German page must point back. You can put them in the HTML head, in HTTP headers or in the sitemap.
- x-default for visitors whose language you don't target. Often that's a language selector or the main version.
- Correct language codes. ISO 639-1 for the language (
en,de), optionally with an ISO 3166-1 region (en-GB). Writingen-UKis a common error. - Translated metadata. Titles, descriptions, alt text, and URLs where practical, not just the body text.
- No forced redirects by IP or browser language. Google advises against them: crawlers may never see some versions, and travelers or expats get the wrong language. Suggest a version with a dismissible banner, let people choose, and remember the choice.
A minimal hreflang set for one page looks like this:
<link rel="alternate" hreflang="ru" href="https://example.com/services/">
<link rel="alternate" hreflang="en" href="https://example.com/en/services/">
<link rel="alternate" hreflang="x-default" href="https://example.com/services/">
Common mistakes
- Pointing hreflang at pages that redirect or return 404. Only reference versions that are actually published.
- Machine-translating everything and publishing it unedited. Thin, awkward pages can do more harm than good.
- Half-translated pages: English headings over Russian body text, or navigation left in the original language.
- Canonical tags on translated pages pointing to the original, which tells search engines to ignore the translation.
Our recommendation
For most businesses, subdirectories. They give the best balance of SEO strength and operational simplicity. Pick subdomains when there's a concrete infrastructure reason, and country domains only when you have real local operations. For the application side of localization, such as string catalogs, plurals and date formats, see the web app i18n stack. We build multilingual corporate websites and add languages to existing sites as part of a redesign.
Planning a second language for your site? Reach us on Telegram or MAX.
Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.
Message on Telegram → Message on MAX