---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "yandexbot"
kind: "search"
operator: "Yandex"
researched_at: "2026-10-23"
confidence: "high"
json_url: "https://newruntime.com/readers/yandexbot.json"
canonical_url: "https://newruntime.com/readers/yandexbot/"
---

# YandexBot

> Yandex's main indexing robot for the Yandex search engine; Yandex runs many other specialised robots (YandexImages, YandexMobileBot, etc.).

## Dossier

- Kind: Search engines
- Operator: Yandex (https://yandex.com/)
- Documentation: https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots.html
- robots.txt tokens: YandexBot, Yandex
- Feeds: search index
- Respects robots.txt: Yes, per its documentation. YandexBot follows general robots.txt rules; some other Yandex robots (e.g. YaDirectFetcher, YandexMetrika) ignore them under conditions.
- Verification: Reverse DNS (https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots.html)
- Labels matched in our logs: yandexbot

## Why it matters to New Runtime (our interpretation)

Primary search crawler for Russian-language readers — relevant to our Russian Telegram audience finding site pages.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 4,397 requests on 82 days; first seen 2026-07-23, last seen 2026-10-22; Regular.
- Reading mix (crawler journeys): 471 content reads, 22 feed or discovery reads, 0 machine-consumption reads; 471 unique materials.
- Identity check: verified 534 requests.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots.html

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md