Categories

The seven request categories and the extra policy keys for unverifiable bots, trap followers, secret probes, robots.txt violations and bursts.

On this page

With AI Crawl Control on, each request gets exactly one category.

CategoryDashboardWhat it is
ai_trainingAI CrawlerCrawlers that collect content to train models (GPTBot, ClaudeBot, CCBot, Google-Extended…).
ai_searchAI SearchCrawlers of AI search engines that index pages to cite them (OAI-SearchBot, PerplexityBot…).
ai_user_agentAI AssistantAgents that fetch a page because a person just asked an assistant (ChatGPT-User, Perplexity-User, Web Bot Auth signatures).
search_engineSearch Engine CrawlerClassic search engines (Googlebot, Bingbot, Applebot, DuckDuckBot…).
unverified_automationUnverified automationAutomation with no verifiable identity: headless browsers, Playwright, python-requests, curl/, an empty User-Agent, scanner behaviour, clients that followed the trap.
spoofedSpoofedClaims to be a catalog bot, and verification says otherwise.
humanHumanEverything else. Always allowed; not configurable.

Extra policy keys

Besides the six configurable categories, the policy has five keys for situations that can apply on top of the category. When several apply, the strongest action wins.

KeyDashboardWhen it applies
unverified_botCrawlers that can't be verifiedThe User-Agent names a catalog bot that publishes no IP ranges, reverse DNS or signatures (ClaudeBot, Bytespider…).
trap_hitFollowed the trapThe client (IP or TLS fingerprint) followed the trap link before.
secret_probeSecret probingThe path looks for secrets: .env and .env.*, terraform.tfstate*, /@fs/, serviceaccount/token, .git/config, .git/HEAD, .aws/credentials, id_rsa, wp-config.php.*, .npmrc, docker-compose*.yml, .DS_Store…
robots_violationrobots.txt violationsA catalog bot requests a path your robots.txt disallows for it (RFC 9309: the longest rule wins, Allow on a tie).
agent_burstComposed burstA code-mode agent fires many distinct endpoints within seconds, walks through ids or paginates systematically.

The edge reads the robots.txt responses that pass through it (and fetches it from your origin when it hasn't seen one for a name in 6 hours) to detect violations.

Actions

ActionDashboardEffect in enforce mode
allowAllowCount only.
logLogCount and record a notable event.
challengeChallengeThe browser challenge for HTML GET navigations; 403 JSON otherwise.
blockBlockThe block response: 403 and the block page by default.
tarpitTarpitA slow maze of generated pages for HTML GET; 403 otherwise. Needs tarpit.enabled.

GET /robots.txt is never challenged or blocked.

Last updated:

↑↓ to navigate↵ to openesc to close