YandexPagechecker
Yandex operates YandexPagechecker, which accesses a page to validate its structured data with the Structured data validator. It honors robots.txt under the token YandexPagechecker and takes general rules into account. Yandex publishes no IP range list; site owners verify by reverse DNS to a yandex.ru, yandex.net or yandex.com hostname with matching forward lookup, or with Yandex Webmaster's IP check tool.
Mozilla/5.0 (compatible; YandexPagechecker/1.0; +http://yandex.com/bots)What YandexPagechecker does
The user-agent string in logs is Mozilla/5.0 (compatible; YandexPagechecker/1.0; +http://yandex.com/bots). The registry classes it as an SEO tool rather than an indexing crawler, because Yandex describes a single job for it, fetching a page so the Structured data validator can check the markup on that URL. Yandex describes only that validator use, not scheduled crawling, and the entry records no crawl-rate figure or JavaScript execution detail from Yandex for this bot, so both remain undocumented.
Yandex says the bot takes general robots.txt rules into account, so general Disallow rules apply to it, and a User-agent: YandexPagechecker block targets it alone. Blocking it means the Structured data validator cannot fetch the page, so validation of your markup through that tool fails; Yandex's description does not link this bot to search indexing itself. Verification uses reverse DNS with forward confirmation, expecting a hostname ending in yandex.ru, yandex.net or yandex.com, or the IP address check tool in Yandex Webmaster. Yandex publishes no IP range file for it.
Operator note. It takes into account the general rules in robots.txt.
Controlling YandexPagechecker with robots.txt
Use the token YandexPagechecker in robots.txt. Yandex documents that YandexPagechecker honors robots.txt directives.
User-agent: YandexPagechecker
Disallow: /User-agent: YandexPagechecker
Allow: /Verifying a request is really YandexPagechecker
Anyone can put YandexPagechecker in a User-Agent header. Reverse DNS lookup on the requesting IP must return a host ending in yandex.ru, yandex.net or yandex.com, and a forward DNS lookup of that host must return the same IP. Yandex Webmaster also provides an IP address check tool.
host <request-ip>
# expect a hostname ending in yandex.ru, yandex.net, yandex.com
host <that-hostname>
# expect it to resolve back to <request-ip>Common questions
Should I block YandexPagechecker?
Only if you do not want the Yandex Structured data validator to read your pages. The bot exists to validate markup on request, and blocking it makes that validation fail. Yandex's description does not tie it to search indexing, so a block has no documented effect on Yandex search results.
How do I verify YandexPagechecker?
Run a reverse DNS lookup on the IP and check the hostname ends in yandex.ru, yandex.net or yandex.com, then a forward lookup on that hostname and confirm it returns the same IP. Yandex also has an IP address check tool in Yandex Webmaster. Yandex publishes no IP range list for this bot.
Does YandexPagechecker follow robots.txt?
Yes. Yandex states the bot takes general robots.txt rules into account, and it can be addressed with User-agent: YandexPagechecker for rules that apply to it alone. Yandex's compliance note for this bot is a plain yes, with no directive listed as ignored.
Sources
Every fact on this page was checked against Yandex's own documentation, listed below, and re-checked by a second reviewer before publication. Reviewed September 2026.
Related crawlers
This registry documents how operators describe their own bots so site owners can identify and control them. It does not publish third-party IP lists or guess at undocumented behaviour. To see how your own site responds to automated visitors, the bot detection scanner reads a URL's live response and names the protection it finds.