yacy
SafeUser-agent: yacy
Category: Data Scrapers
SEO impact if blocked: 2/10
2 crawlers operated by YaCy Community
YaCy Community operates 2 crawlers in our directory, filed under Data Scrapers. Of those 2, 2 rated safe for crawl behaviour.
Blocking YaCy Community carries an SEO impact score of 2/10 across its crawlers. Every crawler here carries the same blocking impact: Low - No SEO ranking impact.
Our recommendation for YaCy Community, set by its least reassuring crawler (yacy, rated safe): Generally safe to allow; provides legitimate crawling value.
| Operator | YaCy Community |
|---|---|
| Crawlers in directory | 2 |
| Categories | Data Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 2 rated safe |
| Official crawler docs | YaCy Community crawler documentation |
YaCy Community runs 2 crawlers in our database. Grouped by the job each one does:
yacy, yacybotThe highest-priority token is Tier 6. That makes YaCy Community a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
None of YaCy Community's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
A robots.txt file cannot say "YaCy Community"; it can only name YaCy Community's tokens, one group at a time. So "block YaCy Community" really means naming each of its 2 tokens, and you can give them different answers.
# Allow YaCy Community search and assistants, refuse training
User-agent: yacy
Disallow: /
User-agent: yacy
User-agent: yacybot
Allow: /
User-agent: *.* group, so copy any Disallow lines you still want it to obey.User-agent: YaCy Community block all of YaCy Community's crawlers?No. robots.txt matches crawler tokens, not company names. Name each token: yacy, yacybot.
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
A one-paragraph brief for every YaCy Community token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
yacy, Tier 6): a retrieval crawler that feeds AI search answers that builds a search or answer index. Rated safe. yacy's operator does not clearly document how it treats robots.txt. Write the yacy rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.yacybot, Tier 6): a retrieval crawler that feeds AI search answers that builds a search or answer index. Rated safe. yacybot's operator does not clearly document how it treats robots.txt. Write the yacybot rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.The errors we see most often with YaCy Community's crawlers in the files and firewalls we test:
User-agent: yacy group exists, YaCy Community's crawlers ignores every rule under User-agent: *.All three hide inside a file that looks correct, so check YaCy Community's crawlers from outside after every change.
robots.txt says what yacy and yacybot may do; your access logs show what they actually did.
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "yacy|yacybot" /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 "yacy|yacybot" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20
Anyone can send these user-agents, so confirm the source before acting on a match:
yacy: we hold no published IP list, so use reverse DNS where YaCy Community documents a hostname and treat an unverifiable yacy request with caution. Check it separately from yacybot.yacybot: we hold no published IP list, so use reverse DNS where YaCy Community documents a hostname and treat an unverifiable yacybot request with caution. Check it separately from yacy.Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from YaCy Community's marketing. It covers 2 YaCy Community tokens in turn.
yacy in our recordsWe first recorded yacy on March 17, 2026. YaCy Community documents it on yacy.net, and we recheck that page before each release. No file in our top-10,000 scans names yacy, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, yacy sits 38th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 29 of the 39 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for yacy is usually a policy for these too.
yacyTeams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the yacy entry reads:
User-agent: yacy
Allow: /
Paste the line into the validator with one of your own URLs before it goes live. Revisit the yacy entry once a quarter, or when YaCy Community publishes a new token next to it.
yacybot in our recordsWe first recorded yacybot on March 17, 2026. YaCy Community documents it on yacy.net, and we recheck that page before each release. No file in our top-10,000 scans names yacybot, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, yacybot sits 39th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 29 of the 39 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for yacybot is usually a policy for these too.
yacybotTeams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the yacybot entry reads:
User-agent: yacybot
Allow: /
Paste the line into the validator with one of your own URLs before it goes live. Revisit the yacybot entry once a quarter, or when YaCy Community publishes a new token next to it.
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for YaCy Community's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch YaCy Community's crawlers too.
yacy, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.User-agent group per decision and repeat any shared rules inside it.These rules cover all 2 crawlers YaCy Community operates. Add them to the robots.txt file at the root of your domain.
These YaCy Community rules ask; they do not enforce. If a YaCy Community token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Text size
Saved on this device only. Drag the round button to move it. Accessibility statement