Multilingual blog SEO: posts in every language
Multilingual SEO treats each language as its own market: a page in another language only ranks when it reads as if it were written there. Write every language natively from the same outline, with its own keywords, slugs and examples.
One market per language
- Give every language its own fully written pages, so each ranks on its own, the way large international companies do it. The main language sits at the root and the others in subfolders (/en/, /ru/, /ua/ with hreflang "uk" for Ukrainian).
- AI answers follow the language of the question. A site in one language loses questions asked in the others to a competitor with a proper page in that language.
- Each language gets its own question set. Russian speakers use different words. English speakers who are new to the country need context: the areas, how to book, what things cost.
Writing each language
- Never translate directly. Every language reads naturally in its own right, and that includes the URLs.
- Write each language from the outline, not from another language's text. Swap the examples for local towns, niches and search phrases checked in that language's keyword data.
- Headings, FAQ questions, slugs, metadata and structured data are written natively per language.
- Facts are identical in every language; only the prose changes.
- Never index a fallback in another language, or raw machine translation. A native-level pass reviews each language, and each one is read once on its own for rhythm.
- No leftovers from the main language on translated pages: buttons, "from" before prices, form widgets, 404 text, aria-labels.
- Judge rhythm in the target language. Russian runs longer and breaks layouts, so headings stay within two lines at 375 px.
- Translate tone, not jokes. Replace a wry line with a local equivalent or drop it.
- Reviews and quotes stay in their original language.
- Graphics with text exist in every language (chapter 7).

Formats and markup
- Use local formats: the decimal comma where the language uses it, a non-breaking space in digit groups, the currency sign where the language puts it (the euro sign after the number in Estonian), the local hour style (9.00 to 18.00), and local quote marks („…" in Estonian, «…» in Russian and Ukrainian, "…" in English).
- Reciprocal alternates only for real translations, with x-default pointing at the main language.
The language selector
- The language selector uses country flags in a dropdown at the top right. On your own site, name each language in itself (Eesti, English, Русский, Українська).
- Where a site has regions, the region picker also offers the languages.
Who reads what
For an online store: each region shows its own currency and prices, so posts take prices live from the catalogue and never type them in.
Keyword research in every language
Each language has its own searches, and they are rarely word-for-word translations of each other.
- Run the demand check and the study of the top 10 results separately in each language, in the country where that language's readers search.
- Take the phrase people type, not the dictionary word. Russian and Ukrainian speakers in Estonia mix Estonian place names and trade terms into their searches.
- Pick the slug from that language's keyphrase, transliterated where the language uses another alphabet.
- Record the keyphrase for each language in the page's notes, so the next refresh checks the right search.
Images, files and downloads in every language
- Every image with text exists in every language, drawn from the same data, so a figure changed in one language changes in all of them.
- Alt text and captions are written natively, never machine-translated from the main language.
- Downloadable versions of a guide ship in every language the page itself is written in.
Hreflang and canonicals in practice
Hreflang tells search engines which page is the same content in another language, so each reader lands on their own version.
- Every page names itself as canonical, in its own language. A translated page never points its canonical at the main language.
- Alternates are reciprocal: if the Estonian page lists the Russian one, the Russian page lists the Estonian one, with the same set on every version.
- List only versions that exist. A language without its own page gets no alternate, and never a fallback page that says "not available".
- x-default points at the main language, for readers whose language the site doesn't have.
- The sitemap lists the alternates too, and each language's slug is written in that language.
- When a page moves, every language moves with it: one redirect per language, each to the new page in the same language.
Test it the way a reader meets it: switch the language on every page with the flags and check that you land on the same page in the other language, never on the home page.
Common multilingual mistakes
- A language switcher that drops the reader on the home page instead of the same page in the other language.
- One language updated and the others left a figure behind, so the same page states two prices.
- Slugs left in the main language under a translated page, and headings that run to three lines because the translation is longer.
- A machine translation published without a native read, with the wrong register for the market.
Launching a new language
A new language is a new market, not a button in the menu, and it launches complete.
- Collect the key phrases and questions in that language, and mark where they differ from your main language.
- Write the pillar pages and the first posts from the shared plan, with local examples, prices in the local format and their own addresses.
- Prepare the images, alt text, sharing images and downloads in that language.
- Set hreflang, canonicals and the sitemap for every version at once, and check the language switch on every page.
- Publish the language in one release, and request indexing of its key pages the same day.
A language with only half its pages ready does more harm than no language at all: the reader hits dead ends, and the search engine sees an incomplete set of alternates.
Edited by Andres LepikCo-founder & Head of Growth
Fact-checked by Siim SaarHead of SEO
Post by Rasmus Kivi
Co-founder & CEO
Co-founded REND and still reads every client's monthly report himself before it goes out.