YandexAdditional
YandexAdditional is blocked by 164 sites in the October 2026 survey, or 2.7% of readable files. The community reference lists its operator as Yandex.
Who runs YandexAdditional?
| Fact | YandexAdditional reference entry |
|---|---|
| Operator | “Yandex” |
| Purpose | “Scrapes/analyzes data for the YandexGPT LLM.” |
| Does YandexAdditional obey robots.txt? | “Yes” |
| Frequency | “No information.” |
| Cloudflare managed list for YandexAdditional | No |
These facts quote the stored community ai.robots.txt reference.
A matching description is used for 1 other entry. Counts below are specific to this crawler.
This entry’s stated use is quoted above. Allowing people to find and read a page need not include permission to gather it for model training. Owners can express those choices in crawler-specific groups.
How many sites block it?
Our readable sample has 164 whole-site blocks, 2.7% of 6,171 files, with Disallow: / as the instruction. Of that full sample, 63 name this crawler, or 1.0%. The count without a whole-site block is 6,007.
Breaking out the leading 1,000 sites gives 552 readable files, with 13 naming the crawler, or 2.4%. Whole-site blocking appears in 29 of them. Blocking is more common among the leading sites, at 5.3%. Beyond those ranks, 5,619 files have a blocking total of 135, 2.4% of that sample.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| YandexAdditional, all ranks | 63 | 1.0% | 164 | 2.7% |
| YandexAdditional, top 1,000 | 13 | 2.4% | 29 | 5.3% |
| YandexAdditional, remaining ranks | 50 | 0.9% | 135 | 2.4% |
Only whole-site blocks recorded against this crawler’s name count here. Rules addressed to every crawler are outside this count. Of 164 blocks, 106 do not also appear in our count of files naming it. We found 58 files naming it and blocking the whole site, along with 5 files naming it without that ban. Another 6,108 files omit the name. We ignore capitalization and repeated names.
How to block or allow it
These lines go in robots.txt at the root. User-agent: * yields to a group naming YandexAdditional under the robots.txt standard.
Block the whole site
User-agent: YandexAdditional
Disallow: /Allow access
User-agent: YandexAdditional
Allow: /It's the 98th most-named crawler of the 171 we counted in the crawler index.
Which other crawlers does this operator run?
How we counted
For YandexAdditional, the survey covered 10,000 top Tranco sites, collected on 19 October 2026. Files had an 8-second timeout and a 262,144-byte limit. Missing, unreachable and oversized files do not contribute to these shares. Repeat readings are included, using scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
Does a User-agent line mean it is blocked?
The 63 files naming it include 5 files without a whole-site ban.
What do the top-ranked sites show?
Its name appears in 2.4% of readable leading files and 1.0% overall. Blocking affects 5.3% in the leading group and 2.7% in all ranks.
Which nearby entry can I compare?
For comparison, Echobot Bot has 62 files naming it and 0 blocks, or 0.0%. Our counts for this entry are 63 files with the name and 164 blocking the whole site, or 2.7%.