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

YandexMetrika

Yandex · Tools and frameworks · json

User-agent: YandexMetrika
Disallow: /
robots.txt tokenYandexMetrika
User-agent containsYandexMetrika
OperatorYandex
CategoryTools and frameworks
robots.txtnot governed by robots.txt (user-initiated, by operator policy)
Verify byreverse DNS

What it is

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.

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)

Allow it instead

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.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=yandexmetrika&s=client-dossiers'

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. All of them.

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