What is YandexAdditional?
YandexAdditional is Yandex's dedicated user agent for content used by YandexGPT and other generative AI features. It is separate from YandexBot, the primary crawler that discovers and indexes pages for conventional Yandex Search. Blocking one does not automatically describe what the other may do.
Search with Yandex AI builds concise answers from web sources and normally includes references to those sources. Yandex says the feature scans for relevant information, analyzes it with a generative neural network in real time, and combines the findings into an answer. Pages must first be present in Yandex's main search index before they can participate in that workflow.
Yandex's robot catalog makes an unusual distinction for YandexAdditional and YandexAdditionalBot: these agents apply to pages already indexed by the primary crawler and do not make indexing requests themselves. A YandexAdditional hit should not be read as first-time discovery of a URL. Its documented purpose is to apply the site's AI-answer preference to material Yandex already knows about.
A specific robots.txt disallow tells Yandex not to use the affected page in Yandex AI answers. Yandex says the change takes effect after its robots recrawl the page, usually within 2 to 14 days. The directive does not remove the page from ordinary search results, which remain under YandexBot and the usual indexing controls.
This entry is categorized for AI training because it collects content for YandexGPT and other generative products. Yandex's webmaster documentation, however, makes a narrower public commitment about appearance in AI answers and does not say that a YandexAdditional request proves inclusion in model training data. The safe conclusion is that the token controls generative product use, not that every fetched page trains a model.
The recorded token is YandexAdditional, and Yandex also documents the YandexAdditionalBot variant. The crawler respects rules addressed to those exact names. Yandex warns that some non-indexing robots may ignore restrictions written only for User-agent: *, so use a dedicated group. No signed-request directory or IP verification method is recorded for this entry.
