Safe Official docs Search Engines

Yandex Render Resources

Operated by Yandex

Quick Facts

User-Agent:
YandexRenderResourcesBot
Category:
Search Engines
Operator:
Yandex
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
yandex.com

Confirmed by the operator

Yandex names YandexRenderResourcesBot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Yandex Render Resources?

Yandex Render Resources is an AI search-index crawler operated by Yandex. It collects and indexes web content so it can be surfaced as citations or answers inside Yandex's AI search experience. Allowing Yandex Render Resources can increase your visibility in AI-powered search results, which is why most sites choose to permit it.

Yandex Render Resources is an AI search-index crawler operated by Yandex. It collects and indexes web content so it can be surfaced as citations or answers inside Yandex's AI search experience. Allowing Yandex Render Resources can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Yandex Render Resources uses the user-agent token YandexRenderResourcesBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Yandex Render Resources?

🔶 AI Visibility Trade-off - Blocking Yandex Render Resources will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Yandex Render Resources with robots.txt

<code>User-agent: YandexRenderResourcesBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: YandexRenderResourcesBot Disallow: /
Allow all (robots.txt)
User-agent: YandexRenderResourcesBot Allow: /
Block private only (robots.txt)
User-agent: YandexRenderResourcesBot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Yandex Render Resources if ($http_user_agent ~* "YandexRenderResourcesBot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Yandex Render Resources SetEnvIfNoCase User-Agent "YandexRenderResourcesBot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Yandex Render Resources safe to allow?

Yes, Yandex Render Resources is a safe and legitimate crawler operated by Yandex. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Yandex Render Resources requests resolve to Yandex's domain.

What does Yandex Render Resources do?

Understanding Yandex Render Resources's purpose helps you decide whether to allow or block it.

  • Indexes web pages for AI-powered search answers
  • Surfaces your content as citations inside AI search results
  • Builds a knowledge index used to answer user questions
  • Allowing it can increase visibility in AI search
  • Respects robots.txt directives

Yandex Render Resources in context

Yandex Render Resources is a search engine crawler operated by Yandex. In plain terms, it builds a search or answer index. Our database files it under search engines and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 62 of the 63 search engines in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So Yandex Render Resources is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat Yandex Render Resources

Our robots.txt study of the Tranco top 10,000 did not track YandexRenderResourcesBot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Yandex Render Resources's operator does not clearly document how it treats robots.txt. Write the Yandex Render Resources rule anyway, then confirm in your logs that its requests stop.

Yandex crawlers and close alternatives

Yandex Render Resources is one of 39 Yandex crawlers in our database. A User-agent: YandexRenderResourcesBot group controls Yandex Render Resources only; the other Yandex tokens below need their own lines.

  • YandexRenderResourcesBot: this crawler (Tier 3)
  • YaDirectFetcher: Yandex Direct Fetcher, checks pages for an SEO, uptime or analytics service (Tier 3)
  • Yandex: Yandex, builds a search or answer index (Tier 3)
  • YandexAccessibilityBot: Yandex Accessibility, builds a search or answer index (Tier 3)
  • YandexAdditional: YandexAdditional, builds a search or answer index (Tier 3)
  • YandexAdditionalBot: YandexAdditionalBot, builds a search or answer index (Tier 3)
  • YandexAdNet: Yandex Advertising Network, checks pages for an SEO, uptime or analytics service (Tier 3)
  • YandexBlogs: Yandex Blogs, builds a search or answer index (Tier 3)
  • YandexBot: Yandex Search, builds a search or answer index (Tier 3)

To give Yandex Render Resources the same answer as its siblings, stack User-agent: YandexRenderResourcesBot with their lines above one set of rules; to treat Yandex Render Resources differently, give it its own group.

Other search engines that do the same job (builds a search or answer index) include Amzn-SearchBot from Amazon, Applebot from Apple, baidu from Baidu, Baiduspider from Baidu, Baiduspider-favo from Baidu, Baiduspider-image from Baidu. Deciding about Yandex Render Resources is usually a decision about the whole group, so check how your file treats these too.

We first recorded YandexRenderResourcesBot on September 22, 2026. Yandex documents it on yandex.com, and we recheck that page before each release.

Which rule Yandex Render Resources actually follows

Yandex Render Resources reads exactly one group in robots.txt, the most specific one that names YandexRenderResourcesBot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: YandexRenderResourcesBot
Disallow: /drafts/
  1. Find the group. Yandex Render Resources looks for a group naming YandexRenderResourcesBot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Yandex Render Resources, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Yandex Render Resources if the file also has a User-agent: YandexRenderResourcesBot group?

No. Once a group names it, Yandex Render Resources reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Yandex Render Resources remove your pages from AI answers?

Often, yes. Yandex Render Resources is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Related: writing content AI engines can cite

Test yourself: is User-agent: yandexrenderresourcesbot the same as User-agent: YandexRenderResourcesBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Yandex Render Resources? Decide by situation

Recommended setting for Yandex Render Resources by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. It is how this search engine finds your pages.
You license content and want to stop AI trainingBlocking it does not stop training, because Yandex Render Resources is a search engine crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless it is overloading your servers.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Yandex Render Resources on your own site

  1. Open /robots.txt on your domain and search for YandexRenderResourcesBot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Yandex Render Resources follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Yandex Render Resources even when robots.txt allows it, and that never shows in the file.
  4. Run our crawlability checker for AI search to see how Yandex Render Resources and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Yandex Render Resources

The errors we see most often with Yandex Render Resources in the files and firewalls we test:

  1. Blocking Yandex Render Resources to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
  2. Writing a User-agent: YandexRenderResourcesBot group to add one rule for Yandex Render Resources and accidentally dropping every rule it used to follow under User-agent: *.
  3. Disallowing CSS and JavaScript folders, which can stop Yandex Render Resources rendering your pages properly.

All three hide inside a file that looks correct, so check Yandex Render Resources from outside after every change.

Spotting Yandex Render Resources in your logs

robots.txt says what Yandex Render Resources may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "YandexRenderResourcesBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "YandexRenderResourcesBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Yandex Render Resources user-agent, so confirm the source before acting on a match:

  • YandexRenderResourcesBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Yandex Render Resources request with caution.

Frequently Asked Questions

What is the official user-agent string for Yandex Render Resources?
The official user-agent string for Yandex Render Resources is: YandexRenderResourcesBot. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Yandex Render Resources by performing a reverse-DNS lookup on the source IP.
Is Yandex Render Resources safe?
Yes, Yandex Render Resources is a safe and legitimate crawler operated by Yandex. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Yandex Render Resources hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Yandex Render Resources will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Yandex Render Resources in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: YandexRenderResourcesBot
Disallow: /

This instructs Yandex Render Resources not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Yandex Render Resources respect robots.txt?
Yandex Render Resources is operated by Yandex and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Yandex Render Resources is crawling my site?
Search your web server access logs for the string YandexRenderResourcesBot (case-insensitive: grep -i "YandexRenderResourcesBot" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us