Yandex
YandexBot
Indexes pages for Yandex Search.
Web searchUser-requested fetch
YandexCalendar
Retrieves user-subscribed calendar files.
Operated by Yandex
See your agent traffic PurposeUser-requested fetch
HTTP identifierYandexCalendar
IdentityVerify beyond the name
THE SIGNAL
What this visit tells you
Calendar refreshes may repeatedly request one feed.
Requested URLs
Response codes
Redirect chains
Your next move
Check calendar MIME types and subscription URL redirects.
The technical details
MarkdownHow to identify it
Look for the YandexCalendar 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. robots.txt does not secure private content.
User-agent: YandexCalendar
Disallow: /Seeing 403 or 404 responses?
403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.
Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.
SourcesReviewed 2026-09-14
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
APOSTL PulseSee YandexCalendar in context
See their requests. Find the pages that matter.
See your agent trafficKEEP EXPLORING
Different bots, different intent
Yandex
YandexImages
Indexes pictures for Yandex Images.
Web searchYandex
YandexVideo
Indexes video for Yandex search.
Web search