Does blocking GPTBot block ChatGPT?
GPTBot, ChatGPT-User, and OAI-SearchBot are three different robots.txt tokens.
Last reviewed: September 13, 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 sets a training preference. OAI-SearchBot is the separate search control. ChatGPT-User supports user actions, so robots.txt may not apply; a firewall can still prevent a fetch.
OAI-SearchBot controls eligibility for ChatGPT search answers, with possible navigational links even for opted-out sites. Access does not guarantee selection. The Technical Access pillar records crawler rules; a named rule is not proof that a user-initiated fetch obeyed it.
| 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 | Robots.txt may not apply to user-initiated visits. Does not control ChatGPT search. |
| OAI-SearchBot | OpenAI | retrieval | Blocks ChatGPT search indexing. Does not block GPTBot or ChatGPT-User. |
| Googlebot | classic search | Controls Google Search crawling, including AI Overviews and AI Mode. Does not apply to Google-Extended. | |
| Google-Extended | retrieval | Does not block Googlebot or control Google Search inclusion. Controls Gemini training and grounding uses. | |
| PerplexityBot | Perplexity | retrieval | Blocks Perplexity's search-index crawler. Does not block Perplexity-User. |
| Perplexity-User | Perplexity | retrieval | User-requested visits generally ignore robots.txt. Does not block PerplexityBot. |
The table distinguishes automatic search crawls, training preferences, and user-requested visits. Read the vendor documentation below for the current controls. Google-Extended is a product token, not a separate HTTP user-agent.
What about Googlebot versus Google-Extended, and PerplexityBot versus Perplexity-User?
Googlebot controls crawling for Google Search, including AI Overviews and AI Mode. Google-Extended controls separate Gemini training and grounding uses; it has no effect on Google Search inclusion or ranking.
Google-Extended controls Gemini training and grounding uses. Googlebot controls Google Search, including AI Overviews and AI Mode; Google-Extended does not affect Google Search inclusion or ranking.
PerplexityBot supports search discovery and respects its crawler policy. Perplexity-User supports user-requested visits and generally ignores robots.txt. Verify genuine IP traffic and network controls when a fetch fails.
What does a GPTBot-only block look like in practice?
Imagine a local service site that wants to decline model training while allowing search discovery. A GPTBot group with Disallow: / expresses that training preference. An OAI-SearchBot group can separately allow public pages. Preserve private-path exclusions when adding a specific group.
A second site disallows OAI-SearchBot too. That opts out of ChatGPT search answers, except possible navigational links. Adding ChatGPT-User to robots.txt does not guarantee that user-requested browsing stops; inspect network controls and authenticated access instead.
These are fictional examples. Check the final robots.txt and genuine request logs after a policy change. A curl request using a vendor user-agent name is not proof that requests from the vendor’s IP ranges succeed.
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. OAI-SearchBot controls ChatGPT search eligibility. ChatGPT-User supports user actions, and robots.txt may not apply to those visits.
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.