Skip to content
SEO10 minJuly 23, 2026

Russian and Uzbek website: how to do SEO correctly

Robert MirovUpdated Jul 23, 2026

Russian and Uzbek website: how to do SEO correctly

In Tashkent clients search in Russian («стomatология Ташкент») and Uzbek («Toshkent stomatologiya narxi»). One language only — you lose half the demand. A second language via Google Translate — you lose SEO and trust. Below is a practical owner-level guide: ru/uz without search cannibalization, duplicate ads, and typical mistakes. No Next.js code — hreflang and Schema implementation is in technical SEO.

01Why two languages and who needs them in Uzbekistan

Russian still dominates commercial queries in Tashkent and among Russian-speaking audiences 30+. Uzbek (Latin and Cyrillic) grows in mobile search, Instagram, and among younger audiences in regions. Two languages make sense if: • you work across Uzbekistan, not only central Tashkent • CRM shows clients writing in Uzbek • competitors already rank with uz versions • you target government or corporate tenders with uz content Two languages are not required if: • niche is narrow B2B Russian-only • 95% of leads come from one language segment in analytics • content budget cannot support two quality texts, not one + auto-translate Main rule: one language done well beats two done poorly. Google often downgrades ru→uz machine translation as low-quality duplicate content.

02URL structure: subfolders, subdomains, what to choose

For SEO in Uzbekistan we recommend subfolders on one domain: • `example.uz/ru/uslugi/implanty` • `example.uz/uz/xizmatlar/implantlar` Why subfolders, not subdomains: • one domain accumulates link equity • simpler analytics and one SSL • language switcher does not «leave» the site Subdomains (`uz.example.uz`) only if the uz version is a separate brand or content team. Avoid: • `?lang=uz` in URLs — worse for indexing and sharing • one URL with JS switch and no separate pages — Google sees one language • mismatched structure: ru `/uslugi/` vs uz `/services/` without logical pairs Each ru page needs a paired uz page with the same meaning and its own URL. ru URL ↔ uz URL map is mandatory when building a site.

03Content: not machine translation

Two-language SEO means two independent texts, not Google Translate copy. Do: • Write uz with a native speaker or pro translator adapted to local usage (Latin vs Cyrillic — decide upfront; Latin often fits younger audiences) • Adapt examples: districts, sums, local brands • Separate title and description — not word-for-word headline translation • Uzbek FAQ from real WhatsApp questions — they often differ from Russian Do not: • one-click «translate whole site» plugins • same H1 on ru, transliterated on uz • hidden uz text via `display:none` — penalty risk Simple quality check: open the uz page and ask an Uzbek-speaking employee — «does this sound like a local clinic ad or a robot?». If robot — fix before indexing.

04SEO without cannibalization: ru and uz do not compete

Cannibalization — when two of your pages fight for one query and Google shows neither well. Separate languages: • ru page targets Russian keys: «имплантация зубов Ташкент цена» • uz page — Uzbek: «Toshkentda tish implant narxi» • do not duplicate one keyword in both titles • hreflang tells Google: «alternates, not competitors» (see below) Within one language — two ru pages «implants» and «implantation» with the same text. Fix: one main page, second redirects or narrows (e.g. «All-on-4»). Quarterly, check Search Console for two URLs on the same queries with low CTR. Broader strategy — SEO promotion in Tashkent.

05Ads: separate campaigns and landings for ru and uz

Do not mix Google Ads and Meta in one «everyone» campaign. Tashkent practice: • separate groups or campaigns: RU and UZ • landing language matches ad — ru ad → `/ru/...`, uz → `/uz/...` • keywords and negatives in each language • creatives: uz copy in Uzbek, not translated ru headline • separate budget and CPL — uz audience may be cheaper or pricier; only numbers show it Split UTM too: `utm_campaign=implants_tashkent_ru` and `utm_campaign=implants_tashkent_uz`. Otherwise analytics says «ads work» but not which language pays back. If uz ad traffic lands on ru pages — conversion drops 20–40% in our projects. Ad language = first-screen language.

06hreflang: what to verify without reading code

hreflang tells Google: «this is Russian, this is Uzbek, they are equivalents». Technical setup — technical SEO article. Owners need a acceptance checklist: • each ru page links to uz counterpart and back • sitemap lists both language versions • language switcher goes to the correct pair, not always homepage • no broken hreflang to 404 pages • `x-default` points to default version (often ru for Tashkent) 10-minute check: 1. Open ru service page → switch uz → same meaning, own URL 2. Run URL through hreflang testing tool or Search Console → International Targeting 3. Google `site:example.uz` — duplicate titles across languages? If the contractor says «hreflang is done» but the switcher breaks URLs — fix before launching ads.

Summary

Bilingual SEO in Uzbekistan is paired URLs, live content in both languages, separate ads, and clean hreflang. Do not save on translation or mix languages in one campaign. Need ru/uz from day one or an audit of current structure — website creation in Tashkent and SEO promotion at UZNEO. Questions — Telegram.

Search Console

Live SEO screenshots

Tap — open and zoom

Rank your site in Google's top?

SEO strategy for your niche in Uzbekistan. Audit and growth plan in 24h on Telegram.