WebmasterID logoWebmasterID
Robots & crawl control

How to control YandexBot in robots.txt

YandexBot is the crawler for Yandex, a major search engine in Russia and nearby markets. You can target it in robots.txt with the YandexBot token. Yandex documents its robots.txt handling, has historically honoured crawl-delay, and provides additional crawl controls in Yandex.Webmaster.

Verified against primary sources

What YandexBot is

YandexBot is the primary crawler for Yandex, which holds significant search share in Russia and several neighbouring markets. If your audience includes those regions, YandexBot crawling supports your visibility in Yandex search, so a full block carries a regional-visibility cost similar to blocking Googlebot for Google.

The rule and Yandex-specific controls

To restrict a path for YandexBot:

User-agent: YandexBot Disallow: /private/

Yandex documents support for standard Allow/Disallow rules and has historically honoured the crawl-delay directive for slowing the crawler. For finer control, Yandex.Webmaster offers crawl-rate and related settings. As always, robots.txt is a request to the compliant crawler, not enforcement.

How it appears in analytics and logs

A request with the YandexBot token is Yandex's search crawler. Disallowing paths stops their crawling and can reduce their presence in Yandex search, which matters most for sites serving Yandex's markets.

Diagnostic use case

Adjust what YandexBot crawls — relevant if you target Russian-language or regional audiences — without unintentionally dropping out of Yandex search.

What WebmasterID can help detect

WebmasterID classifies YandexBot as a search crawler separate from human traffic, so you can confirm a robots.txt change affected it as intended.

Common mistakes

Privacy and accuracy notes

Managing YandexBot is a crawl and search-visibility choice in a public file. It involves no visitor data.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.