ChatGPT-User

AI assistant (user-triggered)

A live ChatGPT user's assistant, fetching your page mid-conversation.

What ChatGPT-User does

ChatGPT-User fires when a real person asks ChatGPT about a URL or a topic that leads it to your site — the assistant fetches the page on their behalf, right then. Every one of these visits is a human evaluating you through an AI intermediary; think of it as a warm lead's research assistant.

Fact sheet

Operator: OpenAI
robots.txt token: ChatGPT-User
Honors robots.txt: Yes (documented)
Executes JavaScript: No — invisible to browser analytics
Identity verifiable by IP: Yes — vendor publishes IP ranges (we verify every visit)
Official documentation: OpenAI docs ↗

How it identifies itself

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

User-agent strings are free to fake — any scraper can claim to be ChatGPT-User. That's why VisitorType checks every claimed ChatGPT-User visit against OpenAI's published IP ranges and downgrades impostors to plain bots.

Allow or block via robots.txt

# Block ChatGPT-User
User-agent: ChatGPT-User
Disallow: /

# Or allow it explicitly
User-agent: ChatGPT-User
Allow: /

Should you block ChatGPT-User?

Blocking ChatGPT-User turns away a live buyer's assistant at the door — they asked about you, and got an error. Almost never worth it. Better: measure which pages assistants read, and make sure pricing and key facts are crawlable HTML.

Is ChatGPT-User reading your site?

ChatGPT-Usernever runs JavaScript, so GA4 can't see it. VisitorType's server-side detection can — with per-page counts and IP-verified identity.

Measure it free