Training, search and user fetches are different crawlers

Most AI companies run more than one crawler, and they do different jobs. Training crawlers like GPTBot and ClaudeBot collect content to train future models. Search crawlers like OAI-SearchBot and PerplexityBot index pages so an assistant can find and cite them in answers. User-requested fetchers like ChatGPT-User retrieve a page when someone asks about it directly.

That split matters. Blocking every AI crawler opts you out of training, but it also removes your pages from the AI answers that increasingly send traffic and brand mentions. For most publishers, the "block training, allow AI search" preset is the balanced choice. See our guide to generative engine optimization for why AI search visibility is worth keeping.

How to use the generated rules

Paste the output into your existing robots.txt rather than replacing it. Each blocked crawler gets its own group, and a crawler that matches a named group follows only that group, so your general User-agent: * rules still apply to every other bot. After you publish, open /robots.txt on your domain to confirm the rules are live.

Blocking AI search crawlers also takes you out of the citation pool entirely. If you want to be cited, the bigger levers are on the page itself — see how to structure content so ChatGPT quotes you.