# YandexMetrika

> Yandex Metrica's own fetcher. Two of its versions — the 2.0 yabs01 availability checker and the 4.0 CSS cache for Webvisor — are documented in Yandex's table as not using robots.txt at all.

| field | value |
|---|---|
| operator | Yandex |
| category | Tools and frameworks |
| robots.txt token | `YandexMetrika` |
| user-agent contains | `YandexMetrika` |
| robots.txt | not governed by robots.txt (user-initiated, by operator policy) |
| verify by | reverse DNS |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Nothing you can enforce through robots.txt. If you run Metrica, its session replay loses your stylesheets and renders your pages wrong.

## Full user-agent string

```
Mozilla/5.0 (compatible; YandexMetrika/2.0; +http://yandex.com/bots)
```

## Block it

```
User-agent: YandexMetrika
Disallow: /
```

## Allow it

```
User-agent: YandexMetrika
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is YandexMetrika?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=yandexmetrika&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/yandexmetrika.json · index: https://www.pathwren.workers.dev/llms.txt