YaDirectFetcher user agent
Operated by Yandex
YaDirectFetcher is the Yandex robot that checks ad landing pages for availability and topic.
The YaDirectFetcher bot at a glance
- YaDirectFetcher is operated by Yandex and checks landing pages for an advertising platform.
- The robots.txt token for YaDirectFetcher is YaDirectFetcher.
- Blocking a platform fetcher has no effect on organic search rankings.
- YaDirectFetcher robots.txt support: No.
- Recommendation for Generative Engine Optimization (GEO): Allow.
What is YaDirectFetcher?
Yandex states it does not use robots.txt.
Yandex lists this robot on its official page of Yandex robots.
Should you block YaDirectFetcher?
Allow YaDirectFetcher unless it causes a measurable load problem.
| Effect on search rankings | Blocking a platform fetcher has no effect on organic search rankings. |
|---|---|
| Effect on AI visibility | Blocking breaks the feature the fetcher serves, such as ad approval or feed updates. |
| Follows robots.txt | No |
| Recommendation | Allow |
How to block or allow YaDirectFetcher
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token YaDirectFetcher is matched case-insensitively. robots.txt alone may not stop YaDirectFetcher, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block YaDirectFetcher
User-agent: YaDirectFetcher
Disallow: /robots.txt: allow
# Allow YaDirectFetcher
User-agent: YaDirectFetcher
Allow: /robots.txt: partial
# Keep YaDirectFetcher out of private areas only
User-agent: YaDirectFetcher
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to YaDirectFetcher
if ($http_user_agent ~* "(YaDirectFetcher)") {
return 403;
}Apache
# Apache .htaccess: return 403 to YaDirectFetcher
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (YaDirectFetcher) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "YaDirectFetcher")How to verify real YaDirectFetcher traffic
Reverse DNS check: look up the request IP, confirm the hostname ends in yandex.ru, yandex.net, yandex.com, then look up that hostname and confirm it returns the same IP.
# 1. Reverse lookup: the hostname must end in yandex.ru, yandex.net, yandex.com
host REQUEST_IP
# 2. Forward lookup: must return the same REQUEST_IP
host HOSTNAME_FROM_STEP_1How to find YaDirectFetcher in your server logs
Search the web server access log for the token. The command below counts YaDirectFetcher requests per URL on Nginx or Apache.
grep -i "YaDirectFetcher" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
YaDirectFetcher user agent string
The full user agent Yandex publishes for YaDirectFetcher. Version numbers such as Chrome/W.X.Y.Z change over time, so match the token, not the whole string.
Mozilla/5.0 (compatible; YaDirectFetcher/1.0; Dyatel; +http://yandex.com/bots)YaDirectFetcher FAQ
YaDirectFetcher identifies itself with the robots.txt token "YaDirectFetcher". A typical request header reads: Mozilla/5.0 (compatible; YaDirectFetcher/1.0; Dyatel; +http://yandex.com/bots)
No reliable evidence says it does. Reports show YaDirectFetcher crawling sites that disallow it, so pair robots.txt with a firewall or server rule.
Blocking a platform fetcher has no effect on organic search rankings. Blocking breaks the feature the fetcher serves, such as ad approval or feed updates.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: YaDirectFetcher" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Yes. Run a reverse DNS lookup on the request IP; a real YaDirectFetcher request resolves to yandex.ru, yandex.net, yandex.com, and a forward lookup of that hostname returns the same IP.
Search your server access log for "YaDirectFetcher", for example with: grep -i "YaDirectFetcher" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Yandex crawler documentation. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
