YandexPagechecker user agent
Operated by Yandex
YandexPagechecker is the Yandex robot behind the structured data validator.
The YandexPagechecker bot at a glance
- YandexPagechecker is operated by Yandex and fetches pages to power a specific product feature.
- The robots.txt token for YandexPagechecker is YandexPagechecker.
- Blocking a search engine crawler removes your pages from that search engine's results.
- YandexPagechecker robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Allow.
What is YandexPagechecker?
It fetches a page when someone validates its markup in Yandex tools.
Yandex lists this robot on its official page of Yandex robots.
Should you block YandexPagechecker?
Allow YandexPagechecker unless it causes a measurable load problem.
| Effect on search rankings | Blocking a search engine crawler removes your pages from that search engine's results. |
|---|---|
| Effect on AI visibility | AI features built on that search index, such as Google AI Overviews and AI Mode on top of Googlebot, also lose access to your pages. |
| Follows robots.txt | Yes |
| Recommendation | Allow |
How to block or allow YandexPagechecker
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token YandexPagechecker is matched case-insensitively.
robots.txt: block
# Block YandexPagechecker
User-agent: YandexPagechecker
Disallow: /robots.txt: allow
# Allow YandexPagechecker
User-agent: YandexPagechecker
Allow: /robots.txt: partial
# Keep YandexPagechecker out of private areas only
User-agent: YandexPagechecker
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to YandexPagechecker
if ($http_user_agent ~* "(YandexPagechecker)") {
return 403;
}Apache
# Apache .htaccess: return 403 to YandexPagechecker
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (YandexPagechecker) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "YandexPagechecker")How to verify real YandexPagechecker traffic
Reverse DNS check: look up the request IP, confirm the hostname ends in yandex.ru, yandex.net, yandex.com, then look up that hostname and confirm it returns the same IP.
# 1. Reverse lookup: the hostname must end in yandex.ru, yandex.net, yandex.com
host REQUEST_IP
# 2. Forward lookup: must return the same REQUEST_IP
host HOSTNAME_FROM_STEP_1How to find YandexPagechecker in your server logs
Search the web server access log for the token. The command below counts YandexPagechecker requests per URL on Nginx or Apache.
grep -i "YandexPagechecker" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
YandexPagechecker user agent string
The full user agent Yandex publishes for YandexPagechecker. Version numbers such as Chrome/W.X.Y.Z change over time, so match the token, not the whole string.
Mozilla/5.0 (compatible; YandexPagechecker/1.0; +http://yandex.com/bots)YandexPagechecker FAQ
YandexPagechecker identifies itself with the robots.txt token "YandexPagechecker". A typical request header reads: Mozilla/5.0 (compatible; YandexPagechecker/1.0; +http://yandex.com/bots)
Yes. Yandex states that YandexPagechecker follows robots.txt rules written for the "YandexPagechecker" token.
Blocking a search engine crawler removes your pages from that search engine's results. AI features built on that search index, such as Google AI Overviews and AI Mode on top of Googlebot, also lose access to your pages.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: YandexPagechecker" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Yes. Run a reverse DNS lookup on the request IP; a real YandexPagechecker request resolves to yandex.ru, yandex.net, yandex.com, and a forward lookup of that hostname returns the same IP.
Search your server access log for "YandexPagechecker", for example with: grep -i "YandexPagechecker" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Yandex crawler documentation. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
