A multilingual website for the EU market: what breaks in translation
- The common mistake is translating the copy and assuming the site is now ready for another market.
- Technically the three that matter most are URL structure, hreflang and separate meta tags per language.
- European buyers check different things: legal details, return terms, accessibility, payment method.
- Each additional language adds roughly 25–40% to the project — and not only for the translation.
Ukrainian companies are looking at Europe more and more, and almost all of them start with an English version of the site. It is the right first step, usually taken the wrong way.
The first decision: URL structure
| Option | Example | When it fits |
|---|---|---|
| Subdirectory | site.com/en/ | Nearly always: all the domain’s authority works for every language |
| Subdomain | en.site.com | When the markets differ sharply in product and team |
| Separate domain | site.de | When there is a local legal entity and a local brand |
For 90% of companies the answer is the subdirectory. A separate domain looks impressive, but it means starting authority from zero and maintaining a second website.
The technical minimum
- hreflang on every page, reciprocal, with
x-default. Without it Google shows a European visitor the Ukrainian version. - Separate title and description per language. Machine-translated meta tags are the fastest way to look improvised.
- Self-referencing canonical inside each language, not pointing at the main version. A frequent error that quietly keeps the English version out of the index.
- A language switcher without automatic IP redirects. The crawler arrives from a US server and never sees the Ukrainian version.
What breaks in the layout
German runs about a third longer than Ukrainian; English runs shorter. That means buttons that no longer fit, headings that wrap badly, and empty space where the grid used to be tight.
Then the details nobody notices until launch: date format, decimal separators, phone formats, units. For a store, add currency — showing a European buyer a price in hryvnia is a guaranteed bounce.
Machine translation in 2026 is very good — right up to the point where it has to translate the names of your own services and products. Industry terminology and brand names need a human pass, or the customer reads the description twice.
What a European buyer checks and a local one does not
- Legal details. Who you are, where you are registered, how to reach you. A Contacts page with nothing but a form reads as a warning sign.
- Returns and delivery terms, written out, not “ask the manager”.
- Privacy policy and cookie handling. Expectations are higher than on the domestic market.
- Accessibility. For some companies this is already a formal requirement — we have a separate piece on it.
- A familiar way to pay, not only local providers.
What it costs
Each additional language adds roughly 25–40%: translation and proofreading, separate meta tags, a second pass over the layout, hreflang setup, separate forms, emails and legal pages.
It is one-time work, though. Maintaining a bilingual site costs only marginally more — provided it was built properly from the start rather than having English bolted on later.
We build multilingual sites for the European market — correct URL structure, hreflang, and copy that reads as though a native speaker wrote it.