Is YandexBot in my logs really Yandex?

Not necessarily, and that is why it is worth checking. Any script can send YandexBot as its user agent. Yandex publishes the addresses its crawler uses, so the claim can be tested against them — a request from outside those ranges is recorded as unverified rather than accepted.

How do I match YandexBot in my own logs?

Match the token as a substring of the user-agent header, case-insensitively. Yandex adds and changes the version and product text around it without notice, so a rule pinned to the whole header stops working the first time they bump a version number, while a rule matching YandexBot keeps working.

Does YandexBot run JavaScript?

No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side.

Why is YandexBot counted as Indexing?

Because that is what the fetch is for. The four categories separate what a crawler came to do rather than who sent it, so a visit from Yandex moves this row and not the others. Where an operator publishes nothing to settle the question, we say so on the page rather than choosing quietly.

Why does YandexBot not show up in Google Analytics?

Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all.

What happens if a YandexBot visit cannot be verified?

It is recorded as unverified, not as a forgery. A published address list can be incomplete or behind — an operator can start using a range before it appears in the file — so a miss is not evidence of anyone pretending. A visit is only marked as spoofed when the address's own reverse DNS record resolves to somebody else, which is proof rather than absence of proof.

AI crawlers

YandexBot

Also known as Yandex YandexBot

3 min read · updated 2026-09-09

Definition

YandexBot is Yandex's crawler for search indexing. Yandex's search crawler. Ordinary Yandex indexing.

For the reference card — YandexBot in the crawler directory.

What YandexBot is

Yandex is Russia's dominant search engine and publishes reverse DNS records for its crawlers, which means its traffic can be verified even without an address list.

On this site YandexBot is counted as indexing, which is the row it appears in on your dashboard. The category matters because it decides which number moves when this crawler visits, and the four are reported separately for exactly that reason.

What its traffic looks like

A steady crawl over time rather than a burst: robots.txt first, then pages in waves, revisiting the ones that change often. Volume tracks how large and how frequently updated your site is. A sudden increase usually follows a sitemap change or a burst of new pages, and a sudden stop is worth investigating — it often means a robots rule or a server error rather than a decision by the operator.

How it is verified

Checked as ip ranges + reverse dns. The user agent has to carry the token, and then the address is compared against what Yandex publishes — refetched every six hours, so a newly announced range is picked up without a deploy.

A request that matches neither is recorded as unverified rather than as a forgery: a published list can be incomplete, and an accusation needs evidence. Only a reverse DNS record resolving to somebody else produces a spoofed verdict, which is proof rather than the absence of it.

If you block it

You stop being findable through Yandex. Whether that matters depends entirely on where your readers are; check your own numbers before deciding, rather than blocking by reflex.

Treat this as a search-engine decision rather than an AI one, because that is what it is. The question is whether the people you want are looking through this engine, and your own analytics answer it better than any general advice can.

It is worth checking what you actually lose before writing the rule. Blocking an index crawler is one of the few changes here with an effect that compounds quietly: nothing breaks on the day, and traffic simply stops arriving over the following weeks.

Questions

Is YandexBot in my logs really Yandex?: Not necessarily, and that is why it is worth checking. Any script can send YandexBot as its user agent. Yandex publishes the addresses its crawler uses, so the claim can be tested against them — a request from outside those ranges is recorded as unverified rather than accepted.
How do I match YandexBot in my own logs?: Match the token as a substring of the user-agent header, case-insensitively. Yandex adds and changes the version and product text around it without notice, so a rule pinned to the whole header stops working the first time they bump a version number, while a rule matching YandexBot keeps working.
Does YandexBot run JavaScript?: No. It requests the HTML and leaves. That is why a browser-based analytics tag never records these visits: the tag is JavaScript, and nothing runs it. Seeing this crawler at all requires reading it server-side.
Why is YandexBot counted as Indexing?: Because that is what the fetch is for. The four categories separate what a crawler came to do rather than who sent it, so a visit from Yandex moves this row and not the others. Where an operator publishes nothing to settle the question, we say so on the page rather than choosing quietly.
Why does YandexBot not show up in Google Analytics?: Google Analytics runs in the browser. This crawler never opens a browser — it requests the HTML, reads it, and leaves, so the tracking script is never executed and no event is ever sent. Every browser-based analytics tool has the same blind spot, which is why crawler traffic has to be read from the server side to be seen at all.
What happens if a YandexBot visit cannot be verified?: It is recorded as unverified, not as a forgery. A published address list can be incomplete or behind — an operator can start using a range before it appears in the file — so a miss is not evidence of anyone pretending. A visit is only marked as spoofed when the address's own reverse DNS record resolves to somebody else, which is proof rather than absence of proof.

See whether YandexBot is reaching your pages.

AI crawlers take your HTML and leave without running a line of JavaScript, so a browser tag records nothing. TrueStat reads them server-side, checks each address against what the operator publishes, and shows you which pages were fetched — including the ones that returned a 404.

Start tracking All terms