# YandexFavicons

> Downloads your favicon so Yandex can show it beside your result. Documented as not taking the general robots.txt rules into account.

| field | value |
|---|---|
| operator | Yandex |
| category | Search engines |
| robots.txt token | `YandexFavicons` |
| user-agent contains | `YandexFavicons` |
| robots.txt | ignores the * group; obeys rules named for its own token |
| verify by | reverse DNS |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Your results in Yandex lose their icon. Cosmetic, and a * rule will not achieve it anyway.

## Full user-agent string

```
Mozilla/5.0 (compatible; YandexFavicons/1.0; +http://yandex.com/bots)
```

## Block it

```
User-agent: YandexFavicons
Disallow: /
```

## Allow it

```
User-agent: YandexFavicons
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is YandexFavicons?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=yandexfavicons&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/yandexfavicons.json · index: https://www.pathwren.workers.dev/llms.txt