Multilingual Websites: How Not to Lose Clients Over Language

We run our own site in five languages — English, Ukrainian, Russian, Slovak, and Czech — because that is where our clients come from. A multilingual site looks like a translation problem. It is not. It is a product problem: every language is a separate version of the site, and each one can quietly lose clients if you treat it as a copy-paste job.

Here are the mistakes we see most often, and what to do instead.

Auto-detection: helpful or hostile?

Automatically switching visitors to their browser language sounds courteous. In practice it goes wrong constantly. Expats get a language they don’t want. A shared family laptop shows grandma a version she never asked for. The back button breaks because the redirect fires again.

The pattern that works: show the site in the default language, offer a visible switcher, and remember the choice. Geo-IP plus a browser hint can be a suggestion — a banner, not a hijack. Forcing a language on a first-time visitor creates frustration before they have read a single sentence of your pitch.

Machine translation vs. quality translation

Machine translation has improved, and for a quick sense of a foreign email it is fine. Publishing raw machine output on your site is a different thing. It produces grammatically plausible sentences with wrong terminology, wrong tone, and sometimes wrong meaning — the kind of text that makes a careful buyer leave.

The workable middle: machine translation as a first draft, then a human editor who knows the industry for the final pass. Full professional translation for the pages that sell — homepage, services, pricing, contact. The deeper a page sits in your funnel, the less tolerance there is for awkward phrasing.

hreflang and local versions

Search engines need to know which page serves which language and region. That is what hreflang does: it links the English, Slovak, and Czech versions of the same page so Google does not treat them as duplicate content or show Slovaks the English version.

Rules we follow on our own projects: every language version must be reachable by a URL such as /en/ or /sk/, every page must link to its siblings, hreflang tags must be bidirectional, and there must be a correct x-default fallback. Miss one of these and you get the classic symptom: the wrong language ranking in the wrong country.

Note that a language and a locale are not the same thing. English for the UK and English for the US differ in spelling, currency, and date formats. Decide per market, not per language.

Cultural differences and typical mistakes

Beyond words: prices in local currency, formats that match local habit, examples the reader actually recognizes, images that don’t feel imported. A site can be perfectly translated and still feel foreign.

The most common mistakes, condensed:

• Translating the navigation labels but forgetting buttons, forms, error messages, and the checkout — the exact spots where a client is about to commit.
• Letting translations drift: the English page gets updated, the Slovak one keeps selling last year’s offer for months.
• Building five languages when two would do, then watching three of them rot. Launch a language only if you can maintain it.
• Using flags as language selectors. A language is not a country — think of Austrian, Swiss, and German users of ‘German’.

A multilingual site is a commitment, not a feature. One extra language roughly doubles your content workload forever. Do it for the markets you’ll actually serve — and serve them properly.