Safe Official docs Search Engines

Yandex Calendar

Operated by Yandex

Quick Facts

User-Agent:
YandexCalendar
Category:
Search Engines
Operator:
Yandex
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
yandex.com

Confirmed by the operator

Yandex names YandexCalendar on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Yandex Calendar?

Yandex Calendar is an on-demand AI fetcher operated by Yandex. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Yandex's assistant.

Yandex Calendar is an on-demand AI fetcher operated by Yandex. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Yandex's assistant.
Yandex Calendar uses the user-agent token YandexCalendar. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Yandex Calendar?

🔶 AI Visibility Trade-off - Blocking Yandex Calendar will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Yandex Calendar with robots.txt

<code>User-agent: YandexCalendar</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: YandexCalendar Disallow: /
Allow all (robots.txt)
User-agent: YandexCalendar Allow: /
Block private only (robots.txt)
User-agent: YandexCalendar Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Yandex Calendar if ($http_user_agent ~* "YandexCalendar") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Yandex Calendar SetEnvIfNoCase User-Agent "YandexCalendar" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Yandex Calendar safe to allow?

Yes, Yandex Calendar is a safe and legitimate crawler operated by Yandex. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Yandex Calendar requests resolve to Yandex's domain.

What does Yandex Calendar do?

Understanding Yandex Calendar's purpose helps you decide whether to allow or block it.

  • Fetches a page only when a user asks an AI assistant to read it
  • Summarizes or extracts the URL the user provided
  • Triggered by real user intent, not bulk crawling
  • Low traffic volume compared with training crawlers
  • Blocking it prevents users from pulling your content into the assistant

Yandex Calendar in context

Yandex Calendar is a user-triggered agent operated by Yandex. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under search engines and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 62 of the 63 search engines in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Yandex Calendar rests on what you want from Yandex, not on its behaviour. How we rate safety and impact.

How site owners treat Yandex Calendar

Our robots.txt study of the Tranco top 10,000 did not track YandexCalendar as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Yandex Calendar's operator does not clearly document how it treats robots.txt. Write the Yandex Calendar rule anyway, then confirm in your logs that its requests stop.

Yandex crawlers and close alternatives

Yandex Calendar is one of 39 Yandex crawlers in our database. A User-agent: YandexCalendar group controls Yandex Calendar only; the other Yandex tokens below need their own lines.

  • YandexCalendar: this crawler (Tier 3)
  • YaDirectFetcher: Yandex Direct Fetcher, checks pages for an SEO, uptime or analytics service (Tier 3)
  • Yandex: Yandex, builds a search or answer index (Tier 3)
  • YandexAccessibilityBot: Yandex Accessibility, builds a search or answer index (Tier 3)
  • YandexAdditional: YandexAdditional, builds a search or answer index (Tier 3)
  • YandexAdditionalBot: YandexAdditionalBot, builds a search or answer index (Tier 3)
  • YandexAdNet: Yandex Advertising Network, checks pages for an SEO, uptime or analytics service (Tier 3)
  • YandexBlogs: Yandex Blogs, builds a search or answer index (Tier 3)
  • YandexBot: Yandex Search, builds a search or answer index (Tier 3)

To give Yandex Calendar the same answer as its siblings, stack User-agent: YandexCalendar with their lines above one set of rules; to treat Yandex Calendar differently, give it its own group.

No other crawler in our search engines category has exactly the same purpose, which makes Yandex Calendar an unusual case: decide about it on its own merits.

We first recorded YandexCalendar on September 22, 2026. Yandex documents it on yandex.com, and we recheck that page before each release.

Which rule Yandex Calendar actually follows

Yandex Calendar reads exactly one group in robots.txt, the most specific one that names YandexCalendar, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: YandexCalendar
Disallow: /drafts/
  1. Find the group. Yandex Calendar looks for a group naming YandexCalendar. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Yandex Calendar, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Yandex Calendar if the file also has a User-agent: YandexCalendar group?

No. Once a group names it, Yandex Calendar reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Yandex Calendar remove your pages from AI answers?

Often, yes. Yandex Calendar is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: yandexcalendar the same as User-agent: YandexCalendar?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Yandex Calendar? Decide by situation

Recommended setting for Yandex Calendar by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Yandex Calendar fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Yandex Calendar is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it unless it is overloading your servers.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Yandex Calendar on your own site

  1. Open /robots.txt on your domain and search for YandexCalendar. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Yandex Calendar follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Yandex Calendar even when robots.txt allows it, and that never shows in the file.
  4. Run our live AI crawler test to see how Yandex Calendar and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Yandex Calendar

The errors we see most often with Yandex Calendar in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Yandex Calendar. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Yandex Calendar as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Yandex Calendar visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Yandex Calendar from outside after every change.

Spotting Yandex Calendar in your logs

robots.txt says what Yandex Calendar may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "YandexCalendar" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "YandexCalendar" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Yandex Calendar user-agent, so confirm the source before acting on a match:

  • YandexCalendar: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Yandex Calendar request with caution.

Frequently Asked Questions

What is the official user-agent string for Yandex Calendar?
The official user-agent string for Yandex Calendar is: YandexCalendar. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Yandex Calendar by performing a reverse-DNS lookup on the source IP.
Is Yandex Calendar safe?
Yes, Yandex Calendar is a safe and legitimate crawler operated by Yandex. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Yandex Calendar hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Yandex Calendar will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Yandex Calendar in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: YandexCalendar
Disallow: /

This instructs Yandex Calendar not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Yandex Calendar respect robots.txt?
Yandex Calendar is operated by Yandex and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Yandex Calendar is crawling my site?
Search your web server access logs for the string YandexCalendar (case-insensitive: grep -i "YandexCalendar" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us