CrawlPactChatGPT-User
- User-agent token
- ChatGPT-User
- Purpose
- User-triggered
- Status
- active
- Last verified
- 2026-07-24
OpenAI documents ChatGPT-User as the crawler used “when users ask ChatGPT or a CustomGPT a
question” and it “may visit a web page” to help answer it, including when a Custom GPT takes an
action against an external site through GPT Actions.
Why this is different from GPTBot
ChatGPT-User requests are triggered by a specific person’s question, not a bulk crawl. It is
tracked separately in CrawlPact’s registry from the training-purpose GPTBot and the
search-purpose OAI-SearchBot — a website can restrict one without restricting the others.
Site-owner controls
Standard robots.txt disallow rules apply. See /limitations for what a
robots.txt rule can and cannot guarantee.
Note on this page’s source
OpenAI’s crawler documentation moved from platform.openai.com/docs/bots to
developers.openai.com/api/docs/bots since this record was first added — the citation above
reflects the current location as of the last-verified date.
Example robots.txt configuration
To disallow ChatGPT-User specifically, without affecting any other crawler:
User-agent: ChatGPT-User
Disallow: /If no dedicated User-agent: ChatGPT-User group exists in a domain's robots.txt, this crawler falls back to whatever the wildcard User-agent: * group says (RFC 9309) — see robots.txt syntax basics for how group selection works.
Verified against the source above as of 2026-07-24 — see how CrawlPact verifies crawler information.
Related crawlers
See how this applies to your own site
Run a free audit to check your declared AI crawler policy against your own domain, or use the AI crawler checker to check this one crawler specifically.
Audit a domain