Website in Uzbek, Russian and English: How to Get Multilingual Right

In Uzbekistan, customers look for the same thing in different languages. One types a query in Uzbek using the Latin script, another searches in Russian, and a foreign partner opens the site in English. If the Uzbek version is a machine translation of the Russian one and the language switcher dumps visitors on the home page, the site loses both visitors and search rankings. This guide covers how to build a multilingual website where every version works: which languages to choose, what to do about Latin and Cyrillic, how to set up URLs and hreflang, and how to prepare for the new Uzbek alphabet that takes effect on 22 April 2027.

Which languages your website needs

Start with your audience. For a company selling in Uzbekistan, the basic set is usually Russian and Uzbek: these are the languages customers use to search for services and to write in chat. An English version is worth having if you work with foreign clients, investors or tourists, or take part in tenders run by international companies.

Every language has to be maintained: new pages, prices, offers and blog posts all need translating. If you lack the resources for that, two complete versions are better than three where one never got past the home page and outdated prices. A visitor who lands on an abandoned English version judges the company by it.

Uzbek: Latin or Cyrillic

The official Uzbek alphabet has been based on the Latin script since 1993; it is what schools teach and government bodies use. Many people of the older generation still read and write in Cyrillic, and it appears in the media and in everyday messages. For most companies, the main Uzbek version should be in Latin.

A separate Cyrillic version only makes sense if you know your audience needs it, for example if the site targets older customers or regions where Cyrillic is common. In that case, build it as a full third version with its own URLs. A button that swaps letters on the fly on the same page does not work for search, because such a version has no URLs of its own.

A few rules for Uzbek text:

• Do not mix Latin and Cyrillic on one page. Search engines determine the language from the visible text, and a mix makes it harder for them to tell who the page is for.
• Automatic transliteration between Cyrillic and Latin makes mistakes in loanwords and proper names. A native speaker should proofread the result.
• Use one form of the mark in the letters oʻ and gʻ across all texts. In practice people type o', o`, o‘ and oʻ, so set up site search to return the same results for all of them.

The 2027 alphabet: what it means for your website

On 21 October 2026 the president signed a law on the updated Uzbek Latin alphabet. It takes effect on 22 April 2027. The alphabet will have 28 letters and an apostrophe: oʻ, gʻ, sh and ch are replaced by the single letters ö, ğ, ş and ç, and the combination ng is dropped from the alphabet. Documents, banknotes and securities with the old spelling remain valid, while textbooks and signs will be replaced gradually. School textbooks will start moving to the new alphabet in 2027, with the transition due to finish by 2031.

There is no need to rewrite your website right away. But it is worth preparing before spring 2027:

• Check your fonts. Ö, Ğ, Ş and Ç are included in most modern fonts that support Turkish, but some display fonts lack them, and then the browser substitutes a different font in the middle of a word.
• Set up site search and filters so they find a word in either spelling: "oʻquv" and "öquv", "shahar" and "şahar". For several years, users will write both ways.
• Do not rename page URLs in bulk. If your Uzbek URLs are transliterated, you can leave them as they are. If you do change them, set up 301 redirects from the old addresses to the new ones, as you would during a website redesign.
• Plan to update your key pages once the law takes effect: the home page, services and contacts. Blog posts can move to the new spelling gradually.

For exactly what has changed in spelling and how to type Ö, Ğ, Ş and Ç on a computer or phone today, see our detailed guide "The New Uzbek Alphabet: What Changed and How to Type Ö, Ğ, Ş, Ç on Your Computer and Phone". To convert existing texts to the new spelling quickly, you can use our free new Uzbek alphabet converter.

How to structure URLs for language versions

Each language version of a page needs its own URL. Google recommends separate URLs for each language and advises against switching the page language with cookies or browser settings, because its crawler may simply never see those variants.

There are three main options:

• Subdirectories: example.uz/uz/, example.uz/en/. The easiest to set up and maintain; the whole site stays on one domain and builds shared authority. For small and medium businesses this is the best choice.
• Subdomains: uz.example.uz, en.example.uz. Suitable if the versions differ a lot in content or run on different servers.
• Separate domains: example.uz and example.com. Expensive and hard to maintain; only justified for large companies with separate teams for each market.

Google does not recommend URL parameters such as ?lang=uz. You can translate page addresses within each version, for example /uz/xizmatlar/ and /en/services/, but a transliterated address used across all languages works fine too. What matters is that URLs do not change after launch.

How to set up hreflang without mistakes

The hreflang attribute tells search engines that several pages are language versions of the same content and helps them show people the right one. In the <head> of every version of the page, list all the versions, including the page itself:

<link rel="alternate" hreflang="ru" href="https://example.uz/uslugi/" />
<link rel="alternate" hreflang="uz" href="https://example.uz/uz/xizmatlar/" />
<link rel="alternate" hreflang="en" href="https://example.uz/en/services/" />
<link rel="alternate" hreflang="x-default" href="https://example.uz/uslugi/" />

What to check:

• The set of tags is identical on every version. If the Russian page links to the Uzbek one but the Uzbek page does not link back, Google ignores the connection.
• URLs are fully qualified, with https:// and the domain, not written as /uz/xizmatlar/.
• Language codes are correct: ru, uz, en. A country code on its own, such as just UZ, does not work: the language always comes first.
• If you have both Latin and Cyrillic, use script codes: uz-Latn and uz-Cyrl. Google supports these under the ISO 15924 standard.
• x-default points to the page for everyone else, whose language matches none of your versions. Usually this is the main version of the site or a language selection page.
• The canonical URL of each version points to itself. If the Uzbek page names the Russian one as canonical, the search engine may not index the Uzbek page.

