WEB3smart contracts / dApps / asset tokenizationExplore Web3 →

A website in Kazakh and Russian: how to build a bilingual site for Kazakhstan

How to run a website in Kazakh and Russian: /kk/ URLs, hreflang, a language switcher, translation that reads well, fonts with Kazakh letters and a launch checklist.

A website with a language switcher on a laptop and a phone: Kazakh and Russian versions

Many companies entering Kazakhstan start with a website in Russian, which is widely used in business here, or even in English only. Sooner or later they find that part of their customers search in Kazakh, the state language, and that a local competitor already appears for Kazakh queries. At that point the task becomes "translate the site into Kazakh", and it is usually understood too narrowly: hand the texts to a translator and put them next to the Russian ones. In practice a bilingual site rests on several technical decisions: page addresses, markup for search engines, the language switcher, fonts, forms and emails. If they are not thought through, the Kazakh version exists on paper, but neither people nor Google and Yandex find it.

Below is how to build a site in Kazakh and Russian so that both versions work and get indexed. The legal side, whether a Kazakh version is required by law, is covered in our guide on website and advertising language. In short: we found no direct rule on the language of a private company's website, but advertising, price lists and menus are placed in the state language, and prices in advertising are given in tenge. That is why two versions, Kazakh and Russian, are the safest option.

What to decide before development

Three questions are worth settling before the designer opens a layout.

Which language is the main one. It opens at the address without a language prefix and becomes the default page for search engines. For many companies in Kazakhstan that is Russian, for part of the audience it is Kazakh. Decide by the language your customers use when they message you on WhatsApp or call, not by taste.

All pages or the key ones. Identical versions are best. If texts or budget do not allow it yet, start with the home page, services, prices and contacts, and add the blog and news as they are ready. The main thing is that unfinished pages do not lead to empty Kazakh addresses.

Who writes the texts. A translator, an employee who writes Kazakh fluently, or an author who writes in Kazakh from the start. The project timeline depends on this answer more than on the programming.

Addresses: a /kk/ folder, a subdomain or a parameter

Each language version needs its own address. Google recommends a separate URL for each language rather than switching the language through cookies or browser settings on one and the same address. The options are:

OptionExampleWhat matters
Folderexample.com/kk/Easy to set up, one hosting and one admin panel
Subdomainkk.example.comVersions can live on different servers, but you maintain two sites
URL parameterexample.com?lang=kkGoogle does not recommend it

A separate domain per language within one country is rarely justified: it is a second site with its own maintenance. In most cases a folder is more convenient: one codebase, one admin panel, a shared domain. This site is built that way: Russian at the root, Kazakh under /kk and English under /en.

We recommend keeping the last part of the page address (the slug) identical and in Latin letters across languages: /services/crm and /kk/services/crm. That makes the switcher simpler and lets you compare versions in analytics. An address with Cyrillic letters turns into a long string of encoded characters when copied and looks messy in an email or a messenger.

hreflang: telling search engines where each version is

Google does not determine page language from hreflang or from the lang attribute: it looks at the visible text. A page with a Kazakh menu and Russian main text stays a Russian page for Google. Google explicitly calls the situation where only the menu and buttons are translated while the main text stays in one language a poor experience for users.

hreflang does a different job: it tells the search engine where the versions of a page in other languages are and which one to show to whom. Google's rules:

  • each version lists itself and all other versions;
  • if two pages do not point to each other, the tags are ignored;
  • the language code follows ISO 639-1 (kk, ru), the region code follows ISO 3166-1 Alpha 2 (KZ), and a region cannot be given without a language;
  • addresses are fully qualified, with https;
  • x-default marks the page that opens when the user's language matches none of the versions.

For Google, three ways of marking up are equivalent: link tags in the HTML, HTTP headers and the sitemap. Yandex reads link rel="alternate" markup in the head of the page, Kazakh (kk) is on its list of languages, and Yandex no longer supports Sitemap files for language versions, recommending markup on the pages themselves. So it is safer to put hreflang into the code of every page and treat alternate links in the sitemap as an addition for Google.

An example from this site, the /services page: ru-KZ points to the Russian version at the root, kk-KZ to /kk/services, en-KZ to /en/services, and x-default to the Russian version. A language code without a region (kk) addresses everyone who reads Kazakh, kk-KZ narrows it to Kazakhstan. Both are valid; what matters is one format across the whole site.

A language switcher without automatic redirects

The switcher should lead to the same page in the other language, not to the home page. Someone reading a service page clicks the Kazakh label and lands on the home page: now they have to look for what they needed all over again. If a page has no translation yet, hide the switcher or lead to the nearest translated section, and leave that page out of hreflang.

Do not redirect automatically by IP or browser language. Google advises against moving users between language versions automatically and against adapting content by IP: Googlebot usually crawls from the USA and may not see all the versions. Besides, a customer in Almaty with a phone set to Russian may well want to read in Kazakh, and the other way round. Show both languages in the header and remember the choice after the first click.

Label each language by its own name, the way its speakers write it. Flags do not fit: a flag stands for a country, and both languages here belong to Kazakhstan.

Translation: why machine translation alone is not enough

