Promotion
Yandex and Google: how promotion differs and how to work with both
One site, two search engines, two different ranking logics. Where the differences actually change the work, why regional settings matter so much in Yandex, and how to build a strategy without writing everything twice.
In short
In Russia commercial results are decided by Yandex, so the strategy is built for Yandex and Google comes as a bonus. The key differences: Yandex has written off links while commercial factors carry 60 to 70 percent of the weight, whereas links still matter in Google. Yandex binds a site tightly to a region, Google is looser. Google indexes faster, Yandex slower but more steadily.
Which engine decides commercial queries in Russia
In the Russian segment Yandex holds more than half of search traffic, and its share is higher still on mobile and in commercial categories. Habit is not the only reason: Yandex is wired into its own ecosystem of Maps, Business, Direct, Market and Alice, so a commercial query is served not only by organic results but by company cards, reviews and rich blocks. The user gets the whole path to purchase inside one product.
That leads to a practical rule: if the business sells inside Russia, the strategy is built for Yandex, and Google compatibility largely follows because the baseline requirements overlap. Doing it the other way round, optimising for Google and hoping Yandex catches up, reliably underperforms, because the commercial and regional factors that decide Yandex results barely feature in the Google playbook.
Google should not be written off either. It remains significant for B2B, IT, SaaS, education and media projects, for English-speaking audiences, and for categories where decisions are made on desktop through professional sources. It is also the doorway into AI Overviews, so part of the GEO work covers it in passing. The right framing is not choose an engine but work out what share of revenue comes from each and split the effort accordingly.
Algorithmic differences that change what you do
There are many differences between the engines, but most of them do not shift priorities. The table below covers only those that change the composition of work and how budget gets allocated. In short: Yandex demands investment in commercial completeness and regional binding, Google in structure, link profile and technical quality.
The content row deserves a separate note. Google historically handles long-form material and overall topical coverage better, while Yandex rewards precise query-to-page correspondence and commercial fitness. So a 12,000-character article that ranks confidently in Google can lose in Yandex to a short service page with prices and a phone number. That is not an argument for writing worse, it is an argument for separating page types by purpose.
| Factor | Yandex | What to do | |
|---|---|---|---|
| Links | Deprecated, near-zero effect on commercial results, marketplace links are a risk | Still works, though relevance and quality matter far more than volume | Skip link packages. Earn links through PR and publications, which help Google and stay neutral in Yandex |
| Commercial factors | The primary differentiator, an estimated 60 to 70 percent of the weight on commercial queries | Counted indirectly through satisfaction and E-E-A-T rather than as a named factor group | Prices, contacts, delivery, legal details and reviews are the mandatory minimum on every money page |
| Behavioural factors | Heavily weighted, with strict anti-fraud and multi-month penalties for manipulation | Influence is indirect and there is no publicly acknowledged standalone factor | Work on time-to-answer and first-screen relevance rather than on time-on-site |
| Page speed | Counted as part of overall quality without a separate named metric | Core Web Vitals is an explicit factor backed by CrUX field data | Target Core Web Vitals thresholds, which satisfy Google and never hurt in Yandex |
| Regional relevance | Hard binding: the same query returns fundamentally different results in Moscow and Kazan | Soft geolocation by IP and language, with no explicit site-to-region assignment | Set the region in Webmaster and verify the organisation in Yandex Business, or stay out of local results |
| Indexing speed | Slower, with updates taking weeks and rollouts arriving in waves | Faster, with new pages indexed within days and sometimes hours | Do not judge Yandex results before 4 to 6 weeks and use the recrawl tool in Webmaster |
| Content handling | Rewards precise query-to-page correspondence and commercial fitness | Rewards topical coverage across the site and depth on the subject | Split page types: short commercial pages for Yandex, in-depth expert pieces for Google and GEO |
| Domain history | A young domain needs longer to earn trust, especially in competitive niches | Admits new domains faster when the content is strong | For a new project, lean on Google and paid ads in the early months while building the Yandex foundation |
Regional relevance: the Yandex lever Google does not have
Regional relevance is the difference that makes a mechanical transfer of Google practice into Yandex fail. In Yandex a site has an explicit region, and that region determines which queries it can rank for at all. The same query in Moscow, Yekaterinburg and Krasnodar returns three different result sets, and you only enter them with the matching assignment. A site with no region falls into region-independent results and effectively sits out local commercial queries.
The region is assigned two ways. The first is the regional settings section in Yandex Webmaster, where you set it manually and back it up with content: an address, a phone number with the local dialling code, mentions of the city. The second and stronger route is a verified organisation in Yandex Business with an address and a category, since the listing ties the domain to geography more reliably than a panel setting. Companies with branches build a separate page per city with real addresses and phone numbers, not a template with the city name swapped in.
International domain zones are a separate case. Yandex associates a .ru or .рф site with Russia by default, but a .com, .tech or .io domain gets no such association. For those projects the region must be set explicitly, otherwise the site risks staying in generic results and losing all local commercial traffic. This applies to Russian companies with international branding too: a nice domain zone does not remove the need to configure regional settings by hand.
The practical regional checklist takes one evening and delivers an effect comparable to months of content work, simply because without it the site is not competing in the right result set at all.
- Set the region in Yandex Webmaster and confirm it is approved rather than stuck in moderation for months.
- Create and verify a Yandex Business listing with address, categories, hours, photos and phone number.
- Keep NAP consistent: name, address and phone must match on the site, in Maps and in directories, character for character.
- A local dialling code and a physical address in the footer of every page, not only on the contacts page.
- For .com, .tech and .io domains, manual regional assignment is mandatory or local results stay closed.
Technical differences: consoles, metrics and directives
Yandex Webmaster and Google Search Console solve the same problem with different data, and you need both. The most valuable part of Webmaster is Pages in Search with exclusion reasons, which states outright that a document was judged low-value, a duplicate or insufficiently good. It is the only official channel where a search engine comments on specific pages. Webmaster also holds regional settings, the recrawl tool, important page monitoring and suggested queries.
Search Console is stronger on query analytics and indexing reports, adds Core Web Vitals field data from CrUX, and offers the URL inspector that shows the rendered page as Googlebot sees it. For JavaScript-heavy projects that inspector is frequently the decisive diagnostic tool.
Authority metrics deserve a separate note. The Yandex site quality index is a public aggregate score, not a ranking factor, and it cannot be steered directly. DR and DA belong to third-party tools, and Google has no official equivalent at all. Setting KPIs on growth in those numbers is a methodological error: they are consequences, not levers. Measure cluster positions, organic traffic and leads instead.
The robots.txt directives diverge too. Clean-param is Yandex-only and is the most convenient way to collapse duplicates on sites with URL parameters. Host and Crawl-delay are obsolete: crawl rate is configured in Webmaster and mirrors are handled with redirects and canonicals. Google, for its part, does not support noindex inside robots.txt, so exclusion has to come from a meta tag or the X-Robots-Tag header. One shared robots.txt works fine for both engines as long as you account for these quirks instead of copying somebody else template.
A content strategy that satisfies both engines
Writing everything twice is unnecessary and harmful, since duplicate material competes with itself. The working model is to split the site by page type and let each type do one job. Commercial service and category pages stay compact and highly specific: a heading matching the query, a price, scope of work, timelines, contacts, reviews and a form. That page wins in Yandex on commercial factors and does not lose in Google, because it resolves the task without padding.
The expert layer, meaning the blog and guides, works for Google, for topical coverage of the domain and for GEO. Long-form material with tables, method breakdowns, numbers and FAQ blocks belongs here. It collects informational traffic, builds expertise, gives people reasons to link, and feeds the source pool of generative answers. It does no harm in Yandex either, since topical coherence raises trust in the domain overall.
Internal linking ties the two layers together. Expert articles link down to commercial pages, and commercial pages link out to articles that answer objections. That structure serves both engines: Google gets a legible topical architecture and Yandex gets a signal that the site covers its niche coherently. A side benefit is that this is exactly the structure generative engines need in order to cite you.
- Commercial pages: short, specific, with price, timelines, contacts and reviews.
- Expert material: long-form, with tables, numbers and an FAQ, aimed at Google and generative engines.
- One query, one page. Two pages targeting the same intent cannibalise each other in both engines.
- Link both ways: article to service, and service to the article that answers the objection.
When to prioritise one engine over the other
Local services and mass-market goods, meaning repairs, healthcare, construction, delivery, retail and household services, are Yandex territory. Here the deciding factors are the Yandex Business listing, Maps reviews, regional binding and commercial factors. Google supplies additional but not decisive traffic in those niches, and investing there makes sense once Yandex is handled.
B2B, IT, SaaS, development, education and professional services see a noticeably higher Google share. That audience works from desktop more often, searches in professional terminology and English, reads long-form material and follows links from communities. For those projects a roughly even split of effort makes sense, with the content layer built primarily for Google and generative engines.
Export and English-speaking markets belong to Google entirely, and everything changes there: keyword research, structure, link strategy, speed requirements. Mixing Russian and English promotion on one domain without correct hreflang and separated sections is a mistake, because the two language clusters start interfering with each other.
A new domain is a separate scenario. Yandex is cautious with it for the first months while Google admits it faster. So at launch it is reasonable to lean on Google and paid channels while building the Yandex foundation in parallel: commercial factors, the organisation listing, reviews and the first external mentions. By month four to six the priorities swap.
Measuring results across both engines
The first rule is never to compare positions between engines. Different scales, different result sets, different personalisation: fifth place in Yandex and fifth in Google mean different traffic volumes. Compare trends inside each system separately, and traffic and leads in aggregate.
Yandex Metrica makes sense as the primary analytics system in Russia: session recording, click maps, native integration with Direct and Webmaster, goals and segments. GA4 belongs as a second system where there is meaningful foreign traffic or specific reporting needs. Rank tracking runs separately per engine and always for the specific regions that matter rather than a blended average.
A monthly report should carry the same set of indicators for both engines: organic traffic split by Yandex and Google, visibility across key clusters, indexed and excluded page counts, organic leads and their cost, and branded demand. A report like that immediately shows whether the problem is technical, for example pages dropping out of the Yandex index, or editorial.
- Track positions separately per engine and per target region.
- Keep indexed and excluded page counts from both consoles in the report.
- Do not set KPIs on aggregate authority scores. They are outcomes, not levers.
- The headline metric is organic leads and their cost, not total traffic.
Where to start: a first-month plan covering both engines
Week one is consoles and diagnostics. Connect Yandex Webmaster and Google Search Console if they are missing, export the excluded page list from both and work through the reasons, then check robots.txt, sitemap.xml, canonicals and redirects. At this stage you almost always find 10 to 30 percent of pages sitting out of results entirely for technical reasons.
Week two is regional settings and commercial factors, everything Yandex needs that does not bother Google. Region in Webmaster, the Yandex Business listing, NAP consistency, prices and contacts on commercial pages, delivery, payment and warranty pages, legal details in the footer. This is the fastest-return block of work.
Weeks three and four are structure and content. Group queries into clusters, remove pages competing for the same intent, rewrite titles and descriptions for the top 30 pages by impressions, rework the first screens of commercial pages, and launch the expert blog layer aimed at both Google and generative engines. After that the work settles into a monthly cycle of edits, measurement and priorities for the next month.
Frequently asked questions
Can one site be promoted in Yandex and Google at the same time?
Yes, and it is standard practice, because roughly seventy percent of the baseline requirements overlap. Technical quality, speed, a clear structure, no duplicates and genuinely useful content serve both. The priorities diverge: Yandex additionally wants commercial factors and regional binding, Google wants a link profile and topical coverage. For a Russian business the right order is to build for Yandex first and layer Google specifics on top, not the reverse.
Why does a site rank in Google but not in Yandex?
Three typical causes. First, the region is unset or unverified, which keeps the site out of local commercial results, and those are the ones producing leads. Second, commercial factors are missing: no prices, contacts, delivery terms, legal details or reviews, and those carry most of the weight. Third, the strategy bet on links and word count, which works in Google and barely registers in Yandex. Check them in that order.
Do you need separate copy for Yandex and Google?
No. Duplicate material targeting the same intent competes with itself and hurts you in both engines. What works is splitting by page type rather than by engine: compact commercial pages with prices and contacts cover Yandex, while in-depth expert pieces with tables and numbers serve Google and generative citation. Internal links connect the two, and that structure pays off across all three channels at once.
How do you set the region for a .com or .tech domain in Yandex?
Manually, and it is mandatory. Yandex associates .ru and .рф domains with Russia by default while international zones get nothing. Open Yandex Webmaster, go to the regional settings section, specify the region and support it with site content: a physical address, a phone number with the local dialling code, mentions of the city. In parallel, create and verify a Yandex Business listing, which binds the domain to geography more reliably than any panel setting. Without these steps the site stays out of local commercial results.
Should you use aggregate authority scores as a success metric?
No. The Yandex quality index is a public aggregate that is not a ranking factor and cannot be steered directly. DR and DA come from third-party tools, and Google has no official equivalent at all. Those numbers are useful for quickly comparing publication venues, but as KPIs they are meaningless: a site can grow traffic with the score unchanged and vice versa. Measure cluster visibility, organic traffic, leads and their cost instead.
Need a hand with this?
We do this work, not just write about it. Describe the task and we will scope it and send a staged estimate.
Related services
- SEO and GEO website promotionSearch traffic is the one acquisition channel that keeps working after the ad budget stops. We run two tracks in parallel: classic SEO for Yandex and Google, and GEO, the work of getting your pages quoted inside AI Overviews, Yandex Neuro, ChatGPT and Perplexity, where a growing share of queries now ends. It starts with an audit, never with buying links.
- GEO: getting your brand cited by AI searchMore and more queries end in an AI answer rather than a click. GEO is the work of getting named in that answer, with a measured mention share rather than a promise.
- IT consulting and product auditThe most expensive mistakes in software happen before the first line of code: a misread problem, a stack chosen out of a contractor’s habit, and a specification that does not exist. Consulting exists to settle all of that before the development meter starts running: what to build, out of what, at what cost and in which order. The result is a document, not an opinion on a call.
Read next
- SEO in Yandex in 2026: what changed and what no longer worksLink buying is dead weight, templated copy pushes pages into the low-value bucket, and behaviour manipulation is no longer a grey tactic but a way to lose the site. Here is what actually drives Yandex rankings in 2026.
- GEO in 2026: how to get cited by ChatGPT, Alice and AI OverviewsGEO is not a separate channel, it is a layer on top of SEO. Here is how six answer engines pick sources, what makes a page quotable, the honest truth about llms.txt, and a weekly method for measuring AI visibility.
- A Slow Site Loses Money: Core Web Vitals and ConversionSite speed is not a technical metric, it is a line in the revenue report. Core Web Vitals explained in plain language, how to find the real cause of a slow page, and a fix list sorted by return per hour of work.