Google accepts hreflang in HTML, in HTTP headers and in the sitemap. Yandex no longer supports the Sitemap file for language versions and recommends markup on the pages themselves, so for websites in Uzbekistan it is safer to put the tags in the <head>.

One more detail: Google uses neither hreflang nor the lang attribute to determine a page's language. It works out the language from the visible text. If half the text on your Uzbek page is still in Russian, no markup will fix that.

Language switchers and automatic redirects

A common mistake is for the site to detect the browser language or the visitor's country by IP and redirect them to the "right" version automatically. Google advises against this. Its crawler usually comes from the US and does not send an Accept-Language header, so with automatic redirects it may miss some of your versions. It is inconvenient for people too: a Russian-speaking customer whose phone is set to Uzbek ends up on the wrong version and does not always find the way back.

A better approach:

• The language switcher is on every page, in the header, where it is easy to see.
• The switcher opens the same page in the other language. If it leads to the home page, people have to look for the section they wanted all over again.
• Languages are labelled in their own language: Oʻzbekcha, Русский, English. Avoid flags: a language is not a country, and a Russian flag for the Russian language looks odd on an Uzbek company's website.
• If you want to suggest a language, show an unobtrusive banner such as "Bu sahifa oʻzbek tilida ham bor" with a link, but do not redirect automatically.

Translation: what to translate and how

A language version is complete when everything a visitor sees is translated. The parts most often forgotten are:

• meta titles and descriptions, and social media texts;
• image alt texts and captions;
• buttons, forms, error messages and the thank-you message after an enquiry;
• emails and text messages the site sends to customers;
• downloadable PDFs, price lists and contracts;
• schema.org markup: names and descriptions in it are best given in the page's language.

Machine translation and AI now produce a good first draft, especially for English. Uzbek is harder: models confuse terms, build sentences on the Russian pattern and do not always keep the spelling consistent. A workable process is an AI draft followed by proofreading by a native speaker who knows your industry. Google's policies have no standalone rule against machine translation, but poor text performs worse both in search and with customers.

Beyond translation, each version needs adapting. Give prices in soʻm, phone numbers in the local format, and choose examples and case studies for the audience. Research keywords separately for each language as well: people phrase queries differently, and a direct translation of your Russian keyword list often produces phrases nobody searches for.

What the law says

The state language of Uzbekistan is Uzbek. The Law on Consumer Protection requires information about goods, work or services to be provided in the state language, and allows it to be given in other languages as well. The Law on Advertising also requires advertising to be distributed in the state language, but information about goods and services on a seller's own website generally falls outside its scope, and websites published only in foreign languages are exempt from its language requirements. So the law does not directly require you to have an Uzbek version of your website, but for a company selling in Uzbekistan it reduces legal risk and is something the audience needs anyway. It is best to check with a lawyer how these rules apply to your site.

Checklist before launching a language version

1. Each version has its own URLs in subdirectories, subdomains or on a separate domain.
2. hreflang tags are in the <head> of all versions, links are reciprocal, URLs are fully qualified, and there is an x-default.
3. Each page's canonical points to itself.
4. There are no automatic redirects by IP or browser language.
5. The language switcher leads to the same page in the other language.
6. Meta tags, alt texts, forms, emails and files are translated.
7. Uzbek text uses one alphabet and has been proofread by a native speaker.
8. Fonts support oʻ, gʻ and the new letters Ö, Ğ, Ş, Ç.
9. Site search finds words in different spellings.
10. All versions are in the sitemap, and the site is verified in Google Search Console and Yandex Webmaster.

Separate language versions also help with AI search. If someone asks ChatGPT or Google a question in Uzbek, the assistant needs an Uzbek page it can cite, and a site with a good Uzbek version has a better chance of appearing in that answer. Read more in our article on getting cited in Google and ChatGPT answers.

Frequently asked questions

Can I just add a Google Translate widget?

Not for search. The widget translates the page in the visitor's browser and does not create separate pages with their own URLs, so search engines do not see an Uzbek or English version of the site. Nobody checks the quality of that translation either.

Does my website need a Cyrillic Uzbek version?

Most companies do not: the main audience reads Latin, and the official alphabet is Latin too. A Cyrillic version is justified if your customers are mostly older people, or if your analytics and enquiries show that they search and write in Cyrillic.

What should I do with Uzbek texts after the switch to the new alphabet?

Nothing urgent before 22 April 2027. Prepare your fonts and site search, and once the law takes effect, update your main pages. You do not have to change page URLs, and if you do, set up 301 redirects.

How much does it cost to add a language to a website?

It depends on whether multilingual support is built into the site's architecture, how many pages need translating and who will proofread the texts. If the site was originally built for one language, it is sometimes cheaper to extend the content management system than to translate pages by hand. We explained what development costs are made of in "How Much Does Website Development Cost and What Does the Price Depend On?".

A site with Uzbek, Russian and English versions, separate URLs and hreflang can be ordered as part of our website development service.

Planning a website in several languages, or want to check that your current multilingual version is set up correctly? Get in touch: we will review your hreflang, URLs and translations and get your site ready for the new alphabet.