AI crawlers don't run JavaScript, so they never load an analytics tag. In GA4, a day when GPTBot reads forty of your pages looks the same as a day when nothing happened at all.
Every crawler request is a real HTTP hit your server writes down. Reading it means parsing raw logs across a dozen crawlers, each with its own IP ranges that change without notice. That's the tedious part we handle.
Nothing on the dashboard is modeled or estimated. Each hit is a request your server received, matched to the IP ranges the crawler's operator publishes. Pull your own logs and check any of it.
Each GPTBot, ClaudeBot, and PerplexityBot request that reaches your server, attributed to the crawler behind it, straight from your server-side logs.
Anyone can put "GPTBot" in a request header. We check the IP against OpenAI's published ranges, so a scraper hiding behind the name doesn't get counted as the real thing — and you see it flagged.
Did GPTBot fetch your pricing page, or just your homepage? See exactly which of your key pages each AI crawler has — and hasn't — reached.
If a crawler never reads the page, no model can cite it. Coverage is the first thing worth fixing, well before you start worrying about how you rank inside the answer.
One screen: how many AI crawlers hit you, how many were the real thing, which of your pages they reached, and what to change. Below is a week of logs from a demo site.
Each request is matched to the IP ranges the crawler's operator publishes. Here, 1,430 checked out and 11 carried a crawler's name from an address that wasn't theirs.
Key-page coverage shows what each crawler fetched and what it skipped. A page no crawler reads is a page no model can cite.
The evidence turns into specific actions: block the scraper at your edge, open up a page answer engines are missing, or decide what training crawlers get to keep.
We're in private beta with a first group of sites and agencies, and we set pricing up with each of them. Book a demo and we'll get your logs flowing in.
We're onboarding founding customers by hand — tell us your email (and your site, if you've got it) and we'll reach out when there's room.
Create an account, point a Cloudflare Worker (or an access log) at your site, and you'll see the verified crawler hits, anything spoofing its way in, and which of your key pages GPTBot, ClaudeBot, and PerplexityBot have actually reached.
Get started