ai-crawlers
Skill0 starsChanged 3 days agoMITView on GitHub
Check and fix which search and AI crawlers can reach a site: OAI-SearchBot, GPTBot, ChatGPT-User, Claude-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot and more, grouped by purpose (search, user fetch, training). Use when the user asks 'can ChatGPT/Claude/Perplexity see my site', 'should I block GPTBot', 'why isn't my site cited by AI', 'write my robots.txt for AI', 'is Cloudflare blocking AI bots', or wants to test a robots.txt draft. Uses the sitetiller CLI against the live robots.txt or a local draft.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-readySkill
- ai-citationsSkill
- ai-logsSkill
- ai-trackerSkill
- backlinksSkill
- cannibalizationSkill
- canonicalsSkill
- citabilitySkill
- comparison-pagesSkill
- competitorsSkill
- content-briefSkill
- content-decaySkill
- content-qualitySkill
- core-web-vitalsSkill
- ecommerce-seoSkill
- ga4-aiSkill
- ghost-publishSkill
- gsc-bingSkill
- hreflangSkill
- imagesSkill
- indexingSkill
- internal-linksSkill
- llms-txtSkill
- local-seoSkill
- measure-rollbackSkill
- onpageSkill
- platformsSkill
- pseo-quality-gateSkill
- quick-winsSkill
- redirects-migrationSkill
- schemaSkill
- seo-planSkill
- seo-reportSkill
- setupSkill
- site-architectureSkill
- sitemapsSkill
- static-site-publishSkill
- sxoSkill
- tech-auditSkill
- titles-metaSkill
- topic-clustersSkill
- weekly-checkSkill
- wordpress-publishSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Run the live check (add a path to test a section):
- Very specific: line 23
Read each bot's allowed, rule, line, group and purpose.
- Distinctive: line 27
If a search crawler is blocked and the user did not choose that, write the fix:
- Distinctive: line 30
Test the draft before the user publishes it:
- Distinctive: line 52
Never recommend blocking search crawlers unless the user asks for it.
- Distinctive: line 53
Do not claim blocking GPTBot removes content already collected.
- Very specific: line 54
Do not state any vendor behaviour that is not in references/sources.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI crawler access
Goal: tell the user exactly which crawlers can read their site, which rule decides it, and what to change so their choice is deliberate: usually search and answer crawlers allowed, training crawlers the user's call.
Inputs
- A site or page URL, or a local robots.txt draft.
- Optional: the user's policy ("stay in AI search, stay out of training", "block everything", "allow everything").
Steps
- Run the live check (add a path to test a section):
npx sitetiller crawlers example.com --json npx sitetiller crawlers example.com/docs/ --json - Read each bot's
allowed,rule,line,groupandpurpose. Group findings by purpose:- search: Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot. Blocked = cannot be cited in that engine's answers.
- user: ChatGPT-User, Claude-User, Perplexity-User. Fetches a person asked for. OpenAI and Perplexity say robots.txt may not apply.
- training: GPTBot, ClaudeBot, CCBot, Google-Extended and Applebot-Extended (tokens, not crawlers). Blocking does not remove the site from those vendors' search features.
- If a search crawler is blocked and the user did not choose that, write the fix:
- Blocked by its own named group → edit that group (the line number is in the output); do not add a second group for the same bot.
- Blocked by the
*group → add a named group above it. A named group replaces the*rules for that bot, so copy any*disallows the user still wants (admin, cart, search).
- Test the draft before the user publishes it:
npx sitetiller robots-test ./robots.txt / /pricing /docs/a /private/x --agents OAI-SearchBot,GPTBot,Googlebot - Remind the user that robots.txt is one gate. CDN/WAF bot settings (Cloudflare's Search/Training/Agent controls since 2026-09-15) can block a bot robots.txt allows. Ask them to check those settings, or analyse real visits with the
ai-logsskill.
Matching rules the tool follows (Google's documented behaviour)
- The most specific matching user-agent group applies; all other groups are ignored for that bot.
- Inside it, the longest matching path wins; on equal length, Allow wins.
*matches any characters,$anchors the end.- 4xx robots.txt (except 429) = no rules; 5xx = Google pauses crawling the whole site.
Output to the user
- One-line verdict per purpose ("Search and answer crawlers: 3 of 5 allowed").
- A table: crawler, owner, purpose, allowed/blocked, deciding rule and line.
- The exact robots.txt lines to change, as a diff, tested with
robots-test. - What this check cannot see (CDN rules, actual visits).
Content-Signal lines
Cloudflare's Content Signals Policy adds Content-Signal: search=yes, ai-input=yes, ai-train=no style lines to robots.txt. npx sitetiller crawlers <url> prints them with their line and group, and flags values other than yes or no. They state a preference about how content may be used (search index, AI answers grounded on the page, model training); they do not block anything and compliance is voluntary. To block a bot, use Disallow or a firewall rule. Cloudflare's managed robots.txt adds search=yes, ai-train=no and leaves ai-input unset.
Guardrails
- Never recommend blocking search crawlers unless the user asks for it; explain the visibility cost.
- Do not claim blocking GPTBot removes content already collected; vendors document it as a signal for future use.
- Do not state any vendor behaviour that is not in
references/sources.md; if unsure, say so.
References
examples/crawlers.json: real output of this skill's command on sitetiller.com (2026-11-13), seeexamples/README.md.references/sources.md: vendor documentation for every crawler, with access dates.references/policies.md: ready-made robots.txt policies.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

