Bot intelligence record
YandexUserproxy
Usually allowYandexUserproxy is a search crawler from Yandex used for search indexing, URL discovery, page rendering, result freshness; it appears in server logs as `YandexUserproxy`.
User-Agent Pattern
YandexYandexUserproxy
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: YandexUserproxy
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
YandexUserproxy is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Record Details
Structured data- Operator
- Yandex
- Family
- Yandex
- Type
- Search
- Purpose
- Search
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Official
- Verification
- Verify YandexUserproxy by matching `YandexUserproxy` to Yandex evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- YandexUserproxy has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
Notes
- YandexUserproxy is a search crawler from Yandex used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Its primary user-agent pattern is
YandexUserproxy; related patterns includeYandexUserproxy Yandex robot; a representative HTTP user-agent isMozilla/5.0 (compatible; YandexUserproxy/1.0; +http://yandex.com/bots). - YandexUserproxy is verified with High confidence. The identity type is Official Documented, and the evidence basis is official operator documentation.
- YandexUserproxy is marked as respecting robots.txt directives for crawler access control.
- YandexUserproxy can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify YandexUserproxy by matching `YandexUserproxy` to Yandex evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- YandexUserproxy traffic is primarily detected by the `YandexUserproxy` user-agent pattern; related patterns include `YandexUserproxy Yandex robot`; a representative HTTP user-agent is `Mozilla/5.0 (compatible; YandexUserproxy/1.0; +http://yandex.com/bots)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Yandex infrastructure before trusting the traffic.
- YandexUserproxy is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- YandexUserproxy has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
https://yandex.com/support/webmaster/en/robot-workings/check-yandex-robots
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.