A multilingual website for Estonia should help people access a service in a language they understand. Estonian, Russian and English versions need a consistent structure, quality localisation and convenient switching between corresponding pages.
Adding three flags to the menu is not enough. If the description is translated but the form, email and manager's reply remain in another language, the customer journey breaks. Below is a process for preparing ET, RU and EN versions that accounts for content, SEO and everyday website updates.
Decide who needs each version
Interface language is not the same as citizenship or place of residence. A Russian-speaking visitor may live in Estonia, while an English page may be needed by a local international team. Start with the audience and service conditions, not the assumption that every language represents a separate country.
Determine which services are available in each language and who answers enquiries. If some resources are not yet translated, establish a clear launch sequence. Do not create empty copies of every page. Fully preparing priority services and contacts is better than presenting a mix of languages as a finished version.
For an online shop, add delivery countries, currency, payment methods and support. Translating into English does not itself mean that the shop ships to every country. The terms must be visible before checkout.
Choose a stable URL structure
A practical option for one business is language folders: /et/, /ru/ and /en/. They allow versions to be managed in a shared system. This is not the only valid approach: separate domains or subdomains may be justified by independent markets and teams, but increase the management workload.
Google recommends separate URLs for language versions. Changing only the text at one address through cookies makes discovering all variants harder. Automatic redirection based on an assumed language can also prevent people and crawlers from opening the required page.
Agree on the structure before publication. For example, a service page has three corresponding addresses and the CMS stores their relationship. Section names can be localised, but editors must see which pages form one group. When an address changes, update internal links and language relationships.
Switch languages without losing context
If visitors are reading a specific service page and choose another language, they expect the same service. Sending them to the homepage forces them to find it again. For equivalent pages, provide direct links between versions and a visible indication of the current language.
If no translation exists, do not conceal this by automatically sending people to a random page. You can explicitly offer an available version or a relevant section and explain the situation. The solution depends on the structure, but its behaviour should be predictable.
Language names are more useful than flags alone
Use clear labels such as Eesti, Русский, English or agreed abbreviations. A flag represents a country, while a language may be used in several countries. Test the selector with a keyboard and on a mobile screen. It should not disappear into a menu covered by a form or banner.
Configure hreflang and canonical consistently
Hreflang identifies language or regional variants of a page. Language codes are et, ru and en; the Estonian language code is et, not ee. Add a region when necessary, such as ru-EE for a page intended for Russian-speaking audiences in Estonia.
Under Google's guidelines for localised versions, the set should include the page itself and corresponding alternatives, use full URLs and provide reciprocal references. A general language-selection page can use x-default. Hreflang does not guarantee that a particular version will be selected in every search result.
Canonical serves a different purpose: it identifies the preferred address among duplicate variants. Complete translations generally have their own canonical URLs. If all languages are declared duplicates of one version, the signals may conflict with the goal of independent search presence for translations.
Technical markup is best generated from relationships in the CMS rather than copied manually into every page. If a translation is removed or a URL changes, the relationship must update. The HTML lang attribute is also needed for assistive technologies to work correctly, but does not replace hreflang.
Localise meaning and search wording
A translation should preserve the facts while sounding natural to the reader. Check terminology, service names and typical questions separately for each language. A common Russian search phrase may have several Estonian equivalents with different meanings.
Create a small glossary covering the company name, services, work stages, technical terminology and how to address customers. It helps maintain a consistent style across articles, ads, forms and emails. Regulated or technically complex topics need an editor who understands both the subject and the language.
What to check after machine translation
Check numbers, negatives, conditions, timeframes, units of measurement and promises. A one-word error can change the company's commitment. Do not retain invented specifications or stronger advertising claims just because the translation sounds convincing.
Localise titles, descriptions, H1 headings, image captions and buttons together with the main text. A page is not ready if its search title remains in another language. Query and structure planning can be connected to the overall website SEO plan.
Translate the entire enquiry journey
List interface messages: field names, hints, errors, submission confirmation, the customer's email and the manager's notification. Store the enquiry language in the CRM so that the employee does not begin with an inappropriate template.
| Stage | What to check | Typical mistake |
|---|---|---|
| Ad | Leads to the required language | Every campaign goes to the ET homepage |
| Form | Fields and errors are localised | RU text, EN errors |
| Confirmation | Explains the next step | The email arrives in another language |
| CRM | Saves the language and page | The manager cannot see the context |
| Order | Terms and support are clear | Only the product page is translated |
Legal and informational documents must also reflect the actual process. Do not copy another website's policy. When terms change, check all versions so that customers are not given different promises depending on their language.
Organise updates without inconsistencies
Assign an owner for the underlying facts and editors for translations. A content record should store the change date, the status of each language and a list of changed blocks. That way, a new price or condition will not remain in just one version.
Separate critical data from editorial content. Prices, availability, contacts and service terms require coordinated updates. An article can be published in languages sequentially, provided there is no false indication that a translation is already available. For a large catalogue, store shared specifications in structured form and localised descriptions separately.
Do not create automatic placeholder pages containing only a translated heading. They disappoint visitors and complicate management. If a translation is temporarily missing, use an explicit status in the editorial system and do not include a nonexistent URL in language alternatives.
Check the versions before launch
Select representative pages: the homepage, a service, an article, contacts and a product page if applicable. In each language, follow the journey through to an enquiry or order. Check wrapping of long words, button sizes, the mobile menu, tables of contents and forms. Different translation lengths often reveal problems that the original design did not show.
Then check URLs, response codes, canonical, hreflang, meta tags and internal links. Each version needs its own clear headings and accessible content. After launch, compare enquiries by language, but do not declare one version ineffective without accounting for traffic volume and audience differences.
Example of a language-equivalence map
Suppose a company has a website-development service and a separate article about preparing for advertising. For each topic, create a row in the editorial map: internal name, ET address, RU address, EN address, owner and review status. The connection in meaning matters, not identical URL spelling.
If a Russian article explains website preparation, its English alternative should be an article serving the same purpose. A general service page does not become a translation simply because it contains similar words. If the corresponding resource does not exist, leave the relationship empty until the translation is ready.
Suppose the team changes the material-submission process: customers now fill in a brief first. The change affects the service page, button, form hint and confirmation email. An editorial map lets you mark all related elements and check them in each language. Without it, often only the prominent main text is updated.
When changing the structure, first map old addresses to new ones. Choose a meaningfully relevant new destination for each old URL, check the redirect and update the links. Redirecting all old pages to the homepage removes context for visitors and makes errors harder to diagnose.
How to compare language-version results
Separate reports by landing page and enquiry language. These are different attributes: a visitor may read an Estonian page but ask for a reply in Russian. The customer's explicitly chosen language matters for service; the pages actually visited matter for content evaluation.
When comparing conversion rates, account for channel, device and offer. If one version receives targeted search advertising and the other mainly informational traffic, the difference does not prove poor translation. First compare equivalent journeys, then examine wording and interface.
A short question log is useful: where a person did not understand a term, which condition needed explanation and which fields are filled incorrectly. These are specific reasons to improve localisation. There is no need to rewrite the whole website because of a few incidental visits or one unusual enquiry.
Also check the operational outcome: does the right manager receive the enquiry and can they continue in the selected language? Sometimes a language-version problem lies after the form, not in its text. Localisation therefore ends with coordinated service, not publication of a translation.
Frequently asked questions about multilingual websites
Must the entire blog be translated immediately?
No. Start with priority resources and pages reached through advertising and navigation. Maintain correct connections only between existing translations. Set the sequence according to demand and the ability to perform a quality editorial review.
Is a separate domain needed for Russian?
The language itself does not require one. For one business with a shared team, folders are often easier to maintain. A separate domain is worth discussing for an independent market, brand or organisational structure.
Can the language be detected automatically?
You can suggest a suitable option while keeping the choice visible. Do not prevent visitors from opening any available language at its direct address. A system's assumption should not override a person's explicit choice.