Multilingual ecommerce site for Uzbekistan: RU/UZ without losing SEO
A multilingual ecommerce site in Uzbekistan almost always means two languages, Russian and Uzbek: some shoppers search for products in Russian, others in Uzbek, and both groups need to find you. Here is how to build a RU/UZ store so both languages get indexed, avoid competing with each other and bring in orders.
Why auto-translation doesn't solve this
Auto-translate widgets like Google Translate change text only in the visitor's browser, while the underlying HTML stays in one language. Search engines index that underlying code, so the second language never enters search. It also has no address of its own that you could link to or send ad traffic to.
Real multilingual support means a separate URL for every language and translated content that is stored in a database or project files and delivered by the server as ready HTML. Then the product name, description and meta tags are visible to both the shopper and the crawler.
Plan the interface too: buttons like Add to cart and Checkout, form error messages, emails and Telegram notifications should all arrive in the chosen language. If the cart suddenly switches to another language, some shoppers abandon the order halfway.
URL structure: language prefix and separate slugs
A workable scheme for Uzbekistan is a language prefix in the path: /ru/catalog/... and /uz/catalog/.... It is easier to maintain than separate domains or subdomains, and all authority stays on one domain. Put the prefix on every page including the home page, so there is no ambiguous default language without a prefix.
Each version of a product and category needs its own slug in its own language, in Latin letters, for example /ru/catalog/krossovki-nike-air and /uz/catalog/nike-air-krossovkalar. The language switcher must lead to the same product in the other language, not to the home page. If a page has no translation yet, do not show a switcher for it: an empty or Russian copy under an Uzbek address is worse than no page.
Do not force a language through an automatic redirect based on IP or browser headers. Googlebot visits without language preferences, and such logic hides part of your versions from it. A soft prompt such as Switch to Uzbek? with the choice remembered in a cookie is fine.
Hreflang, canonical and sitemap
The hreflang tag on every page points to its counterpart in the other language, and the links must be reciprocal: if the Russian page references the Uzbek one, the Uzbek page must reference the Russian one. A page also references itself. Use the codes ru and uz, and add x-default for a language-selection page if you have one. Without this, Google may show the wrong version or treat the pages as duplicates.
The canonical of each language version should point to itself, not to the Russian variant. A typical mistake is setting the canonical of all Uzbek pages to the Russian ones: the Uzbek version then drops out of the index even though you paid for the translation.
Add both languages to sitemap.xml and check indexing in Google Search Console. The most common problem is hreflang set on only part of the catalog, which makes the two languages index unevenly. Watch filter and sorting parameters too: they should not produce duplicates in each language, so use canonicals or block them from indexing.
What to translate by hand and what to check separately
Category names, title and description, H1, slugs, product page copy, delivery and payment terms, and the About and Contacts pages should be translated thoughtfully by a native speaker. Machine-translated Uzbek in commercial copy often sounds unnatural, erodes trust and distorts search wording.
Choose keywords separately for each language rather than translating them word for word. People search differently and often mix languages, with some words in Russian and some in Uzbek. Look at Google and Yandex search suggestions in both languages and rely on real phrasing.
Check separately the price format and currency (sum, so‘m or сум), units of measurement, city and district names, dates, phone numbers and brand names that are not translated. Mechanical translation sometimes changes price formatting or confuses units.
The Uzbek version is usually built in Latin script. Add Cyrillic Uzbek only if search queries show a real need, but then it is a third language with its own URLs and its own hreflang.
What the price consists of and how long it takes
The cost of a bilingual store has several parts: development (on a ready platform or custom), data storage for two languages, translation and content entry, integrations (payment via Payme or Click, delivery, inventory) and SEO setup. As a market guideline, a store with a catalog and two languages usually costs roughly 15–60 million soums and more depending on complexity. This is a guideline, not a price list.
Treat translation as a separate line item. As a guideline, 20,000–50,000 soums per product page when the description runs several paragraphs; for a catalog of 500 products that is roughly 10–25 million soums. To keep the budget in check, translate the main categories and best sellers first and the rest in turns.
Timelines are also approximate: a simple store on a ready platform takes 3–6 weeks, a custom store with integrations 2–4 months. Launch is most often delayed not by developers but by content and translation, so start them in parallel with layout.
FAQ
Can we start with one language and add the second later? Yes, but plan the language prefix in the addresses and translation fields in the database in advance. Otherwise you will have to change every URL and set up 301 redirects later.
Do we need a separate domain for the Uzbek version? As a rule, no: one domain with /ru/ and /uz/ sections is simpler and stronger.
What if some products are not translated yet? Do not publish empty pages and do not set hreflang to a version that does not exist. The product is shown in the language where the translation is ready.
How do I check hreflang? Open the page source, find the alternate tags with the hreflang attribute, make sure the links are reciprocal and lead to live pages, then review the reports in Search Console.
How soon will a language version appear in search? It depends on the site: usually from a few days to a few weeks after submitting the sitemap. Nobody can guarantee it.
Checklist: launching a multilingual ecommerce site
Go through it step by step. Open the home page, a category, a product page and the cart in both languages. Check that the switcher leads to the same product. Make sure every page has its own title and description in its language. Verify hreflang and canonical, that both versions are in the sitemap, and that there are no 404 errors or Russian text on Uzbek pages. Place a test order in each language and check the email and notification.
4 Digital in Tashkent builds turnkey websites and online stores, including in two languages; turnkey website development starts from 1,399,000 soums. If you want to estimate your project, send a list of sections and an approximate number of products, and we will tell you the scope and timeline.