How to Block ChatGPT-User: Stop ChatGPT Real-Time Browsing on Your Site
ChatGPT-User isn't a crawler — it's triggered only when a ChatGPT user explicitly asks it to read a URL. Blocking it stops on-demand page reads. It has zero effect on training data or ChatGPT Search.
Updated March 2026
ChatGPT-User ≠ GPTBot ≠ OAI-SearchBot
OpenAI operates three distinct agents. Most people conflate them. They have completely different purposes and blocking one has zero effect on the others.
GPTBotAutonomous training crawler. Crawls the web to collect data for future GPT models.OAI-SearchBotSearch index crawler. Builds and maintains ChatGPT Search (SearchGPT) results.ChatGPT-UserOn-demand browsing agent. Fetches a specific URL only when a ChatGPT user explicitly requests it.What Does ChatGPT-User Actually Do?
When a ChatGPT subscriber types something like "summarize this article for me" and pastes a URL, ChatGPT sends a live HTTP request to that URL using the ChatGPT-User user agent. It reads the page, processes the content, and returns a summary to the user.
This is fundamentally different from a crawler. It doesn't systematically index your site. It doesn't follow links. It fetches exactly the URL the user provided — once, on demand. Volume is typically low unless your content gets widely shared in ChatGPT conversations.
The user agent string is: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); ChatGPT-User/1.0; +https://openai.com/bot
How to Block ChatGPT-User in robots.txt
Add this to your robots.txt to block ChatGPT from reading any page on your site on-demand:
User-agent: ChatGPT-User Disallow: /
To block all three OpenAI agents at once (training + search + browsing):
User-agent: GPTBot Disallow: / User-agent: ChatGPT-User Disallow: / User-agent: OAI-SearchBot Disallow: /
Note: Each agent needs its own block
You cannot group them under a single User-agent: directive. Each must be listed separately. Blocking GPTBot does not block ChatGPT-User or OAI-SearchBot.
Who Actually Needs to Block ChatGPT-User?
For most public websites, blocking ChatGPT-User is low priority. It only fires when a user explicitly submits your URL — not on autonomous crawls. But there are specific cases where it matters:
What Blocking ChatGPT-User Does (and Doesn't) Do
- • ChatGPT fetching your pages when users submit URLs
- • ChatGPT summarizing your paywalled content via on-demand reads
- • Real-time page reads triggered by ChatGPT Plus/Pro users
- • GPTBot training crawls (block GPTBot separately)
- • OAI-SearchBot search indexing (block separately)
- • ChatGPT's existing knowledge of your content
- • Users copy-pasting your content into ChatGPT manually
Verify Your Block Is Working
After deploying your robots.txt changes, test them at Open Shadow's robots.txt checker. Enter your domain and verify ChatGPT-User shows as blocked.
You can also check your server logs. ChatGPT-User requests will appear with the user agent string containing ChatGPT-User/1.0. After blocking, you should see 403 or no requests from that agent (depending on how your server handles disallowed bots).
nginx log grep
grep "ChatGPT-User" /var/log/nginx/access.log
Frequently Asked Questions
If I block ChatGPT-User, will ChatGPT tell users it can't access my site?
Yes. When ChatGPT-User encounters a Disallow in robots.txt, ChatGPT informs the user that it cannot access the content at that URL. The user will see a message like "I'm unable to access this page" — rather than silently failing.
Does blocking ChatGPT-User affect my site's ranking in ChatGPT Search?
No. ChatGPT Search uses OAI-SearchBot, a separate crawler. Blocking ChatGPT-User has zero effect on whether your content appears in ChatGPT Search results.
Can I block ChatGPT-User for specific paths only?
Yes. Instead of Disallow: / you can target specific paths: Disallow: /members/ or Disallow: /premium/ — this lets public pages remain accessible while protecting gated content.
Is there a way to block ChatGPT-User at the server level instead of robots.txt?
Yes — you can match the user agent in nginx or Cloudflare and return a 403. But robots.txt is sufficient since OpenAI respects it. Server-level blocking is only worth adding if you want to also prevent the request from hitting your origin at all (reducing load).
Related Guides
Is your site protected from AI bots?
Run a free scan to check your robots.txt, meta tags, and overall AI readiness score.