Safe Official docs SEO Tools

Yandex Metrica

Operated by Yandex

Quick Facts

User-Agent:
YandexMetrika
Category:
SEO Tools
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 YandexMetrika 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 Metrica?

Yandex Metrica is a monitoring and validation agent operated by Yandex. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.

Yandex Metrica is a monitoring and validation agent operated by Yandex. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Yandex Metrica uses the user-agent token YandexMetrika. 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 Metrica?

🔶 AI Visibility Trade-off - Blocking Yandex Metrica 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 Metrica with robots.txt

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

Block completely (robots.txt)
User-agent: YandexMetrika Disallow: /
Allow all (robots.txt)
User-agent: YandexMetrika Allow: /
Block private only (robots.txt)
User-agent: YandexMetrika Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Yandex Metrica if ($http_user_agent ~* "YandexMetrika") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Yandex Metrica SetEnvIfNoCase User-Agent "YandexMetrika" 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 Metrica safe to allow?

Yes, Yandex Metrica 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 Metrica requests resolve to Yandex's domain.

What does Yandex Metrica do?

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

  • Validates pages, ads, or policy compliance
  • Performs automated quality and safety checks
  • Does not collect training data
  • No impact on search rankings
  • Generally safe to allow

Yandex Metrica in context

Yandex Metrica is a utility crawler operated by Yandex. In plain terms, it checks pages for an SEO, uptime or analytics service. Our database files it under SEO tools and ranks it Tier 4, specialist crawlers that matter to particular sites or markets. 19 of the 19 SEO tools in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Yandex Metrica rests on what you want from Yandex, not on its behaviour. How we rate safety and impact.

How site owners treat Yandex Metrica

Our robots.txt study of the Tranco top 10,000 did not track YandexMetrika 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 Metrica's operator does not clearly document how it treats robots.txt. Write the Yandex Metrica rule anyway, then confirm in your logs that its requests stop.

Yandex crawlers and close alternatives

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

  • YandexMetrika: this crawler (Tier 4)
  • 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 Metrica the same answer as its siblings, stack User-agent: YandexMetrika with their lines above one set of rules; to treat Yandex Metrica differently, give it its own group.

Other SEO tools that do the same job (checks pages for an SEO, uptime or analytics service) include AhrefsBot from Ahrefs, AhrefsSiteAudit from Ahrefs, AwarioBot from Awario, AwarioRssBot from Awario, AwarioSmartBot from Awario, Chrome-Lighthouse from Google. Deciding about Yandex Metrica is usually a decision about the whole group, so check how your file treats these too.

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

Which rule Yandex Metrica actually follows

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

User-agent: *
Disallow: /private/

User-agent: YandexMetrika
Disallow: /drafts/
  1. Find the group. Yandex Metrica looks for a group naming YandexMetrika. 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 Metrica, 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 Metrica if the file also has a User-agent: YandexMetrika group?

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

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

Often, yes. Yandex Metrica is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: yandexmetrika the same as User-agent: YandexMetrika?

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

Should you allow Yandex Metrica? Decide by situation

Recommended setting for Yandex Metrica by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because Yandex Metrica is a utility crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless your logs show it is costly.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Yandex Metrica on your own site

  1. Open /robots.txt on your domain and search for YandexMetrika. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Yandex Metrica 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 Metrica even when robots.txt allows it, and that never shows in the file.
  4. Run our website crawlability test to see how Yandex Metrica and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Yandex Metrica

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

  1. Treating Yandex Metrica as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when Yandex Metrica is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking Yandex Metrica by IP alone. Ranges change; match the token and verify with logs.

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

Spotting Yandex Metrica in your logs

robots.txt says what Yandex Metrica 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 "YandexMetrika" /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 "YandexMetrika" /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 Metrica user-agent, so confirm the source before acting on a match:

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

Frequently Asked Questions

What is the official user-agent string for Yandex Metrica?
The official user-agent string for Yandex Metrica is: YandexMetrika. 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 Metrica by performing a reverse-DNS lookup on the source IP.
Is Yandex Metrica safe?
Yes, Yandex Metrica 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 Metrica hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Yandex Metrica 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 Metrica in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: YandexMetrika
Disallow: /

This instructs Yandex Metrica not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Yandex Metrica respect robots.txt?
Yandex Metrica 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 Metrica is crawling my site?
Search your web server access logs for the string YandexMetrika (case-insensitive: grep -i "YandexMetrika" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us