YandexVertis

Safe Block: Depends Verified robots.txt: Yes

This Botcrawl listing helps site owners recognize Yandex traffic from the YandexVertis user-agent pattern and review its classification, trust signals, and blocking guidance.

Common use category: search indexing or content discovery. Confirm the user-agent against server logs before relying on this entry because user-agent strings can be copied or spoofed.

Key facts

Operator
Yandex
Family
Yandex
Purpose
Indexing
User-Agent
YandexVertis
Should you block it?
Depends
Verified
Yes
Respects robots.txt
Yes
Identity type
Official Documented
Confidence
High
Last verified
2026-04-29
Last checked
2026-04-29

Bot details

Identity

User-Agent
YandexVertis
robots.txt token
YandexVertis
HTTP user-agent
Mozilla/5.0 (compatible; YandexVertis/1.0; +http://yandex.com/bots)
Aliases
YandexVertis Yandex robot

Ownership

Operator
Yandex
Family
Yandex
Type
Search
Purpose
Indexing

Verification and trust

Source type
Official
Confidence
High
Last verified
2026-04-29
Last checked
2026-04-29
Verification
Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.
Spoofing risk
Yandex user-agent strings are often spoofed. Verify the source host with reverse DNS and forward DNS before allow-listing.

Blocking and detection

Robots

User-agent: YandexVertis Disallow: /

Cloudflare

(http.user_agent contains "YandexVertis")
Advanced server rules

Apache

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} YandexVertis [NC]
RewriteRule ^ - [F,L]

Nginx

if ($http_user_agent ~* "YandexVertis") { return 403; }

Notes

YandexVertis is documented here as part of the Botcrawl bot directory so site owners can identify and review automated traffic that presents with the YandexVertis user-agent pattern.

Identification

  • User-agent pattern: YandexVertis
  • Operator: Yandex
  • robots.txt token: YandexVertis
  • HTTP user-agent: Mozilla/5.0 (compatible; YandexVertis/1.0; +http://yandex.com/bots)

Classification

  • Type: search
  • Kind: crawler
  • Purpose: search indexing or content discovery
  • Risk: safe
  • Suggested action: depends

Verification

The row includes an official source URL and is marked as verified in the imported metadata. Confidence is listed as high, and the last verification date is 2026-04-29.

Handling Guidance

Start by logging or rate limiting this traffic, then decide whether to allow or block it based on volume, source, and site context. The imported metadata says it respects robots.txt.

Use the user-agent pattern as one signal only. For stronger decisions, compare it with request rate, IP ownership, reverse DNS, authentication context, referrer behavior, and whether the traffic is expected for services used by the site.

Evidence and source

  • Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.
  • Common use category: search indexing or content discovery. Confirm the user-agent against server logs before relying on this entry because user-agent strings can be copied or spoofed.
  • Yandex user-agent strings are often spoofed. Verify the source host with reverse DNS and forward DNS before allow-listing.

WordPress Bot Protection

Bot Blocker for WordPress

Detect bot traffic, monitor live activity, apply bot-aware rules, and control AI crawlers, scrapers, scanners, spam bots, and fake trusted bots from one clean WordPress admin interface.