Bot intelligence record

YandexMetrika

Usually allow

Use the YandexMetrika identifier to separate Yandex uptime, accessibility, or site-health monitoring traffic from normal visitor requests in server logs.

Monitoring Monitoring Official Documented Confidence: High Verified: Yes robots.txt: No

User-Agent Pattern

Yandex
YandexMetrika

Robots.txt Snippet

Copy-ready
User-agent: YandexMetrika Disallow: /

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.

Record Details

Structured data
Operator
Yandex
Family
Yandex
Type
Monitoring
Purpose
Monitoring
Identity type
Official Documented
Confidence
High
Last verified
2026-04-29
Last checked
2026-05-20
Source type
Official
Spoofing risk
Yandex user-agent strings are often spoofed. Verify the source host with reverse DNS and forward DNS before allow-listing.

Notes

YandexMetrika is listed in the Botcrawl directory as a monitoring bot from Yandex. The primary identifier for log review is YandexMetrika.

Identification

  • User-agent pattern: YandexMetrika
  • Family: Yandex
  • Type: Monitoring
  • Kind: Monitor

Common use

Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.

Verification and handling

Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.

Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.
  • Match `YandexMetrika` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Uptime checks, managed website monitoring, synthetic tests, accessibility scans, or site-health reviews.
  • 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

Monitor bot traffic, review live activity, and control AI crawlers, scrapers, scanners, spam bots, and fake trusted bots from one clean WordPress dashboard.