Multilingual Website: URLs, hreflang and Translation Done Right
A company website in Estonia is rarely in one language. Customers speak Estonian, Russian and English, and tourism and retail businesses often add Finnish. A multilingual website looks simple: write the copy, translate it, put a language button in the corner. In practice, a few technical choices decide whether each language version can be found in search and whether visitors land in the right place.
This post covers the decisions that matter: URL structure, hreflang, translation, per-language titles and slugs, the language switcher and the sitemap. Our example is our own site, ravien.eu, which runs in Estonian and English.
Who reads your site
Before the technical part, answer a simple question: who reads your site, and in which language do they search?
- Estonian is the default for local customers.
- Russian is the first language of many people in Estonia. If your customers are in Ida-Viru County or Tallinn and the service is local, a Russian page can matter as much as the Estonian one.
- English is needed for foreign customers, tourists, expats living in Estonia and partners.
- Finnish makes sense when customers come from Finland, for example in tourism, accommodation and services.
Every language is its own ongoing work: copy, upkeep, updates. Two languages done well beat four half-done. If a Russian page brings no enquiries because nobody answers in Russian, it isn't helping.
URL structure: subfolder, subdomain or separate domain
Each language version needs its own URL. If the language switches only through a cookie or JavaScript and the address stays the same, search engines usually see just one language. There are three common options:
| Option | Example | Pros | Cons |
|---|---|---|---|
| Subfolder | company.ee/en, company.ee/ru | easy to manage, one domain, one hosting setup | all languages share one domain |
| Subdomain | en.company.ee | languages can be hosted separately | more setup and maintenance |
| Country domain | company.ee, company.fi | clear signal for a specific country | several domains, more cost and admin |
Google describes these options in its guide to multi-regional and multilingual sites. For a small or mid-sized company, subfolders are usually the most sensible choice. Separate country domains make sense when you run as separate businesses in different countries, with different prices, delivery and teams.
Our example: ravien.eu uses subfolders. The English home page is / and the Estonian one is /et; the blog is /blog and /et/blog. One domain, one app, each language at its own address.
hreflang: tell search which page is in which language
hreflang is an annotation that tells search engines these pages are the same content in different languages. That way someone searching in Estonian gets the Estonian page, and someone searching in English gets the English one. The exact rules are in Google's hreflang documentation.
The key points:
- Every language version points to all the others and to itself. If the Estonian page points to the English one, the English page must point back. One-way links don't work.
- Language codes follow ISO 639-1:
et(Estonian),en(English),ru(Russian),fi(Finnish). A common mistake isee, which is actually the code for the Ewe language. - You can add a region, such as
ru-EE, if you have separate Russian pages for different countries. With just one Russian page,ruis enough. x-defaultnames the page to show when none of the languages matches the searcher's. Usually that's the English page or a language picker.- Point to the same content. The Estonian version of a blog post points to the English version of the same post, not to the English blog index.
Our example: the ravien.eu home page has hreflang en → /, et → /et and x-default → /. Each blog post points to its translation, with the English version as x-default. Both languages reference each other and themselves. Every page also sets <html lang> correctly, which helps screen readers and browsers handle the text properly.
Why machine translation alone isn't enough
Machine translation is good these days, and fine for a first draft. It isn't something to publish without a person checking it, for several reasons:
- Terminology. Your products and services have names customers search for. Machine translation may pick a word nobody uses.
- Search terms differ by language. Nobody searches in Russian with a word-for-word translation of an Estonian phrase. For each language, look at what people actually search for.
- Tone. Estonian and Russian both have a formal and an informal "you". The translation has to stick to one choice across the whole site.
- Local content. Prices, delivery, opening hours, phone numbers, examples. A customer from Finland may need different information than one in Tallinn.
- Trust. Clumsy translation tells readers that this language is an afterthought for you. Native speakers notice immediately.
A good workflow: machine translation for the draft, a native speaker edits, then adapt the content for that audience where needed.
Titles, descriptions and slugs in each language
Each language version has to be a complete page, not just translated body copy. That means:
- its own
titleandmeta description, written with that language's search terms; - its own slug, the last part of the URL, in that language;
- translated navigation, buttons, forms and error messages, not just the main text;
- image alt text in the right language;
- Open Graph data, so shares on social media show the title and image in the right language.
Our example: our blog posts have a separate slug in each language. The post on building a website is /blog/custom-website-vs-template in English and /et/blog/kodulehe-tegemine-eritellimus-voi-mall in Estonian. Slugs use ASCII only, so õ, ä, ö and ü become o, a, o and u. Accented letters are allowed in URLs, but when shared they often turn into unreadable encoded text.
Language switcher: simple, visible, no forcing
The language button looks like a small detail, but a few rules are worth following:
- Don't redirect automatically by IP address. An English speaker living in Tallinn, or an Estonian in Finland, doesn't want the site to decide for them. Google's guidance also recommends avoiding automatic redirects, because they can stop both visitors and crawlers from seeing all language versions.
- The switcher should lead to the translation of the same page, not to the other language's home page. If there's no translation, the index of the same section is a sensible fallback.
- Name languages in their own language: "Eesti", "English", "Русский", "Suomi". Skip flags: a flag stands for a country, not a language.
- Make it easy to find, usually in the header, and make sure it works on phones and with a keyboard.
Our example: the ravien.eu header has a language link (ET or EN). On a blog post it goes to the same post's translation when there is one, and otherwise to the other language's blog index. There's no automatic redirect: open ravien.eu and you get English, open ravien.eu/et and you get Estonian.
Sitemap with language alternates
hreflang can go in each page's HTML head, and also in the XML sitemap, where every URL lists all its language versions. That's handy when you have many pages, and it helps search engines find the language versions quickly.
Our example: ravien.eu does both. Every page's head carries hreflang links, and the sitemap lists the Estonian and English addresses for the home page, the blog and every post. Because both language versions of a post live in the same folder, the system pairs them automatically and nobody has to maintain the links by hand.
Checklist
- We picked languages based on who our customers are, and we have people who answer enquiries in those languages.
- Each language has its own URL (preferably a subfolder).
- hreflang links are two-way, include a self-reference and an
x-default. - Language codes are correct (
et, notee). - A native speaker has reviewed the translations.
- Each language has its own title, description and slug.
- Navigation, forms, error messages and alt text are translated.
- The switcher leads to the same page's translation, and there's no IP-based redirect.
- The sitemap includes every language version.
When you don't need a multilingual website
Not every business needs several languages. If your customers all speak Estonian and the service is local, one very good Estonian site is the better choice. If you add a language but can't keep it updated, it fills up with stale information and does more harm than good. And don't add a language "just in case" when there's nobody to answer enquiries in it.
For more on what to weigh when building a site in the first place, see Custom Website vs Template: When Is Custom Worth It?
Summary
A multilingual website works when each language has its own address, the hreflang links are right, a person has reviewed the translations and visitors can choose the language themselves. The technical part is small if it's done right from the start. Fixing it later is always more work.
If you're planning a new multilingual website, or the language versions of your current site aren't working the way they should, get in touch. We'll look at what's in place today and tell you honestly what's worth changing.
Have a workflow that should work better?
Start a conversation