curl -s https://www.pathwren.workers.dev/crawler/yandexrenderresourcesbot.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 · Search engines · json
User-agent: YandexRenderResourcesBot Disallow: /
| robots.txt token | YandexRenderResourcesBot |
| User-agent contains | YandexRenderResourcesBot |
| Operator | Yandex |
| Category | Search engines |
| robots.txt | ignores the * group; obeys rules named for its own token |
| Verify by | reverse DNS |
Loads the CSS, JavaScript and images Yandex needs to render a page. Yandex documents the exact rule: it ignores robots.txt for a resource when the HTML page using it is allowed, and does not fetch the resource when that page is disallowed.
Yandex renders your pages without their stylesheets or scripts and ranks what it sees. This is the classic accidental self-inflicted ranking loss.
Mozilla/5.0 (compatible; YandexRenderResourcesBot/1.0; +http://yandex.com/bots)
User-agent: YandexRenderResourcesBot Allow: /
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=yandexrenderresourcesbot&s=client-dossiers'
/tools/verification-methods?crawler=yandexrenderresourcesbotEvery 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 · allow-ai-search-only · maximum-ai-visibility