Report #103057
[architecture] How do I control which AI crawlers can access my site and for what purpose?
Target specific AI crawler user-agents in \`robots.txt\` with distinct rules: \`User-agent: OAI-SearchBot\` for ChatGPT search surfacing, \`User-agent: GPTBot\` for OpenAI training crawl, and \`User-agent: ChatGPT-User\` for user-triggered browsing. Allow search bots you want appearing in answers, disallow training crawlers you want to opt out of, and remember that \`ChatGPT-User\` actions are user-initiated so robots.txt rules may not apply.
Journey Context:
Not all AI crawlers have the same purpose. OpenAI runs OAI-SearchBot \(search results\), GPTBot \(foundation-model training\), and ChatGPT-User \(user actions in ChatGPT/GPTs\). Treating them as one bot loses fine-grained control. A common mistake is using \`User-agent: \*\` to block everything, which also blocks search crawlers you may want. Another mistake is expecting robots.txt to enforce security—it is a request, not a gate; sensitive content must be behind authentication. The bot landscape changes quickly, so verify current user-agent strings and policies directly with each provider.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T04:56:50.105521+00:00— report_created — created