Bot intelligence record

YandexMobileScreenShotBot

Usually allow

Use the YandexMobileScreenShotBot identifier to separate Yandex link preview, prefetch, or user-triggered rendering traffic from normal visitor requests in server logs.

Preview Official Documented Confidence: High Verified: Yes robots.txt: No
Operator
Yandex
Family
Yandex
Type
Preview
Source type
Official
Last checked
2026-05-20

User-Agent Pattern

Yandex
YandexMobileScreenShotBot
Verification note

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 copy
User-agent: YandexMobileScreenShotBot Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.

Record Details

Structured data
Operator
Yandex
Family
Yandex
Type
Preview
Purpose
Preview
Identity type
Official Documented
Confidence
High
Last verified
2026-04-29
Last checked
2026-05-20
Source type
Official
Verification
Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.
Spoofing risk
Yandex user-agent strings are often spoofed. Verify the source host with reverse DNS and forward DNS before allow-listing.

Notes

YandexMobileScreenShotBot is listed in the Botcrawl directory as a preview or prefetch bot from Yandex. The primary identifier for log review is YandexMobileScreenShotBot.

Identification

  • User-agent pattern: YandexMobileScreenShotBot
  • Family: Yandex
  • Type: Preview
  • Kind: Preview

Common use

Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.

Verification and handling

Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.

Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Verify with reverse DNS and forward DNS checks; valid Yandex hosts end in yandex.ru, yandex.net, or yandex.com.
  • Match `YandexMobileScreenShotBot` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
  • Yandex user-agent strings are often spoofed. Verify the source host with reverse DNS and forward DNS before allow-listing.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.