ChatGPT-User

ChatGPT-User appears in your logs when a real person, mid-conversation, causes ChatGPT to open your page: pasting your URL, asking for a summary of your pricing, or requesting up-to-date details the model retrieves via browsing. Unlike GPTBot or OAI-SearchBot, it does not crawl proactively or build an index. Each hit maps to genuine human intent, which makes ChatGPT-User traffic one of the most commercially meaningful bot signals a site can receive.

A spike in ChatGPT-User fetches on a product or comparison page means users are actively discussing it inside ChatGPT, even if no click-through ever lands in your analytics. This is the invisible middle of the AI search funnel: research that happens entirely inside the chat interface. Blocking ChatGPT-User in robots.txt is self-defeating for almost everyone, because you are refusing a page view that a human explicitly requested; ChatGPT will simply tell the user it could not access your site, often pushing them to a competitor's page instead.

Because these fetches execute no JavaScript, they are invisible to client-side analytics and only show up in server logs or edge-level tracking. Logging them per page reveals which content ChatGPT users actually pull into conversations, a different and often earlier signal than AI referral traffic. Geonimo's Cloudflare Worker integration records ChatGPT-User hits alongside other bot activity through its AI traffic analytics, letting you correlate in-conversation fetches with subsequent referral visits and citations.