AI traffic analytics

See which AI agents actually visit your site.

A scan tells you whether an agent could read your site. This tells you whether one actually came — which pages it fetched, and which ones turned it away. Your Google Analytics can’t see any of it.

One snippet, no SDK. Data starts appearing within minutes.

AI traffic · last 7 daysExample
AgentIntentRequestsStatus
ChatGPT-UserAnswering a user1,204200
ClaudeBotAI search index860200
PerplexityBotAnswering a user412403
GPTBotTraining data389200
Google-ExtendedTraining data77403
Why your analytics can’t see agents

Analytics scripts run in the browser. AI crawlers don’t run JavaScript — they fetch your HTML and leave — so an agent never triggers the script, and never shows up in Google Analytics, Plausible, or anything else client-side. The only place an agent is visible is your server logs. This reads it from there: a fire-and-forget line in your server records the request the moment it lands, classifies the agent, and rolls it up. One HTTP POST, no SDK, and it swallows its own errors so it can never slow a page down.

What you get

Three questions, answered every day

Every agent that arrived

ChatGPT, Claude, Perplexity, Google and the rest — named, counted, and ranked by how many requests each one made this week, with the week-over-week trend.

What they actually fetched

The pages agents requested most, so you can see which parts of your site are being read into answers — and which never get touched.

Where they were turned away

Every 4xx and 5xx an agent hit, broken out by path. A blocked agent is a page that can never be cited — this is the number that quietly costs you answers.

Not all agent traffic is equal

We tell you why each one came

Answering a user

Fetching your page to answer someone right now. This is the traffic that converts — a real person is on the other end of it.

AI search index

Indexing you for AI search results. Shows up in answers later, the way an SEO crawler feeds a search engine.

Training data

Collecting training data. No near-term traffic value, so blocking it is a licensing choice rather than a visibility one.

A page an “answering” agent can’t reach is an answer you’ll never appear in.

Half your traffic is agents now. Start counting it.

Traffic ingest is included on every paid plan and shares your monthly event quota — no separate meter, no extra line item.

Start free →See plans

Not sure yet? Run the free readiness scan — it’s the same product from the other side.