Kazakh is an agglutinative language: a word changes through endings for case, number and possession, and word order differs from Russian. Machine translation often gets endings, terms and word order wrong, so the text is understandable but reads heavily and does not build trust. Foreign companies feel this most, because nobody in the team can spot the problem. We work like this:

  1. A glossary before translation. How we name the product, services and buttons, which words stay in Latin letters (CRM, API, Kaspi). Without a glossary one concept ends up with three different names on the same site.
  2. A machine draft, then an editor. A draft by machine is fine, but before publication the text is read by an editor who writes Kazakh fluently and understands your field.
  3. Short interface texts separately. Buttons, form errors, emails, SMS and WhatsApp templates are the ones most often forgotten, and customers see them first.
  4. Keywords of their own for each language. Collect Kazakh search queries separately instead of translating the Russian ones: people search with their own everyday Kazakh phrases, not with a word for word translation of the Russian query.
  5. A title and description of their own. The page title and description for search are written in each language separately, not copied from the Russian version.

Kazakh letters, fonts and the Latin alphabet

The Kazakh Cyrillic alphabet has 42 letters, and nine of them are not in Russian: ә, ғ, қ, ң, ө, ұ, ү, һ, і. The site font must contain them in every weight you use. Otherwise the browser takes the missing letters from another font, and words look patched. Check headings, buttons, PDF documents, emails and the admin panel.

Site search and filters should find words with these letters, and form validation should accept names that contain them: a validator that only lets through the Russian alphabet will reject such a name as an error. People sometimes type Kazakh words on a Russian keyboard layout, replacing these letters with the nearest Russian ones, and it helps if site search forgives that.

Now about the Latin alphabet. Decree of the President of Kazakhstan No. 569 of 26 October 2017 approved a Kazakh alphabet based on Latin script (as amended by Decree No. 637 of 19 February 2018) and instructed the government to carry out a phased transition by 2025. On the date we checked, the text of the decree on adilet.zan.kz still gives exactly that deadline, while Kazakh texts, including on adilet.zan.kz itself, are written in Cyrillic. So today we build sites in Cyrillic and keep texts in the admin panel rather than in the code. If the alphabet changes, that will be a separate job on the texts, not a new site.

Forms, emails and everything around the pages

A bilingual site is more than pages. Field labels, error and success messages, auto-replies and emails are needed in both languages. So is the consent text for processing personal data: we wrote a separate article on where and how to store customer data in Kazakhstan.

Save the language the customer chose with the lead: the manager in the CRM sees at once which language to reply in. An online store needs, besides product cards, its offer, delivery and return terms in both languages, see our step by step guide to launching a store. In analytics, set up segments by language to see which version brings leads.

Checklist before launch

  • Every page has its own address in every language
  • hreflang on every page lists all versions including the page itself, fully qualified with https, plus x-default
  • The switcher leads to the same page, there are no automatic redirects
  • title, description and H1 are written separately in each language
  • There is a glossary, and an editor who knows the language has read the texts
  • The font has all nine Kazakh letters in every weight
  • Forms, errors, emails and the consent text exist in both languages
  • Both versions are in the sitemap, and their indexing is checked in Google Search Console and Yandex Webmaster

What it costs and how we do it

We build sites in Russian and Kazakh from the start: addresses, hreflang, the switcher, fonts and forms are part of the project, not added later. A website starts at 540 000 ₸, and we price the second language version separately: you provide the texts or order them from us, and the final amount is fixed in the contract. If you already have a site in Russian only, a redesign is a convenient moment to add Kazakh. More on the website development page, and on what a company website needs in general in our article on a website for business.

More about the service

What we do on this topic

Questions

Short and to the point.

Is a Kazakh version of a website required by law?

We found no direct rule on the language of a private company website. But advertising, price lists and menus are placed in the state language, and prices in advertising are given in tenge. The articles of the laws are covered in our guide on website and advertising language.

Can we translate the site into Kazakh with machine translation?

As a draft, yes. Before publication the text should be read by an editor who writes Kazakh fluently and knows your field, and terms and buttons are best collected in a glossary first. Otherwise the version exists, but it reads heavily.

Which hreflang should the Kazakh version use?

The language code kk or kk-KZ, and ru or ru-KZ for the Russian version. Each version lists itself and all the others, addresses are fully qualified with https, plus x-default for the default page. For Yandex the markup has to be in the page code.

Which is better: a /kk/ folder or a separate domain?

For one country it is almost always a folder: one site, one admin panel, a shared domain. A subdomain makes sense if the versions live on different servers. Google does not recommend a URL parameter such as ?lang=kk.

How much does a website in Kazakh and Russian cost?

A website starts at 540 000 ₸. We price the second language version separately: it depends on the number of pages and on who writes the texts. The final amount is fixed in the contract before work starts.

Read also

Shall we discuss your project?

We will tell you what it costs and how long it takes. The price is fixed in the contract.

Your selectionWebsite developmentfrom 540 000 ₸
The team gets your request; we reply during business hours.Price fixed in the contract before you pay.No calls unless you ask.
Request a quote
Project budget
Your request goes to the team. We reply by email, no cold calls.

Got a task? Write to us.

Describe your project on WhatsApp or by email. We reply during working hours and name the price after the brief.