ChatGPT-User

ChatGPT-User fetches a page live when someone asks the AI platform about it. Most operators use a separate user agent for each job, so you can usually allow or block one without affecting the others.

Page fetches requested by AI platform users. A verified request establishes a page read, not a citation or a human visit.

This is a full user agent string ChatGPT-User sends. Version numbers change over time; match the ChatGPT-User token rather than the whole string.

To block ChatGPT-User, add this to the robots.txt at the root of your site:

Blocking it stops the assistant reading your page when a user asks for it, so the answer is built from other sources. Operators can treat user-requested fetches differently from automatic crawling; check the operator's documentation for how it applies robots.txt.

To allow it explicitly, for example after a broader rule blocks other crawlers:

Check what your robots.txt allows for ChatGPT-User and the other AI crawlers in this directory.

OpenAI publishes the IP addresses ChatGPT-User uses. A request that claims to be ChatGPT-User from any other address is not genuine.

• openai.com/chatgpt-user.json

SurfacedBy's AI traffic tracking recognizes ChatGPT-User in the user agent and checks each request against OpenAI's published addresses. Only requests that pass count as crawls; the rest are shown separately.

Details on this page come from OpenAI's own documentation: developers.openai.com/api/docs/bots.

• GPTBotTraining
• OAI-SearchBotSearch indexing