How to host the Russian and Uzbek versions of a website, link them for search engines, and avoid losing visitors to language-switching mistakes.
KelyanMedia editorial team · Updated November 20, 2026

A multilingual website is needed wherever customers speak different languages. In Uzbekistan, people search for the same service in Russian and in Uzbek, and Uzbek queries are typed in both Latin and Cyrillic script.
Simply translating the texts is not enough. Search engines need to understand that they are looking at versions of the same page and show each visitor the one in their language.
This takes three things: separate URLs for the versions, links between them, and a translation built around what customers actually search for.
In short: what you need to know
- Where to place themEach language version has its own URL. Most often, versions are placed in folders on a single domain.
- How to link themWith the hreflang attribute in the page code: each version points to itself and to all the others.
- What to decide in advanceWhich script to use for the Uzbek version: Latin, Cyrillic, or both.
When a business needs a website in Uzbek
A language version is needed when people search for you in that language, not because it “should be there”.
The Russian version answers Russian queries, the Uzbek version answers Uzbek ones. If there is no page in the language of the query, search engines will show someone else’s.
An Uzbek version is a priority if:
- you sell mass-market products and services rather than a niche product for specialists;
- customers come not only from Tashkent but also from the regions;
- people call and message you in Uzbek;
- your Uzbek-language ads lead to a Russian page;
- there are few useful pages for Uzbek queries in your niche.
The last point is easy to check: type your main queries in Uzbek and see who ranks for them. If there are few useful pages, it is a chance to take the spot before your competitors.
Language versions are planned at the stage of choosing the type of website. Read more about it in our article on what kind of website a business needs.
Multilingual website structure: where to place the versions
Each language version of a page must have its own permanent URL. Without it, search engines see only one language.
If the language is switched by a button while the page URL stays the same, the search crawler only gets the default version. The others never make it into search.
| Option | What the URL looks like | When it fits |
|---|---|---|
| Folders on one domain | Domain and the /uz/ folder | Most common: one website that is easier to maintain |
| Subdomains | The uz prefix before the domain | When versions are run by different teams or hosted on different servers |
| Separate domains | A separate domain for each country | When a company operates in several countries |
| URL parameter | Domain and the ?lang=uz suffix | Not recommended: versions are hard to separate |
← Swipe to scroll the table →
A company operating in one country in two languages usually only needs folders. This is how the KelyanMedia website is built: the Russian version is in the root, the Uzbek and English versions are in the /uz/ and /en/ folders.
Before adding a version, estimate the amount of work.
A hypothetical example: a services website in Russian and Uzbek in two scripts.
Each of these URLs needs its own text, title and search description, and any change has to be made in three places. Do not launch a version you cannot maintain: a half-empty section is worse than none at all.
If you also need an English version for foreign markets, see our article on SEO promotion of a website in the USA.
hreflang and language switching: how to link the versions
hreflang tells search engines: these pages are about the same thing, but in different languages. Without it, search engines are more likely to pick the wrong version.
hreflang is written in the service part of the page code. The Russian version is marked with the code ru, the Uzbek one with uz. Visitors do not see this markup; it is read by search crawlers.
- Its own URLFor each language version of a page
- Reciprocal linksThe Russian version links to the Uzbek one, the Uzbek to the Russian
- Self-referenceEach version also lists its own URL
- Full URLsIncluding https and the domain
The most common mistake: the links are added only to the Russian version. Without return links, search engines may ignore them.
Google accepts hreflang in the page code, in server headers and in the sitemap (Sitemap file). Yandex only takes into account the markup in the page code. For the links to work in both search engines, put them in the code.
The second group of mistakes is related to language switching.
| Error | What is happening | How to fix it |
|---|---|---|
| Automatic redirect based on browser language or visitor location | The crawler and some visitors never reach the other versions | Remove the redirect and keep language selection as a link |
| The language changes without the URL changing | Only one version gets into search | Give each version its own URL |
| Links only on the Russian version | Search engines may ignore them | Add reciprocal links on all versions |
| Only the menu is translated | The text stays in Russian, and the page answers Russian queries | Translate the page in full or do not publish it |
| Links only in the Sitemap | Yandex ignores them | Add the markup to the page code |
← Swipe to scroll the table →
An automatic redirect seems convenient, but Google’s crawler usually comes from US addresses and does not send a language. The website sends it to one version, and it may never see the others.
It is more reliable to place a visible language switcher made of regular links on every page. It leads to the same page in the other version, not to the homepage.
Latin and Cyrillic script: SEO specifics for the Uzbek language
To a search engine, a query in Latin script and a query in Cyrillic consist of different letters. A page in one script is not guaranteed to appear for a query in the other.
Uzbek texts and queries come in two scripts. Which one matters more to you depends on your audience: age, region, habits.
Hypothetical query examples. Choose a script.
- Buy a refrigeratormuzlatgich sotib olish
- Dentistry in Tashkentstomatologiya Toshkent
- Flower deliverygul yetkazib berish
- Apartment renovationkvartira ta’mirlash
This is how it is written on websites and in apps with an Uzbek interface.
- Buy a refrigeratorмузлатгич сотиб олиш
- Dentistry in Tashkentстоматология Тошкент
- Flower deliveryгул етказиб бериш
- Apartment renovationквартира таъмирлаш
This is how part of the audience types out of habit.
Open the search query reports in Google Search Console and Yandex Webmaster, the dashboards for website owners. They show which script people already use to find you.
From there, there are three workable options:
- one Uzbek version in Latin script: the most common choice, and the one used for the Uzbek version of the KelyanMedia website;
- two Uzbek versions with their own URLs, if you get a lot of Cyrillic queries;
- one Latin-script version plus separate Cyrillic pages for the most important queries.
If there are two versions, hreflang distinguishes them by script code: uz-Latn for Latin and uz-Cyrl for Cyrillic. After launch, check in both dashboards that both versions are indexed.
Do not build a script switcher that changes the letters on the same page without changing the URL. For search engines, such a Cyrillic version does not exist.
Translation and localization: what to translate besides the text
Translation answers the question “how do you say this in Uzbek”. Localization answers the question “how do people search for and buy this”.
A literal translation often does not match what people type into search. The name of a service in Uzbek is chosen based on queries, just as in Russian.
- Words are translated literally
- Search titles are copied from the Russian ones
- Buttons and forms remain in Russian
- Requests are handled by a manager who only speaks Russian
- Names match how people search for them
- Dedicated titles and descriptions for Uzbek queries
- Menu, buttons, forms and emails in Uzbek
- Requests are answered in the customer’s language
Google determines the page language from the visible text, not from service tags in the code. That is why the whole page needs to be translated, including the menu and captions.
Do not mix languages on one page: Russian text with an Uzbek menu, or a paragraph’s translation right below the original, makes it harder for search engines to understand who the page is for.
Machine translation works as a draft. Before publishing, the text should be proofread by someone who writes fluent Uzbek and knows your field.
Timing and results depend on the niche, competition and the state of the site, so we do not promise specific rankings.
Learn about website development →Important
Search engine guidelines change. This article reflects the practice as of the update date, and the result of promotion depends on the niche, competition and the state of the site.
FAQ
Does a multilingual website in Uzbekistan need a Cyrillic version?
What happens if you do not use hreflang?
Can you launch an Uzbek version for only part of the website?
Next steps
You need to build or rework a website for two languages: see website development.
The versions already exist, but the Uzbek one gets no traffic: learn about SEO promotion and discuss a website audit.
Want to assess an agency's experience: take a look at website examples.
Still have questions: call +998 33 339 33 34.
Discuss a bilingual website →
