SEO in Uzbekistan: how Google.uz differs from Yandex.uz
In Uzbekistan you cannot optimise for 'search in general': Google and Yandex index differently, resolve region differently and react to links differently.
Market share reality
Public traffic counters consistently put Google ahead on mobile in Uzbekistan, a direct consequence of Chrome shipping preinstalled on Android, which dominates the handset base. Yandex retains meaningful desktop share and strength in Russian-language verticals such as real estate, autos and B2B services.
Exact percentages shift quarter to quarter and vertical to vertical, so market-wide figures are useless for planning. Open your own Google Analytics 4 or Yandex.Metrica source report for the past twelve months — that is the split for your actual audience.
The practical conclusion: if over 80% of your traffic comes from Google, Yandex-specific work pays back slowly and belongs at the bottom of the backlog.
Indexing: different speed, different rules
Google crawls new pages on .uz sites noticeably faster, especially with a working sitemap.xml and inbound links. The URL Inspection tool in Google Search Console with 'Request indexing' puts a URL in a priority queue, though it guarantees nothing.
Yandex follows robots.txt more strictly: the Clean-param directive, which Google ignores entirely, genuinely consolidates URLs carrying junk GET parameters such as utm_source or sort. For faceted e-commerce that saves real crawl budget.
Yandex.Webmaster exposes 'Indexing → Pages in search' with exclusion reasons. Search Console's equivalent is the Page Indexing report with statuses like 'Discovered — currently not indexed'. Different naming, comparable diagnostic value.
Regional targeting: the biggest divergence
For Yandex, region is an explicit setting. Yandex.Webmaster has a site region section, and the binding runs through a verified organisation in Yandex.Business with a physical address in Tashkent, Samarkand or elsewhere. Without it a site competes nationally and loses to local players.
Google removed the international targeting setting from Search Console in 2022. It now infers local relevance from a combination of signals: the .uz zone, physical address in markup and in Google Business Profile, content language, local mentions and links, and hosting IP, which today carries minimal weight.
Hence the practice: local relevance for Google is earned through content and business profile, for Yandex it is an administrative setting. Skipping the region setting in Webmaster is the classic reason a site never surfaces for geo queries in Yandex.
Ranking factors: confirmed versus assumed
Confirmed in Google documentation: speed and layout stability as part of page experience, mobile-first indexing, HTTPS, structured data for rich results. The link graph remains central, though Google never discloses individual signal weights.
Confirmed by Yandex: user behaviour in search results feeds its machine-learning ranking — the company states this openly, unlike Google. That is why optimising snippets for click-through produces a faster response in Yandex.
Assumptions frequently sold as fact: 'Yandex prefers long texts', 'Google demotes sites without a blog', 'keyword density matters'. None of these appear in official sources. Test hypotheses on your own project via template splits rather than importing folklore.
Tooling: what to connect first
The mandatory minimum: Google Search Console and Yandex.Webmaster, both verified through a DNS TXT record — that method survives CMS migrations and redesigns, unlike an HTML file in the root.
For keyword research: Yandex Wordstat gives Uzbekistan-region frequencies with a region operator; Google Keyword Planner shows ranges without an active campaign. Your own Search Console Performance report filtered by country is always more honest.
For crawling: Screaming Frog SEO Spider in list mode catches redirect chains, broken links and duplicate titles well. The free tier caps at 500 URLs, so a 10,000-SKU shop needs a licence or an alternative such as Netpeak Spider.
Running a two-engine programme
The technical base is shared: clean URL architecture, correct canonicals, no duplicates, fast mobile rendering. All of it serves both engines and should ship first.
Then the paths diverge: content and business profile for Google, region binding, Clean-param and snippet work for Yandex. Plan them as two separate backlog lines, not one generic 'SEO' item.
Track rankings separately per engine with an explicit region. A blended 'average position across engines' report is worthless: growth in one engine masks decline in the other.