Yandex SEO

How ranking in Yandex — Russia's dominant search engine — differs from Google: heavier behavioral factors, an explicit commercial-query classifier, direct regional targeting, what the 2023 source-code leak actually showed, and whether Yandex.Direct spend touches organic.

First published: Jul 3, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #2 in Market-Specific SEO#6 in International SEO#262 on the site

Yandex SEO means optimizing and monitoring a site for Yandex Search with Yandex's own live webmaster guidance. Use Yandex Webmaster for verification, indexing, query data, diagnostics, and supported regional settings; keep paid Yandex.Direct campaigns separate from organic work. Historical leaks and market-share estimates are context, not current operational guarantees.

TL;DR — Yandex operates its own search and webmaster systems. Verify indexing, diagnostics, query data, and any regional settings in Yandex Webmaster, and keep paid Yandex.Direct campaigns separate from organic search. Avoid turning leaked or historical factor lists into current guarantees; official live documentation is the safer operational source. Retired delivery formats should not be used anew.

Evidence for this claim Yandex publishes webmaster recommendations and diagnostics for sites seeking visibility in Yandex Search. Scope: Current official Yandex webmaster guidance; no market-share claim. Confidence: high · Verified: Yandex Webmaster Help Evidence for this claim Yandex Webmaster provides indexing, search-query, quality, and diagnostic information after site verification. Scope: Current Yandex Webmaster functionality. Confidence: high · Verified: Yandex Webmaster: Getting started

Yandex’s market position: small globally, dominant locally

Start with the framing that makes Yandex worth an SEO’s time despite a tiny global number. In the global search-engine share figures I presented at Ahrefs Evolve 2025 (per Stan Ventures’ recap of that talk — treat the exact breakdown as their paraphrase, not an Ahrefs-published table), Google sat around 90.4%, Bing 4.08%, Yahoo 1.46%, and Yandex about 1.65% worldwide as of September 2025. That’s rounding-error territory globally — but Yandex is a top engine inside Russia and the CIS, which is exactly why “1.65% globally” undersells it. This is the same “small globally, dominant locally” pattern you see with Baidu in China and Naver in South Korea; the market-specific SEO hub covers the whole set.

One organizational fact worth stating plainly, because it drives enterprise procurement and compliance questions more than SEO ones: in February 2024 Yandex N.V. (the Dutch parent) agreed to sell its Russia-based businesses to a consortium at roughly USD 5.4 billion; the deal’s second closing completed in July 2024, the parent renamed itself Nebius Group in August 2024 and pivoted to AI infrastructure, with Nebius resuming Nasdaq trading in October 2024. The divestment itself was an ownership change, not an algorithm change — there’s no evidence in any source that ranking mechanics moved because of it. The Russian search business is now fully Russian-owned, which is a real vendor/compliance question for Western enterprises, separate from whether the optimization tactics still work (they do).

Yandex vs. Yandex.Direct: organic and paid are separate

Just like Google organic vs. Google Ads, Yandex organic and Yandex.Direct (its PPC/contextual ad product) are separate systems. The evergreen question mirrors the Google one: does paid spend buy organic rank? The most direct sourced answer comes from Dan Taylor (founder of RussianSearchNews.com), whose post “Is Yandex.Direct (Paid Search) A Yandex Organic Ranking Factor?” answers “Yes” — but read the nuance carefully. His “yes” is that the 2023 leak showed total traffic volume and percentage of organic traffic are ranking factors, both of which paid Direct traffic could indirectly influence. That is a much narrower and more indirect claim than “ad spend buys organic placement.” Do not conflate the two: Yandex has not said, and the leak does not show, that buying Direct ads directly lifts your organic position. (The live URL currently returns a 403; the quote above is from an archived copy — confirm against the live page if it comes back.)

How Yandex ranking actually works

Behavioral factors — the headline difference

If you take one thing from this page: Yandex weights behavioral factors more heavily, and admits to it more openly, than Google ever has. SEO Sherpa puts it directly — “Yandex puts even more weight on behavioral factors than Google.” The 2023 leak named these signals in the code: in SISTRIX’s analysis the behavioral inputs include “CTR, time on site, bounce rate and number of visitors returning to the SERPs.” Weglot’s guide independently corroborates “the average amount of time a user spends on the website” and average pages-per-session as inputs. Practically, this means the same on-page levers you’d use for engagement on Google — compelling titles that earn the click, fast pages, content that satisfies the query so people don’t pogo-stick back — carry more direct weight in Yandex.

Commercial vs. informational queries

