Promotion in Kazakhstan, Uzbekistan, Russia and neighbouring countries: languages, hreflang, currencies and domains.
In Kazakhstan Google's search share is well above Yandex's, and many commercial queries are made in Russian. You need pages for your real services with prices in tenge, local contacts and addresses, profiles in 2GIS and Google Business Profile, and — if you serve Kazakh-speaking customers — a full Kazakh version. Demand differs between Almaty, Astana and the regions.
Google is the main search engine; people search in Uzbek (Latin and Cyrillic) and Russian. Check search volume in each language first: in some niches Russian demand is comparable to Uzbek. Pages need to be local — prices in sum, local phone numbers and Telegram, market-relevant examples. Translating a Russian page and swapping the city name does not work.
In Russia you need to work with both engines: Yandex leads, Google is significant on mobile. Yandex values regional assignment, commercial factors and user behaviour; both value speed and page quality. There are legal specifics: Russian citizens' personal data must be stored on servers in Russia (Federal Law 152-FZ), advertising must be labelled, and a data-processing policy is required.
If customers search in both languages, yes. Each version must be complete: navigation, prices, forms and markup translated, each with its own URL (e.g. /ru/ and /kk/) and reciprocal hreflang. Unedited machine translation is obvious to native speakers and erodes trust. If Kazakh-language demand in your niche is small, start with a strong Russian version and add Kazakh for priority pages.
An attribute that tells search engines about language and regional versions of a page: <link rel="alternate" hreflang="kk" href="…/kk/">. Rules: each version links to all others and to itself, links are reciprocal, URLs are canonical and return 200, codes follow ISO 639-1 (language) and ISO 3166-1 (region, e.g. ru-KZ). x-default marks the default version. Google uses hreflang; Yandex supports it partially.
Yes, if the pages genuinely differ: currency and prices, payment methods, timelines, contacts, legal terms, local examples. Pages where only the country name changes are treated by search engines as duplicates or doorways. For Russian-language versions aimed at different countries, use hreflang with a region (ru-RU, ru-KZ) and visible on-page differences.
Not necessarily. A .kz domain is a strong signal of a Kazakhstan focus for search engines and users, but registration requires the server to be located in Kazakhstan. An international domain (.com, .agency) with a /kk/ or /ru/ folder works if you serve several countries. The choice depends on whether you need one strong domain or a local presence.
The currency of the market the page targets: tenge for Kazakhstan, sum for Uzbekistan, roubles for Russia. If prices are converted from another currency, say so and give the rate date. Prices must match everywhere — on the page, in the FAQ, in markup and in materials for AI. Discrepancies confuse both customers and AI systems that compare sources.
Minsk (UTC+3) and Almaty (UTC+5) are two hours apart, as are Moscow and Tashkent. Show office hours with a time zone on the site, ask for a convenient contact time in the form and schedule meetings through a calendar that converts time automatically. Deadlines in contracts are better set in business days rather than hours.
No. Translate what has demand in the target language: service pages, prices, contacts, key articles. Every translation should be checked by a native speaker, and terms should match how people actually search (sometimes that is the English or Russian term). Leave untranslated pages out of hreflang and do not present them as a "translation" in the language switcher.
Nothing found.
