# YandexFeed

Operator: Yandex
Purpose: User-requested fetch
Reviewed: 2026-09-14
HTTP identifier: YandexFeed
robots.txt token: YandexFeed

## What is YandexFeed?

Retrieves owner-submitted structured feeds.

## How to identify it

Look for the YandexFeed identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

## How to check identity

Confirm reverse DNS under yandex.ru, yandex.net or yandex.com, then resolve that hostname back to the original request IP.

## Access and robots.txt

General wildcard robots.txt rules may be ignored. Yandex documents named-client Disallow rules for these crawlers; site-specific agreements can create exceptions.

Optional full-site opt-out; merge with existing rules only if intended. Not a security control.

```text
User-agent: YandexFeed
Disallow: /
```

## What it means in your analytics

A feed fetch may be part of a configured service integration.

## Useful measures

Requested URLs; Response codes; Redirect chains.

## What to check next

Validate the submitted feed and its authentication requirements.

## Sources

- [yandex.ru](https://yandex.ru/support/webmaster/ru/robot-workings/check-yandex-robots)

Operator facts are source-backed; interpretation and actions are Apostl guidance.

## Related profiles

- [YandexBot](https://apostl.dev/bots/yandexbot)
- [YandexImages](https://apostl.dev/bots/yandeximages)
- [YandexVideo](https://apostl.dev/bots/yandexvideo)

[Start measuring agent traffic](https://apostl.dev/start/agent-analytics)