Yandex
YandexBot
Indexes pages for Yandex Search.
Web searchTHE SIGNAL
Mobile checks can reveal a response that desktop tests miss.
Compare mobile page content and redirect behavior.
Look for the YandexMobileBot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.
Confirm reverse DNS under yandex.ru, yandex.net or yandex.com, then resolve that hostname back to the original request IP.
General wildcard robots.txt rules may be ignored. Yandex documents named-client Disallow rules for these crawlers; site-specific agreements can create exceptions.
Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.
User-agent: YandexMobileBot
Disallow: /403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.
Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
See their requests. Find the pages that matter.
See your agent traffic