AI crawler · registry

ChatGPT-User

OpenAI · Live retrieval · robots.txt token chatgpt-user

honors robots.txtMeasured across 3,958 sites with a robots.txt policy record for this agent, out of 7,068 on record.
6%
of measured sites block it
235
sites blocking
3,723
sites allowing
yes
honors robots.txt

What it is definition

Fetches a page when a ChatGPT user or GPT Action asks for it; user-initiated, so robots rules may not apply.

ChatGPT-User is operated by OpenAI and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.

Disallowing chatgpt-user stops the fetch that happens when a user asks ChatGPT browsing about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

robots.txt token
chatgpt-user
Operator
OpenAI
Purpose
Live retrieval
Honors robots.txt
yes
Documentation
https://platform.openai.com/docs/bots

Identity on the wire exact string

User-agent string
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot
Verify your own edge is not refusing it
curl -A 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

How to allow it, how to block it robots.txt

Allow it
User-agent: chatgpt-user
Allow: /

Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.

Block it
User-agent: chatgpt-user
Disallow: /

Disallowing chatgpt-user stops the fetch that happens when a user asks ChatGPT browsing about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

Sites that block it 60 shown

DomainAI access scoreRank
amazon.com 33 26
tiktok.com 41 54
yahoo.com 52 58
msn.com 34 62
amazonvideo.com 55 121
nytimes.com 67 157
cnn.com 50 190
bbc.com 69 207
bbc.co.uk 70 226
nature.com 56 281
amazon.co.uk 33 318
bloomberg.com 53 358
amazon.de 33 377
espn.com 44 432
claude.ai 46 435
cnbc.com 59 457
quora.com 41 479
amazon.co.jp 33 494
aol.com 54 499
usatoday.com 55 552
alrosa.ru 62 556
telegraph.co.uk 45 580
amazon.fr 33 609
amazon.co.za 33 623
dailymail.co.uk 63 627
techcrunch.com 79 629
amazon.ca 33 635
cambridge.org 48 650
amazon.in 34 659
cnet.com 75 662
dailymail.com 63 681
primevideo.com 55 682
amazon.it 33 706
amazon.es 33 725
mercadolivre.com.br 72 740
amazon.com.au 33 812
theverge.com 68 815
nbcnews.com 63 823
amazon.com.br 33 833
lefigaro.fr 74 834
genius.com 60 926
mercadolibre.com.ar 72 931
webmd.com 66 932
elmundo.es 86 983
theconversation.com 52 1,019
huffpost.com 82 1,027
amazon.com.mx 33 1,032
spiegel.de 72 1,042
archiveofourown.org 60 1,051
marca.com 85 1,056
bfmtv.com 71 1,073
franceinfo.fr 66 1,098
cookpad.com 63 1,105
gsmarena.com 65 1,114
mercadolibre.com.mx 72 1,125
economist.com 43 1,157
mercadolibre.com 47 1,165
pimpbunny.com 56 1,177
ad.nl 47 1,190
nu.nl 47 1,191

Compare OpenAI

OpenAI runs 4 agents in this registry, and they do different jobs. Blocking one says nothing about the others.

Common questions answered

Does blocking ChatGPT-User remove me from ChatGPT browsing?

Partly. ChatGPT-User fetches a page only when a user asks about it, so disallowing it does not delist you from ChatGPT browsing. It does mean the answer is composed without your live page, from a stale copy or a third-party summary.

How do I verify ChatGPT-User requests are genuine?

OpenAI publishes the address ranges its crawlers fetch from as JSON files linked from its bot documentation, one file per agent. Compare the source address of the request against the file for that agent. There is no reverse DNS name to check, so the address list is the only signal.

Check your own site free

See whether your robots.txt admits ChatGPT-User today, and whether your edge agrees with it.