OpenAI · User-triggered fetch
ChatGPT-User
- Operator
- OpenAI
- Purpose
- User-triggered fetch
- Verification
- Published IP ranges
- Follows robots.txt
- Operator says it may ignore robots.txt
01Identify and verify
How it shows up in your logs
User-agent contains
ChatGPT-User
Matching is case-insensitive. Anyone can send this string, so a match alone says only what the request claims to be.
Is it really ChatGPT-User?
Plumb checks the request IP against the operator's published ranges.
Range checked: openai:chatgpt-user
Signing keys: openai.com
02Publishers
How major publishers treat it
38%of 319 publishers on the leaderboard block
ChatGPT-User outright (121). 140 more close some sections. 140 name it explicitly in their robots.txt.03robots.txt
A rule you can paste
The group names ChatGPT-User exactly. A group for a different token from the same company does not cover it.
OpenAI says robots.txt rules may not apply to fetches a user starts in ChatGPT. A rule here records your preference; enforcing it takes a block at your CDN or firewall.
# ChatGPT-User (OpenAI) User-agent: ChatGPT-User Disallow: /
04Same operator
OpenAI's other agents
- GPTBotModel training
- OAI-SearchBotAI search indexing