Yandex has separated commercial from informational queries for a long time. SISTRIX notes the leak makes “differences for adult entertainment” and “commercial queries” explicit as distinct ranking treatments. Historically this traces to Yandex’s Magadan update (2008), which per Dan Taylor’s SEJ guide “enabled the search engine to understand abbreviations, as well as start to understand the difference between commercial and non-commercial queries and content uniqueness” — though that specific Magadan attribution is single-sourced to SEJ, so treat the date and framing as industry-reported rather than officially confirmed. The takeaway stands regardless: a page targeting a transactional query is judged on commercial-trust criteria (clear pricing, contact details, business legitimacy) that an informational page isn’t.

Regionality — a direct lever, not an inference

Yandex’s geo-dependence is semi-explicit in a way Google’s isn’t. You declare a site region in Yandex Webmaster, and Yandex also reads signals off the page: per SEJ, Yandex “checks your website’s IP, contact information (make sure this is structured and displayed clearly), and domain registration information” to localize rankings. Weglot confirms the principle: “Yandex takes into account a website’s region when ranking web pages for location-dependent search queries.” The leak even named a geo factor codename — Michael King’s live-tweet analysis surfaced FI_GEO_CITY_URL_REGION_COUNTRY, “the geographical coincidence of the document and the country that the user searched from.” Region (declared in Yandex Webmaster) and language (marked up on the page) are separate layers, not one setting: Yandex’s own “Indexing localized pages” doc documents a page-level markup step — “If your site has pages in multiple languages or pages intended for various regions, make sure to specify this information for the Yandex indexing bot” — using standard hreflang attributes in a <link rel="alternate"> tag, the same syntax Google uses. Declaring a region does not substitute for that page-level language/region markup, and vice versa. The tactical how-to for region declaration lives in the Yandex Webmaster Tools guide (including the Site Quality Index / IKS and the region-registration mechanics) — I won’t re-derive it here.

Underneath the differences, Yandex shares information-retrieval fundamentals with Google. Per SISTRIX, “Yandex uses a PageRank algorithm to rank the quality of links” and “mainly relies on BM25, a well-known approach from information retrieval” for text relevance — the same classical techniques widely believed to underlie parts of Google. And SEO Sherpa notes a useful contrast: “Unlike Google, which relies more on semantic understanding, Yandex still rewards direct keyword matches” — so exact-match keyword usage is a little less punished here than on modern Google. Trust/quality gets a YMYL-style treatment too — SISTRIX notes “higher quality requirements for sensitive topics such as health.”

What Yandex’s own docs say

Yandex’s public guidance lines up with this picture without spelling out weights. The Webmaster help names two internal quality metrics: Proxima, “a page quality metric built upon assessors’ evaluations and additional signals,” and Proficit, “a metric of search results’ usability that is calculated based on user interactions with Search” — that second one is the closest official acknowledgment that user interaction (i.e. behavior) feeds ranking. The docs also flag a trust angle — “When ranking sites in search results, Yandex may take into account additional signals about the company’s integrity” — and, importantly, mirror Google’s stance on human raters: “Assessors’ evaluations do not affect search results directly. Rather, they help to determine whether a particular change in the ranking algorithm is appropriate.” If that sounds like Google’s Quality Rater Guidelines, it should — it’s the same concept.

The 2023 source-code leak: what it actually showed

In January 2023, roughly 44.7GB of Yandex internal source code was posted to a Russian-language forum and mirrored on GitHub. Yandex’s response, via Search Engine Land, disputed the “hack” framing: “Yandex was not hacked. Our security service found code fragments from an internal repository in the public domain, but the content differs from the current version of the repository used in Yandex services.” (This is SEL-sourced; no Yandex-hosted primary posting was located.)

The factor count is three different numbers — don’t merge them

This is where most coverage goes wrong. There is no single “number of ranking factors” from the leak. Three analysts produced three different figures from the same data, and they do not reconcile:

  • SISTRIX (Johannes Beus): 1,922 total, 417 active. Beus found “An extensive list of 1,922 different ranking factors” and concluded “there are just 417 active ranking factors to consider” after removing those tagged TG_DEPRECATED (999), TG_UNUSED (242), TG_UNIMPLEMENTED (149), and TG_REMOVED (115). This is the most granular breakdown found.
  • Search Engine Land / Dan Taylor: ~690 potential. SEL reports “244 of the ranking factors were categorized as unused and 988 as deprecated, ‘meaning that 64% of the document is either not actively used or has been superseded – so it’s more like ~690 potential ranking factors.’” Note this is a different count than SISTRIX’s (different tag tallies, different active total) — two named analysts, same leak, unreconciled numbers.
  • iPullRank / Michael King: 17,854 (unverified). SEL credits King with finding “17,854 ranking factors, not 1,922.” I could not verify this figure against an iPullRank-hosted source — it doesn’t appear in the ipullrank/yandex-decoder-ring README (which frames the work as breaking “down the code by its function as it relates to Information Retrieval components”), and King’s own recovered live-tweets say something different: “How did y’all come up with that number of ranking factors? I see 481 factors just related to ‘Rapid Clicks’.” Treat 17,854 as SEL’s characterization of King, not a confirmed iPullRank figure.

