← All posts
gptbot ai-crawlers geo robots-txt

How to tell if ChatGPT is reading your site

Your normal analytics can't answer this, by design. Here's why, and how to actually check whether AI crawlers are reading you.

u.
The usrPeek team · 3 min read

Before an AI assistant can recommend your site to someone, it has to read it. That reading is done by crawlers, and each assistant has its own:

Assistant Crawler
ChatGPT GPTBot
Claude ClaudeBot
Perplexity PerplexityBot
Google AI Google-Extended

So a useful question for any founder right now is simple. Are they reading me yet?

Your analytics dashboard can't tell you. Not because it's a bad dashboard. Because of how it's built.

Why your analytics is blind to crawlers

Tools like Google Analytics, Plausible, and Fathom work by running a small piece of JavaScript in the visitor's browser. When a real person loads your page, their browser runs that script, and the visit gets recorded.

Crawlers don't run JavaScript. GPTBot fetches your HTML and leaves. There's no browser, no script execution, nothing for a client-side analytics tool to hook into. So as far as your dashboard is concerned, the crawl never happened. This isn't a setting you can flip. Any analytics tool that lives entirely in the browser is structurally unable to see bots, full stop.

You're asking a question the tool was never able to see.

The two ways to actually check

The manual way

  • Grep your server access logs for GPTBot, ClaudeBot, PerplexityBot
  • Free, works today
  • A chore most people do exactly once
  • Can't tell you much beyond "something hit these URLs"
  • Probably counts impostors as real bots

The continuous way

  • Something watches server-side for you
  • Verifies crawlers against published IP ranges
  • Shows which bots read which pages, and when
  • Sits next to the rest of your traffic
  • "Did ClaudeBot crawl my new page" becomes a glance

The continuous way is what usrPeek does. It classifies the major AI crawlers, separates the genuine ones from spoofed user agents, and tells you which bots read which pages, and when.

While you're at it, check you're not blocking them

Here's the mistake I see constantly. Founders accidentally block AI crawlers in robots.txt, often inherited from a template or a plugin, and then wonder why no assistant ever cites them. A block like this tells ChatGPT's crawler to stay out, and people set it without realizing:

User-agent: GPTBot
Disallow: /

So two quick things to do today:

  • Open yoursite.com/robots.txt and check you're not disallowing GPTBot, ClaudeBot, PerplexityBot, or Google-Extended unless you mean to
  • Confirm the crawlers are actually coming through

That second half is the one your current tools can't do. usrPeek shows you AI crawler activity server-side, verified and sitting right next to your real visitor traffic, so you can finally answer the question every founder is starting to ask: does AI know I exist yet?

See what your visitors actually do

usrPeek is dead-simple analytics for solo founders. One script tag for visitor journeys, auto-tracked clicks, AI traffic, and a daily email. No bolt-on cookie tooling.

Start for free

Keep reading