hreflang is a special attribute that tells Google "which language and region this page is written for". It was introduced by Google in 2011 and has since become a mandatory SEO element for any multilingual website. For projects operating in the Central Asian market it matters even more, because the Uzbek audience is split into several segments: some users read and write in Russian, others prefer Uzbek in Latin script, and a meaningful portion still uses Cyrillic. Without explaining these differences to Google explicitly, the search engine will frequently serve the wrong language version and your conversion rate will suffer accordingly.
How hreflang works and why it matters
Imagine a situation where your website has three versions of the same page — Uzbek, Russian, and English. Google indexes each of them separately and tries to guess on its own which version should appear for which user. Unfortunately these guesses are often wrong in practice. A Russian-speaking resident of Tashkent might land on the Uzbek version, while an English-speaking customer from the United States could end up on the Russian interface. hreflang eliminates this ambiguity and routes every visitor to the page that is written in their own language.
Three ways to implement hreflang
The first and most common method is adding link rel="alternate" tags inside the HTML head section. This approach works well for small and medium-sized websites because the markup is visible directly in the page source and any errors can be spotted visually. The second method delivers hreflang through HTTP headers, which is mainly used for non-HTML files such as PDF documents or images. The third method describes hreflang inside the sitemap.xml file, and this is the most efficient path for large websites.
Language and region codes
An hreflang value consists of two parts: a language code following the ISO 639-1 standard and an optional region code following the ISO 3166-1 standard. Language codes are written in lowercase letters such as uz, ru, en, kk, and tj. Region codes are written in uppercase letters such as UZ, RU, US, GB, and KZ. When combined they produce values like en-US for American English, en-GB for British English, ru-RU for Russian as spoken in Russia, and uz-UZ for Uzbek as used in Uzbekistan.
The role of x-default
x-default is a special value that determines which version Google should show to users whose language does not match any of the available language versions on your site. If an Arabic-speaking visitor lands on your domain and you do not offer an Arabic version, Google will serve the page marked as x-default. Most often this role is filled by the English version.
Site structure: ccTLD, subdomain, or subdirectory
There are three primary approaches to building a multilingual site. The ccTLD approach uses a separate country-code domain for each language, for example sayt.uz for Uzbekistan and sayt.ru for Russia. This gives the strongest regional signal to search engines but requires building authority for each domain from scratch. The subdomain pattern with en.sayt.com and ru.sayt.com offers flexibility but splits accumulated authority across hosts. Subdirectories such as sayt.com/uz/ and sayt.com/ru/ preserve all the main domain authority and represent the simplest technical solution overall.
The most common configuration mistakes
The single biggest mistake when working with hreflang is the absence of reciprocal links between language versions. If the Uzbek page points to the Russian version, the Russian page must also point back to the Uzbek one. When this rule is broken, Google ignores all hreflang signals entirely and treats the markup as invalid. Another frequent problem is using incorrect language codes such as "uzb" or "rus" instead of the correct values "uz" and "ru".
The special case of the Uzbek language
The Uzbek language is used in two scripts — Latin and Cyrillic — and this requires special attention when configuring hreflang. For the Latin script the value "uz-Latn-UZ" is used, while for Cyrillic the value is "uz-Cyrl-UZ". These script codes come from the ISO 15924 standard and are officially supported by Google.
Monitoring through Google Search Console
The most reliable way to verify that hreflang is working correctly is to study the reports inside Google Search Console, specifically the "International Targeting" section or its newer equivalent under "Pages". Google surfaces all detected hreflang errors there, including reciprocal link problems, invalid language codes, non-indexable URLs, and similar issues.