In Estonia a multilingual website is not a luxury but often simply a necessity: Estonian-, Russian- and English-speaking customers search for the same service in different languages. A site with badly handled translations, however, confuses both search engines and visitors. Here is how to build a multilingual website properly.
Why a multilingual site pays off
- More customers: some people search for a service in Russian or English and an Estonian-only page doesn't fit them.
- Less competition: Russian and English queries are often answered by fewer high-quality pages.
- Trust: people trust a company that speaks their language.
- International clients: e-residents and foreign partners need information in English.
URL structure: how to place the languages
| Option | Example | Pros | Cons |
|---|---|---|---|
| Subfolder | yoursite.ee/en/, yoursite.ee/ru/ | One domain, shared authority, easy to manage | Needs a clean structure |
| Subdomain | en.yoursite.ee | Managed separately | Authority is split, more complex |
| Country domain | yoursite.com, yoursite.ru | Strong local signal | Many domains, expensive and laborious |
| URL parameter | yoursite.ee?lang=en | Quick to do | Poorly indexed, not recommended |
For most Estonian companies the best fit is a subfolder: Estonian on the main address and other languages in folders (/en/, /ru/). That is exactly how this website is built.
hreflang: how Google knows which language is which page
hreflang is a markup that tells a search engine that the language versions of the same page belong together. Each language version must point to all the others and to itself. Example:
<link rel="alternate" hreflang="et" href="https://yoursite.ee/teenused/">
<link rel="alternate" hreflang="en" href="https://yoursite.ee/en/services/">
<link rel="alternate" hreflang="ru" href="https://yoursite.ee/ru/uslugi/">
<link rel="alternate" hreflang="x-default" href="https://yoursite.ee/teenused/">- The markup must be reciprocal: if A points to B, B must point to A.
- Each page also points to itself.
x-defaultis the default version (for us, Estonian).- The canonical of each language page must point to that page itself, not to another language.
- The same information can also go in the sitemap.
Common mistakes on multilingual sites
- Automatic redirects based on location or browser language. They can mislead both search engines and visitors. Offer a language switcher instead.
- Machine translation without review. Badly translated text hurts trust and rankings.
- Untranslated parts: the menu, forms, error messages, meta descriptions and image alt text.
- Missing or broken hreflang, so Google shows the wrong language.
- The same page in three languages at one address (text swapped with JavaScript), which search engines don't index separately.
- A language switcher that always goes to the homepage instead of the same page in the other language.
Content: translation or localisation
A good multilingual site is not a word-for-word translation. In each language you should use the phrases people really search for there (for example "kodulehe tegemine" in Estonian, "создание сайтов" in Russian, "website development" in English) and adapt examples, prices and contact details. That is why each language on our site has its own titles, meta descriptions and, where needed, adapted addresses.
What affects the cost of a multilingual site
- The number of languages and the volume of pages.
- Translation quality: professional translation or content written by you.
- Language switcher, hreflang, sitemap and SEO setup.
- Maintenance: every change has to reach every language.
Price ranges: website cost in Estonia 2026. Our pricing is here.
Pre-launch checklist
| Check | Why |
|---|---|
| Each language is on its own address | Search engines can index them separately |
| hreflang is reciprocal and includes itself | Google shows the right language |
| Canonical points to itself | Prevents languages being mixed up |
| The switcher goes to the same page in the other language | Better user experience |
| Meta descriptions and titles are translated | The search result is in the right language |
| All language versions are in the sitemap | Faster discovery |
| The page has an html lang attribute (for example lang="ru") | Accessibility and correct pronunciation in screen readers |
Frequently asked questions
Does an Estonian business need a trilingual website?
If your customers are Estonian-, Russian- and English-speaking, yes, at least for the main pages. Start with Estonian and one other language and expand as needed.
Is machine translation acceptable?
As a draft yes, but always have a person review it. Poor translation hurts trust and rankings.
Is a multilingual site bad for SEO?
No, if it is done correctly: separate addresses, hreflang and quality content in every language.
How much does a trilingual website cost?
The price depends on the page volume and the translations. Our Business package (€1,190) is a multi-page website; we give an exact multilingual quote in writing.
Need an Estonian, Russian and English website?
We build multilingual sites with the right structure and SEO. We reply within one day.