Does blocking GPTBot block ChatGPT?
GPTBot, ChatGPT-User, and OAI-SearchBot are three different robots.txt tokens.
Last reviewed: August 14, 2026
No. Blocking GPTBot does not block ChatGPT. GPTBot is OpenAI's training crawler. ChatGPT-User fetches a page when a person asks ChatGPT to browse a URL. OAI-SearchBot indexes pages for ChatGPT search. A GPTBot Disallow is a training opt-out, not a live ChatGPT block.
How do GPTBot, ChatGPT-User, and OAI-SearchBot differ?
People treat the ChatGPT bot as one user-agent. OpenAI documents three. GPTBot crawls to collect training data. OAI-SearchBot crawls to build OpenAI's search index. ChatGPT-User fetches a page in response to a person asking ChatGPT to browse.
A Disallow under User-agent: GPTBot is a training opt-out. It is not the same as blocking ChatGPT-User. The reverse is also true: allowing GPTBot does not mean ChatGPT can live-fetch the page if ChatGPT-User is disallowed.
ChatGPT search citations go through OAI-SearchBot. Blocking ChatGPT-User targets on-demand browsing, not the search-index crawler. The Technical Access pillar scores those tokens as separate robots.txt groups.
| User-agent | Vendor | Purpose | If you block it |
|---|---|---|---|
| GPTBot | OpenAI | training | Training opt-out. Does not block ChatGPT-User or OAI-SearchBot. |
| ChatGPT-User | OpenAI | retrieval | Blocks on-demand ChatGPT browsing. Does not block GPTBot or ChatGPT search. |
| OAI-SearchBot | OpenAI | retrieval | Blocks ChatGPT search indexing. Does not block GPTBot or ChatGPT-User. |
| Googlebot | classic search | Blocks classic Google Search. Does not apply to Google-Extended. | |
| Google-Extended | retrieval | Does not block Googlebot. Separate Gemini and AI Overviews token. | |
| PerplexityBot | Perplexity | retrieval | Blocks Perplexity's search-index crawler. Does not block Perplexity-User. |
| Perplexity-User | Perplexity | retrieval | Blocks Perplexity's on-demand fetch. Does not block PerplexityBot. |
Purposes for GPTBot, ChatGPT-User, OAI-SearchBot, Google-Extended, PerplexityBot, and Perplexity-User come from this site's AI crawler roster. Googlebot is Google's classic search crawler and is not on that roster. The Fix Report scoring table does not list Perplexity-User.
What about Googlebot versus Google-Extended, and PerplexityBot versus Perplexity-User?
Googlebot is Google's classic search crawler. Google-Extended is a separate token for Gemini and AI Overviews. A robots.txt rule that names one does not apply to the other.
Purpose is contested; robots.txt token is separate from Googlebot; Fix Report shows your rule.
Perplexity documents PerplexityBot as a search-index crawler for live results, not a foundation-model training crawl. Perplexity-User is a separate on-demand fetch agent. Each user-agent is its own robots.txt group.
What does a GPTBot-only block look like in practice?
Imagine a local service site that ranks in Google and wants to stay out of model training. The owner pastes a robots.txt snippet that names GPTBot, then Disallow: /. That snippet opts the site out of GPTBot. It does not mention ChatGPT-User or OAI-SearchBot. A visitor can still ask ChatGPT to open the homepage. ChatGPT-User is allowed, so the live fetch proceeds.
A different site copies a broader block. It adds three User-agent groups: GPTBot, ChatGPT-User, and OAI-SearchBot. Each group has Disallow: /. Those are three agents and three switches. GPTBot controls training. ChatGPT-User controls on-demand browse. OAI-SearchBot controls ChatGPT search indexing.
Neither site is a named customer. The user-agent string in robots.txt is the rule, not the brand name on the blog. Training consent and live citation fetch are separate switches.
Primary sources
Crawler names and purposes come from vendor documentation and this site's AI crawler roster. The Technical Access pillar is where the Fix Report checks robots.txt against the scoring roster.
Frequently asked questions
Does blocking ChatGPT-User block ChatGPT search?
No. ChatGPT search citations go through OAI-SearchBot. Blocking ChatGPT-User targets on-demand browsing, not the search-index crawler.
Does a robots.txt Disallow stop ChatGPT-User for sure?
Not for sure. OpenAI's bots documentation notes that robots.txt may not apply to ChatGPT-User, so a Disallow is not a guarantee that ChatGPT never fetches the page. It is also not the same as blocking ChatGPT search.
Does a free scan check these crawlers?
No. A free scan does not read robots.txt. It scores homepage pillars that actually run. The GPTBot, ChatGPT-User, and OAI-SearchBot table is in the paid Fix Report. The report reads robots.txt for the scoring roster and live-fetches a smaller set of user-agents. It does not fetch as GPTBot.
The crawler table is in the Fix Report
A free scan does not read robots.txt. The GPTBot, ChatGPT-User, and OAI-SearchBot table is in the $19 Fix Report.