YandexRenderResourcesBot
Yandex operates YandexRenderResourcesBot to load the resources a page needs for JavaScript rendering. It honors robots.txt only partially, ignoring resource-level rules when the HTML page using those resources is open to the Yandex bot, and skipping resources of disallowed pages. Verification is reverse DNS to yandex.ru, yandex.net or yandex.com with forward confirmation; Yandex documents no IP range list.
Mozilla/5.0 (compatible; YandexRenderResourcesBot/1.0; +http://yandex.com/bots)What YandexRenderResourcesBot does
Requests from this bot carry the user-agent Mozilla/5.0 (compatible; YandexRenderResourcesBot/1.0; +http://yandex.com/bots). Yandex describes its job as loading resources for page rendering with JavaScript. Yandex does not enumerate which resource types it loads; the documentation says only that they are resources used in rendering. Whether Yandex renders a site with JavaScript at all is a per-site setting in Yandex Webmaster, under Indexing and then JavaScript page rendering, which Yandex labels as beta.
Yandex states that general robots.txt rules do not apply to this bot. If the HTML page that uses a resource is accessible to the Yandex bot, YandexRenderResourcesBot ignores robots.txt instructions covering that resource and fetches it anyway. If the HTML page is disallowed, the bot does not access the resources it uses. The way to keep the bot away from a resource is therefore to disallow the page that references it, since a rule on the resource path alone has no documented effect while the page stays open.
To confirm a request is from Yandex, run a reverse DNS lookup on the source IP and check that the hostname ends in yandex.ru, yandex.net or yandex.com, then resolve that hostname forward and confirm it returns the same IP. Yandex Webmaster also has an IP address check tool for the same purpose. Yandex documents no list of IP ranges for this bot, so address matching is not a documented option.
Operator note. It does not take into account the general rules in robots.txt. Yandex says only that it 'loads resources for page rendering with JavaScript' and does not enumerate resource types. JavaScript rendering itself is controlled per site in Yandex Webmaster (Indexing -> JavaScript page rendering, beta).
Controlling YandexRenderResourcesBot with robots.txt
Use the token YandexRenderResourcesBot in robots.txt. Yandex documents limits on how this bot applies robots.txt; see the operator note.
User-agent: YandexRenderResourcesBot
Disallow: /User-agent: YandexRenderResourcesBot
Allow: /Verifying a request is really YandexRenderResourcesBot
Anyone can put YandexRenderResourcesBot 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 YandexRenderResourcesBot?
Blocking it prevents Yandex from loading the resources it uses to render pages with JavaScript, which affects how Yandex sees pages that depend on those resources. A Disallow on the resource path alone has no effect while the page using it is allowed; Yandex only skips resources of pages that are themselves disallowed.
Does YandexRenderResourcesBot obey robots.txt?
Partially. Yandex says general robots.txt rules do not apply to it. It ignores robots.txt instructions for a resource when the HTML page that uses the resource is accessible to the Yandex bot, and it does not fetch resources belonging to pages that robots.txt disallows. Control access to the page and the bot's access to its resources follows.
How do I verify YandexRenderResourcesBot?
Reverse-resolve the source IP and check that the hostname ends in yandex.ru, yandex.net or yandex.com. Then forward-resolve that hostname and confirm it returns the original IP. Yandex Webmaster also has an IP address check tool. Yandex documents no IP range file for this bot.
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.