Search engine crawler · Yandex
YandexBlogs user agent, IP ranges and robots.txt
YandexBlogs is Yandex's search engine crawler. It identifies itself with the YandexBlogs user-agent token, honors robots.txt according to its operator, and can be verified by reverse DNS (yandex.ru, yandex.net, yandex.com).
- Operator
- Yandex
- Reviewed
- September 2026
- Sources
- 1
- Operator
- Yandex
- User-agent token
- YandexBlogs
- Purpose
- Search engine crawler
- robots.txt token
- YandexBlogs
- Honors robots.txt
- Yes, per the operator
- Published IP ranges
- No official range file
- Verification
- 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.
- Reverse DNS suffix
- yandex.ru, yandex.net, yandex.com
- Full user-agent example
- Mozilla/5.0 (compatible; YandexBlogs/0.99; robot; +http://yandex.com/bots)
Block or allow YandexBlogs in robots.txt
User-agent: YandexBlogs
Disallow: /User-agent: YandexBlogs
Allow: /Verify a request is really YandexBlogs
Anyone can put YandexBlogs 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>What YandexBlogs does
Yandex operates YandexBlogs, the blog search robot that indexes post comments. It follows general robots.txt rules, and site owners can also address it directly with the token YandexBlogs. Yandex publishes no IP range list; site owners verify a visit by reverse DNS to a host ending in yandex.ru, yandex.net or yandex.com, forward-confirmed, or with the Yandex Webmaster IP check tool.
In logs YandexBlogs identifies itself as Mozilla/5.0 (compatible; YandexBlogs/0.99; robot; +http://yandex.com/bots). Yandex describes it as the blog search robot and says its job is indexing post comments. Pages with a comment section are the content Yandex says this robot indexes, so a blog is where a site owner is most likely to meet it in the logs. The documentation does not describe fetch rate or whether the robot executes JavaScript.
Yandex states that YandexBlogs takes general robots.txt rules into account, so a Disallow rule for all user agents applies to it, and a group naming User-agent: YandexBlogs applies to it alone. Allowing it keeps comment content on the site available to Yandex blog search. Blocking it removes that content from Yandex blog search results. Yandex publishes no IP range list for this robot; verification relies on the reverse DNS check Yandex documents for all of its robots, plus the IP address check tool in Yandex Webmaster.
Operator note. It takes into account the general rules in robots.txt.
Common questions
- Should I block YandexBlogs?
- Block it only if you do not want your post comments indexed in Yandex blog search. Yandex describes that as the robot's purpose. If you want comment content findable there, allow the token. A site-wide Disallow for all user agents also stops it, since Yandex says it follows general robots.txt rules.
- How do I verify YandexBlogs?
- Do a reverse DNS lookup on the requesting IP. The host name should end in yandex.ru, yandex.net or yandex.com; then resolve that name forward and confirm it returns the same IP. Yandex also provides an IP address check tool in Yandex Webmaster. Yandex publishes no IP range list for YandexBlogs.
- Does YandexBlogs run JavaScript?
- The operator's documentation does not say. The Yandex robots page lists YandexBlogs as the blog search robot that indexes post comments and gives no detail on rendering or script execution.
Sources
The operator documentation used for this entry. Recorded review date September 2026; consult the linked pages for current policy and compare them with this dated snapshot.
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.