On demand · OpenAI
ChatGPT-User
Fetches a page when a ChatGPT user asks about it or a GPT action calls it. Not used for training and not an automatic crawl. Blocking it means ChatGPT cannot read your page when a user shares the link.
- Operator
- OpenAI
- Purpose
- User-triggered fetchers
- Feeds
- ChatGPT (live browse)
- robots.txt token
ChatGPT-User- Honours robots.txt
- Honours robots.txt
- Documentation
- platform.openai.com
What it looks like in server logs
A representative user-agent string. Version numbers change; the ChatGPT-User token does not. Paste your own log line into the user-agent checker to confirm a match.
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/botHow to block ChatGPT-User
Add this to the robots.txt at the root of your domain. Robots.txt is advisory: it works only on crawlers that choose to read it. This one is honours robots.txt according to its operator.
User-agent: ChatGPT-User
Disallow: /
To block every user-triggered fetcher at once, or to block training while keeping AI search citations, use the robots.txt generator.
How to allow ChatGPT-User while blocking others
A more specific User-agent group wins over a wildcard. Place this above any User-agent: * block that disallows paths, and ChatGPT-User keeps full access.
User-agent: ChatGPT-User
Allow: /
How to verify a genuine hit
The user-agent string is self-asserted: anyone can send it from a laptop, and scrapers routinely impersonate well-known crawlers to slip past filters aimed at unknown ones.
OpenAI publishes its IP ranges as JSON; a hit from outside them is spoofed.