curl -s https://www.pathwren.workers.dev/crawler/yandexmetrika.json # this page, as JSON
No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a
Yandex · Tools and frameworks · json
User-agent: YandexMetrika Disallow: /
| robots.txt token | YandexMetrika |
| User-agent contains | YandexMetrika |
| Operator | Yandex |
| Category | Tools and frameworks |
| robots.txt | not governed by robots.txt (user-initiated, by operator policy) |
| Verify by | reverse DNS |
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.
Nothing you can enforce through robots.txt. If you run Metrica, its session replay loses your stylesheets and renders your pages wrong.
Mozilla/5.0 (compatible; YandexMetrika/2.0; +http://yandex.com/bots)
User-agent: YandexMetrika Allow: /
Operator documentation: https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots
Machine copies: json ·
markdown
Policies that name this crawler:
allow-all · block-disputed · maximum-ai-visibility