Multilingual websites: when you actually need one
In Estonia the question of languages comes up early in almost every web project. Estonian is a given, but should you add Russian, English, or both? More languages can open real markets, but each one is a permanent cost in translation and upkeep. The honest answer is that it depends entirely on who your customers are, and this is how to decide.
When a second or third language pays off
The test is simple: do you have, or want, customers who do not read Estonian comfortably? If yes, speaking their language is worth real money. If no, you are paying to maintain pages nobody needs.
In Estonia, Russian is the obvious case. A large share of the population uses Russian as a first language, and for many local services, retail and consumer businesses, a Russian version reaches real local buyers.
English matters when you serve tourists, expats, international clients or other businesses abroad. A B2B software firm, a tourism operator or a law office working with foreigners has a clear reason for English.
If you are a local trade serving only Estonian-speaking neighbours, a single Estonian site is often the right and most cost-effective answer. More languages would be effort spent on visitors you do not have.
When it is not worth it
A multilingual site is a long-term commitment, not a one-off translation. Every new page, price change or campaign now has to be done in every language, forever.
Half-finished multilingual sites are common and damaging. A visitor who switches to English, hits an Estonian page, then a broken link, trusts you less than if you had simply stayed in one language.
Auto-translation widgets that machine-translate the whole site on the fly look cheap and easy, but they often produce clumsy, error-filled text that hurts your image and does little for search ranking.
If you cannot commit to keeping a language version complete and current, it is usually better not to offer it at all.
Doing it technically right with hreflang
When you do go multilingual, the technical setup matters for both search engines and users. The key tool is the hreflang tag, which tells Google that a page exists in several languages and which to show to whom.
- Give each language its own real, crawlable URL, for example a /en/ or /ru/ path, rather than swapping text with JavaScript on one address.
- Add hreflang tags so each language version points to the others, helping Google serve the right one to the right searcher.
- Let users switch language easily and obviously, and remember their choice so they are not thrown back to the default on every page.
- Translate the metadata too, not just the visible text. Page titles and descriptions in the right language improve how you appear in local search results.
Translation quality is the whole point
The reason to offer a language is to speak to people properly in it, so a sloppy translation undermines the entire effort. Awkward, obviously machine-translated text can feel worse than no translation at all.
Use a human translator, or at least a fluent human editor over a machine draft, especially for the pages that sell: your homepage, services and contact pages.
Localise, do not just translate word for word. Examples, currency, references and tone should fit the reader's context, not read like a literal conversion of the Estonian.
Pay particular attention to the calls to action and forms. These are where the visitor decides to act, and clumsy wording there costs you directly.
Budget for the upkeep, not just the launch
The launch translation is the cheap part. The real cost is every future update, multiplied by the number of languages you run.
Before adding a language, ask honestly who will keep it current. A new service, a seasonal offer or a policy change all have to be reflected everywhere, or the site slowly drifts out of sync.
A clean approach is to start with the languages you can truly support well, and add another only when there is clear demand and a plan to maintain it.
Two complete, accurate languages beat four neglected ones every time. It is better to serve fewer audiences properly than many audiences badly.
FAQ
Should an Estonian business default to adding English?+
Only if you have a real audience for it: tourists, expats, international clients or B2B customers abroad. If everyone you serve speaks Estonian or Russian, English may add cost without adding customers. Let your actual market decide, not a sense of obligation.
Is automatic machine translation good enough now?+
It is a useful starting point but rarely a finished product for the pages that matter. Machine output still produces errors and awkward phrasing that can hurt trust and ranking. Use it to draft, then have a fluent human edit the important pages.
Does a multilingual site help my Google ranking?+
It can, when done properly, by letting you rank for searches in each language. But it only helps if the translations are genuine, the pages are real and crawlable, and hreflang is set up correctly. A half-built multilingual site can confuse search engines and hurt you.