Guides2 February 20267 min read
Multilingual websites for EU markets: i18n done right
Selling across EU borders in English only leaves money on the table — most Europeans buy in their own language. The architecture, SEO and translation playbook.
A multilingual website done right means three things: every language lives on a clean URL structure with correct hreflang tags, translations are written for the market rather than run through a machine and forgotten, and all of it ships from one codebase your team can actually maintain. Done wrong, it means duplicate-content penalties, half-translated checkouts and a maintenance nightmare. The gap between the two is architecture, decided on day one.
Why English-only quietly caps your growth
Research has shown it for years: roughly three quarters of European consumers prefer buying in their native language, and a large share simply will not purchase from a site they cannot read. English works for pan-EU B2B software; it fails for services, retail and anything local. If your competitors serve Riga in Latvian and you serve it in English, the ranking — and the sale — goes to them, because search engines serve searchers in the searcher’s language.
The architecture that works
- URL structure: language in the path (/de/, /fr/) on one domain concentrates authority and simplifies analytics — the right default for most businesses.
- hreflang tags: every page declares its language variants, so Google serves the German page to German searchers instead of flagging duplicates.
- One codebase, many locales: components and design stay unified; only content varies. Adding market number four costs days, not a rebuild.
- Everything translated: checkout, forms, error messages, emails. A translated homepage with an English checkout converts like an English site.
Translation: the machine-plus-human play
Machine translation in 2026 is good enough to draft with and dangerous enough to publish unreviewed. The workable pipeline: machine-draft, native-speaker review for the pages that persuade (homepage, services, checkout), and market-level keyword research before translating a single heading — because Germans and Estonians do not search in translated English phrases, and word-for-word translation of your keywords is how multilingual SEO fails invisibly.
We build this daily
Our own client work runs this exact architecture — recruit24.ee serves Estonian, Russian and English from one codebase, each language ranking in its own market from a single build pipeline. The pattern scales from three languages to ten without changing shape: static generation per locale, headless content, edge delivery everywhere.
Frequently asked questions
Subdomains, subfolders or separate domains per country?
Subfolders (/de/) win for most businesses: one domain accumulates all authority, and maintenance stays sane. Separate country domains only make sense with genuinely separate local businesses and budgets to build authority per domain.
Is machine translation enough for SEO?
For long-tail content, reviewed machine translation performs fine. For commercial pages, invest in native review and local keyword research — the pages that make money deserve language that sells, and engines increasingly detect unedited machine output.
What does adding a language cost?
On a properly internationalized codebase: translation costs plus days of integration work. On a site built single-language: often a partial rebuild — which is why the architecture decision belongs at project start, even if you launch with one language.
Written by the iweb.eu studio — twelve years of building fast websites, sharp brands and search visibility. Talk to us about your project.