So: 1,922 total and 417 active (SISTRIX) is the number I’d anchor on, with Taylor’s ~690 potential as the competing named estimate and 17,854 flagged as unverified. Anyone quoting a single clean count is skipping the disagreement.

Specific named factors worth knowing

Beyond counts, the leak named concrete factors that make Yandex’s priorities tangible — surfaced through King’s and Alex Buraks’ live-tweet threads (recovered via a Search Engine Roundtable roundup; the live page 403s, so this is from an archived copy):

  • FI_GEO_CITY_URL_REGION_COUNTRY — geographic match between document and searcher’s country (the regionality lever, in code).
  • FI_ADV: -0.2509 — a negative weight for a page having advertising on it.
  • Time-of-day weighting — per SISTRIX, “a distinction is made by time – there are morning and evening weights,” a genuinely Yandex-specific dimension with no obvious Google analog.
  • Number of unique visitors, percent of organic traffic, and average domain ranking across queries — factors SEL flagged as the surprising ones (these are what the Yandex.Direct discussion above hinges on).
  • A Wikipedia-uplift factor, orphan-page detection, keyword-in-URL, and even a factor literally named “random” (per Buraks, used to test behavioral-factor response).

What the leak does NOT tell you: it’s not Google’s algorithm

Plenty of headlines framed the leak as revealing Google’s ranking factors (e.g. fizzypop.nz’s “Google Ranking Factors Revealed in Yandex Source Code Leak”). That’s a conflation. Yandex and Google are different companies with different codebases; any read-across to Google is indirect — shared IR fundamentals like BM25 and PageRank-style link analysis — not a disclosure of Google’s algorithm. The best rebuttal is Google’s own John Mueller, who commented directly on the leak: “Will this help you do SEO on Google? Probably not but hey, it is super interesting.” In fairness, it’s not a universally-rejected view among practitioners — Alex Buraks tweeted “I downloaded the code, analyzed it and there is a lot of useful information for Google SEO as well” — so treat “the leak teaches you about Google” as a minority position rather than a settled fact, with Mueller’s “probably not” as the counterweight.

Note: as of 2026-07-18, Search Engine Roundtable’s live page is directly accessible and its Mueller/King/Buraks quotes and factor codenames were re-verified against it; RussianSearchNews still returns 403 to automated fetches, so that quote remains sourced from an archived copy. Confirm against the live RussianSearchNews page before treating it as final.

A working checklist for Yandex

The practical differences from a Google program, in order:

  1. Set up Yandex Webmaster and declare your region. This is the single most Yandex-specific setup step, and it directly affects location-dependent rankings.
  2. Optimize for behavioral signals. Earn the click (titles/meta), keep people on the page (speed, content quality), and don’t make them bounce back to the SERP — these carry more weight than on Google.
  3. Meet commercial-page expectations. For transactional queries, show clear pricing, structured contact information, and business-legitimacy signals.
  4. Get your technical basics right for YandexBot. Robots.txt (including the Yandex-only Clean-param directive), rendering, and bot verification are covered in that guide — Yandex’s JS rendering is limited, so serve important content server-side.
  5. Handle language properly. Russian is morphologically rich (heavy declension), and Yandex still rewards direct keyword matches — so keyword research and on-page usage in Cyrillic matter. For images, note a concrete Google difference: SEJ reports Yandex prefers schema “implemented in Microdata format (unlike Google, which prefers JSON-LD).”
  6. Use hreflang the same way you would for Google — as the international-SEO pillar notes, hreflang tells Google and Yandex which language/region a URL targets.
  7. Do not build Turbo pages. Some older guides (Weglot’s among them) still recommend Yandex’s AMP-analogue Turbo pages; Yandex discontinued them in early 2025. Ignore that advice.

Should you invest in Yandex SEO in 2026?

If you have real audience or revenue in Russia/CIS: yes. The mechanics are stable, the algorithm’s differences are learnable, and the 2024 corporate split changed ownership, not ranking. The compliance/procurement question (a now fully Russian-owned search vendor) is real for Western enterprises and is a leadership decision, not an SEO one. If you have no audience there, Yandex traffic in your logs is mostly just YandexBot crawling — nothing to optimize for.

For the broader “which non-Google engines should I care about” decision, see market-specific SEO and the international SEO pillar.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin an expert quote first.