Yandex Vertis
Operated by Yandex
Quick Facts
- User-Agent:
- YandexVertis
- 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 YandexVertis 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 Vertis?
Yandex Vertis 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 Vertis can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Yandex Vertis 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 Vertis can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Yandex Vertis uses the user-agent token YandexVertis. 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 Vertis?
How to block Yandex Vertis with robots.txt
<code>User-agent: YandexVertis</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Yandex Vertis safe to allow?
What does Yandex Vertis do?
Understanding Yandex Vertis'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 Vertis in context
Yandex Vertis 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 not documented. So the decision about Yandex Vertis rests on what you want from Yandex, not on its behaviour. How we rate safety and impact.
How site owners treat Yandex Vertis
Our robots.txt study of the Tranco top 10,000 did not track YandexVertis 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 Vertis's operator does not clearly document how it treats robots.txt. Write the Yandex Vertis rule anyway, then confirm in your logs that its requests stop.
Yandex crawlers and close alternatives
Yandex Vertis is one of 39 Yandex crawlers in our database. A User-agent: YandexVertis group controls Yandex Vertis only; the other Yandex tokens below need their own lines.
YandexVertis: 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 Vertis the same answer as its siblings, stack User-agent: YandexVertis with their lines above one set of rules; to treat Yandex Vertis 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 Vertis is usually a decision about the whole group, so check how your file treats these too.
We first recorded YandexVertis on September 22, 2026. Yandex documents it on yandex.com, and we recheck that page before each release.
Which rule Yandex Vertis actually follows
Yandex Vertis reads exactly one group in robots.txt, the most specific one that names YandexVertis, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: YandexVertis
Disallow: /drafts/
- Find the group. Yandex Vertis looks for a group naming
YandexVertis. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Yandex Vertis, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to Yandex Vertis if the file also has a User-agent: YandexVertis group?
No. Once a group names it, Yandex Vertis reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Yandex Vertis remove your pages from AI answers?
Often, yes. Yandex Vertis is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: yandexvertis the same as User-agent: YandexVertis?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Yandex Vertis? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Allow it. It is how this search engine finds your pages. |
| You license content and want to stop AI training | Blocking it does not stop training, because Yandex Vertis is a search engine crawler. Block the operator's training crawler instead. |
| You run an online shop | Allow it unless it is overloading your servers. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Yandex Vertis on your own site
- Open
/robots.txton your domain and search forYandexVertis. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Yandex Vertis follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse Yandex Vertis even when robots.txt allows it, and that never shows in the file.
- Run our AI bot access checker to see how Yandex Vertis and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Yandex Vertis
The errors we see most often with Yandex Vertis in the files and firewalls we test:
- Blocking Yandex Vertis to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
- Writing a
User-agent: YandexVertisgroup to add one rule for Yandex Vertis and accidentally dropping every rule it used to follow underUser-agent: *. - Disallowing CSS and JavaScript folders, which can stop Yandex Vertis rendering your pages properly.
All three hide inside a file that looks correct, so check Yandex Vertis from outside after every change.
Spotting Yandex Vertis in your logs
robots.txt says what Yandex Vertis 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 "YandexVertis" /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 "YandexVertis" /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 Vertis user-agent, so confirm the source before acting on a match:
YandexVertis: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Yandex Vertis request with caution.
Frequently Asked Questions
What is the official user-agent string for Yandex Vertis?
YandexVertis. 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 Vertis by performing a reverse-DNS lookup on the source IP.Is Yandex Vertis safe?
Will blocking Yandex Vertis hurt my SEO?
How do I block Yandex Vertis in robots.txt?
/robots.txt file:User-agent: YandexVertis Disallow: /
This instructs Yandex Vertis not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Yandex Vertis respect robots.txt?
/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 Vertis is crawling my site?
YandexVertis (case-insensitive: grep -i "YandexVertis" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).