ChatGPT-User: What It Is, User Agent & Should You Block It?

What is ChatGPT-User?

Traffic from ChatGPT-User is bursty and query-driven: single-page fetches at the moment a user asks, rather than systematic site-wide crawling. Volume scales with how often your pages are referenced in conversations.

Because each fetch stands in for a human reader, many publishers treat ChatGPT-User traffic as audience rather than scraping — the open question is that these readers never see your pages, your ads, or your subscription prompts.

How to identify ChatGPT-User

ChatGPT-User identifies itself with the following user-agent string:

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot

Never trust the user-agent string alone. Scrapers routinely impersonate well-known crawlers to inherit their access. OpenAI publishes IP ranges for ChatGPT-User; verify source IPs against the published JSON rather than trusting the user-agent header.

Published IP ranges: https://openai.com/chatgpt-user.json

Note that most AI crawlers and fetchers, ChatGPT-User included, do not execute JavaScript — so this traffic is invisible to GA4 and every script-based analytics tool. Server logs, CDN analytics, or a dedicated bot-analytics layer are the only places you will see it. For the full picture of measuring AI-driven visits, see our guide on how to track AI traffic.

Controlling ChatGPT-User with robots.txt

To refuse ChatGPT-User access to your entire site, add this to your robots.txt:

User-agent: ChatGPT-User
Disallow: /

To restrict it from specific sections only (for example, premium content) while leaving the rest open:

User-agent: ChatGPT-User
Disallow: /premium/
Disallow: /members/

Should you block or monetize ChatGPT-User?

The case for blocking: Blocking ChatGPT-User stops ChatGPT from reading your pages even when a user explicitly pastes your URL. That protects paywalled content from being summarized on demand, which is a real leak for subscription publishers.

The case for allowing or monetizing: These fetches are exactly the 'agent visit on behalf of a human' that per-fetch licensing and sponsored inclusion are designed for. A human is consuming your content — the monetizable event exists, it just happens inside ChatGPT instead of on your page.

Bottom line

Allow it unless you run a hard paywall. On-demand fetches represent real readers, and cutting them off makes your brand silently absent from conversations where you were explicitly requested. Publishers with subscription content should either block it or move to licensed access.

Where Oasy fits

See exactly what ChatGPT-User does on your site — then decide what that access is worth.

Oasy detects and fingerprints 50+ AI crawlers with per-URL analytics, blocks the ones you exclude at the edge, and turns the rest into revenue — licensed RAG access and sponsored placement inside AI answers, settled weekly. Analytics scripts can't see this traffic; your server logs can, and so can we.

Join the waitlist

Frequently asked questions

Is ChatGPT-User the same as GPTBot?+

No. GPTBot crawls in bulk to collect training data on its own schedule. ChatGPT-User fetches one page at a time, only when a human's ChatGPT session needs it, and the content is not used for training.

Why do I see ChatGPT-User hits on pages that aren't in any index?+

Because users paste URLs directly into ChatGPT. Any page a user references can be fetched, whether or not search engines or OAI-SearchBot know about it.

Does ChatGPT-User show up in Google Analytics?+

No. It fetches server-side and doesn't execute your analytics JavaScript, so these visits are invisible in GA4 and only appear in server or CDN logs — one reason publishers underestimate their AI readership.

Stay informed on life in Europe as an expat. The Local delivers daily news, guides and essential info across 9 European countries. Sign up for the free newsletter at thelocal.com/free-newsletter