Should you block AI crawlers? GPTBot, ClaudeBot and PerplexityBot, explained

Publishers block them; brands mostly shouldn't. What each crawler does, what blocking actually prevents, and a sane robots.txt policy for a SaaS.

Your server logs already show them: GPTBot, ClaudeBot, PerplexityBot, Google-Extended and a lengthening parade of AI user-agents. News publishers block them in droves, and you've probably seen the "block AI bots" checkbox in your CDN. We leave that checkbox off on tryzene.com, and we'd leave it off on almost any SaaS site. But the crawlers do different jobs, and the difference is what makes the call easy.

Three kinds of AI crawler

  • Training crawlers (GPTBot, ClaudeBot, Google-Extended, Meta's bots) collect text for future model training. Blocking them is a bet about models that ship years from now.
  • Retrieval / search crawlers (PerplexityBot, OAI-SearchBot, and friends) index pages so live AI search can find and cite you. Blocking these removes you from answers today.
  • On-demand fetchers (e.g. ChatGPT-User) fetch a page in real time because a user's question led there. Blocking these breaks the moment a model tries to read your pricing page mid-answer.

Why publishers block, and why you're not them

A news site's product is its text: an AI that summarizes the article is a substitute for the visit, so blocking training bots is a rational licensing position. Your marketing site is the opposite case - its entire purpose is to be read, understood and repeated. When a model summarizes your features page inside an answer, the page is doing exactly its job. A publisher can reasonably say "stop taking my content"; a marketing site is a brochure you printed hoping someone would repeat it.

The asymmetry that decides it: blocking training bots can't remove what previous crawls already captured, but it does exclude you from future model memory - while your competitors' docs stay in the corpus.

A sane robots.txt policy for a SaaS

  • Marketing surface open to everything: home, features, pricing, blog, docs, comparisons - every crawler, AI included.
  • App and auth surface closed to everyone: dashboards, settings, checkout. No crawler has business there (we disallow ours for all user-agents).
  • Verify, don't trust. Well-behaved crawlers respect robots.txt; impersonators exist. The major vendors publish IP ranges if you need to enforce at the CDN - here's how to find and verify AI crawlers in your server logs.
  • Revisit yearly. The crawler list grows; policy is a living file.

This is exactly the policy on tryzene.com's own robots.txt - open marketing pages, closed app, AI crawlers welcome. We build a tool whose whole premise is that models read your site and repeat what they find; blocking them on our own domain would be malpractice.


To confirm they can actually reach and read your pages, check your site's AI readiness score. Letting the crawlers in only gets you read - it doesn't get you mentioned. Run a free audit and see what the engines actually do with the access you're giving them.

Frequently asked questions

Should I block AI crawlers like GPTBot and ClaudeBot on my site?

For most SaaS marketing sites, no. Your marketing site's entire purpose is to be read, understood and repeated, so a model summarising your features page inside an answer is the page doing exactly its job. News publishers block these bots because their product is the text itself, but a brochure site is the opposite case.

What's the difference between the various AI crawlers?

There are three kinds. Training crawlers like GPTBot and Google-Extended collect text for future model training, so blocking them is a bet about models that ship years from now. Retrieval crawlers like PerplexityBot index pages so live AI search can find and cite you, and on-demand fetchers like ChatGPT-User load a page in real time during an answer - blocking either of those removes you from answers today.

What's a sensible robots.txt policy for a SaaS?

Open your marketing surface to everything - home, features, pricing, blog, docs and comparisons, AI crawlers included - and close your app and auth surface to every crawler, since dashboards, settings and checkout have no business being indexed. Remember that well-behaved crawlers respect robots.txt while impersonators exist, so verify against published IP ranges at the CDN if you need to enforce it, and revisit the file yearly as the crawler list grows.

Muhammet İLBAŞ
Written by
Muhammet İLBAŞ
Founder & engineer, building Zene in public
Share

Put it into practice

Free AI visibility checker →Schema markup generator →llms.txt generator →All free toolsCompare Zene vs alternatives

Keep reading

All articles →

Find out if AI recommends you.

Put this guide into practice - get your free visibility score in minutes.

Zene dashboard: a brand's AI visibility score, the next automatic scan, and per-engine cards for ChatGPT, Claude, Gemini and Perplexity