All insights
2 min read

One website, six languages: what we learned localising our own site

Lessons from publishing our site in six languages: native copy, fonts for every script, language choice and multilingual SEO.

One site, six languages — AtmosGate Insights editorial cover

This year we published our own website in six languages: English, Georgian, Russian, Azerbaijani, Armenian and Kazakh. That meant four scripts, six audiences and one codebase.

It was a reminder that a multilingual website is an engineering project as much as a writing one. These are the lessons we now apply when a business plans a site for several markets in the region.

Write for each market, not only translate

Our first drafts were grammatically correct but read like translations, and native speakers notice that immediately. Marketing copy carries tone and expectations that differ between Tbilisi, Baku, Yerevan and Almaty.

We rewrote each language as original copy for its audience and had it reviewed separately for grammar and tone. The pages say the same things, but not always in the same words.

Plan fonts and layout for every script

Many brand typefaces do not include Georgian or Armenian characters. When a glyph is missing, the browser falls back to whatever the visitor’s device provides, and the design breaks in ways the team may never see on its own computers.

We self-host a font for each script so every visitor sees the intended design. Translated text is often longer than English, so headings, buttons and navigation need to be tested with the longest language rather than the shortest.

Let visitors choose, and remember the choice

Visitors should be able to switch language on any page, arrive at the equivalent page and keep that language as they browse. Guessing from location or domain often goes wrong: many people in Georgia prefer English or Russian, and many abroad prefer Georgian.

Each page should declare its language correctly. W3C guidance on language tags explains how to choose tags such as ka, hy or kk so that browsers, assistive technology and search engines interpret the content properly.

Sources and release notes: [2]

Make every language discoverable

Google Search Central recommends telling search engines about localised versions of a page, for example with hreflang annotations, so that the right version appears for each audience. Each version should reference all of its alternatives, including itself.

In practice we also recommend the following:

  • A separate URL for each language version.
  • Translated titles, descriptions and social sharing images.
  • Content present in the server-rendered HTML rather than added only by JavaScript.
  • A sitemap that lists every language version.

Sources and release notes: [1]

Sources and release notes

Original analysis by AtmosGate, based on the sources below. Vendor claims and release status are attributed to their publishers.

  1. Tell Google about localized versions of your page

    Google Search Central

  2. Choosing a language tag

    W3C Internationalization