AI agents are reading your site. You can't see a single one.

31% of B2B content-page traffic is already AI agents, not humans. 0% of it shows in your legacy analytics. Agent Analytics reads it at the edge: which models, which pages, which questions, and what converts.

Agent Analytics dashboard showing total LLM visits, traffic by AI model (ChatGPT, Perplexity, Claude), and a live clickstream of AI agents reading the site in real time
Integrations

Works with your stack.

Agent Analytics reads traffic at your CDN or edge, behind whatever you already run. No tag manager, no JavaScript, no code changes.

CloudflareCloudflare
WordPressWordPress
VercelVercel
AWS CloudFrontCloudFront
NetlifyNetlify
NginxNginx

CDN-level integration. No code changes required.

The blind spot

Your analytics stack was built for human clicks. Your buyers stopped clicking.

A buyer now asks ChatGPT before they ask you. The agent reads your site, forms an opinion, and the human shows up already decided. Every tool you own is counting the humans. None of them is counting the agent that briefed them.

What legacy analytics sees
A gap.
Most AI agents run server-side and never execute JavaScript. 59% of ChatGPT agent traffic uses raw HTTP clients. Your tag-based analytics never fires, so the visit simply isn't there.
Counting humans, blind to agents
What Agent Analytics sees
All of it.
We read traffic at the edge, before the page renders. Every fetch, every page, every question, every citation, by model, in real time. No tag manager, no JS bundle, nothing for an agent to skip.
The traffic your stack throws away
From signal to action

Seeing every agent is step one. Here's what you do with it.

The visibility is the easy part. The value is in the moves it unlocks: sharper content, fewer stale answers, and a roadmap built from what AI buyers actually read.

Double down on what resonates

See which pages agents read and cite most. That's hard proof of what AI buyers find useful. Make more of it, and lift the rest of your library to the same bar.

You'd see42 agents cited /guides/llm-seo this week

Catch stale answers before they cost a deal

An agent pulls a two-year-old post with old pricing or packaging, and you catch it. Update the page so the answer a buyer gets is the current you, not a version from 2024.

You'd seeClaudeBot → /blog/pricing · last edited 2024

Write the pages agents keep asking for

Every question an agent asks that your site can't answer logs as a miss. That's your content roadmap, ranked by how often buyers actually ask.

You'd seeGPTBot asked "SOC 2 report?" → no match

Optimize for the model about to buy

Some models browse, some are ready to buy. When a high-intent model is reading you, make your pricing and comparison pages airtight. That's where the decision gets made.

You'd seeClaude · 5× more pricing-page clicks

Win the comparison while it's happening

Agents pulling your "vs competitor" pages means the shortlist is being written in real time. Sharpen those pages so you're the one that gets recommended.

You'd seePerplexityBot → /vs-competitor · 3× today

Put a number on the AI channel

Tie agent reads to the conversions they pre-educated. Report a channel that's invisible to legacy analytics, and justify the next investment with data.

You'd seeChatGPT-referred visitors convert 4.4×
The new traffic, in numbers

This is not a forecast. It is already in your logs.

31%

Of B2B content-page traffic is agents

Across the monitored network, nearly a third of traffic to B2B content pages now comes from AI agents instead of people. The share grows every month.

4.4×

Conversion vs. organic

An AI-referred visitor arrives pre-educated and converts at 4.4× the rate of a generic organic visitor. They are your best traffic, and the channel you can't currently report on.

Source · Salespeak internal research
0%

Show in legacy analytics

Server-side agents leave no client-side footprint. Your entire AI-research funnel is invisible to every analytics tool you pay for. Until you read it at the edge.

Who is actually crawling you

Not "AI traffic." Four very different visitors.

Each model reads your site differently and buys differently. Agent Analytics splits them apart so you can see who is browsing, who is comparing, and who is about to convert. A blended "bot traffic" number hides all of it.

ChatGPT
The volume
The firehose. It reads everything, broadly. +91% URL coverage in 2 months. If a page exists, GPTBot has probably seen it.
Claude
The buyer
Lower volume, far higher intent. Claude clicks pricing 5× more often, and its traffic grew 26× in five months. The doubling time is now ~20 days.
Perplexity
The closer
Sends real people. Only 1% of Perplexity visits touch your homepage: it goes straight to the deep page that answers the question, then hands off the click.
Gemini & others
The field
Gemini, Bing, and a growing field. New crawlers appear on the network monthly. Agent Analytics fingerprints each one the day it shows up.
How it works

It reads at the edge. Your engineers won't care.

No tag manager, no JS bundle, no sampling. Deploy at your CDN, behind your existing edge. Humans get your site, unchanged. Agents get counted, the moment they arrive.

01CAPTURE

Every request, at the edge.

Before a page renders, Agent Analytics logs the request server-side. Nothing for an agent to skip, no JavaScript required. The 59% of traffic legacy analytics misses, you keep.

02IDENTIFY

Which agent, which page, which question.

We fingerprint the model (GPTBot, ClaudeBot, PerplexityBot, Gemini, more), the exact path it read, and the buyer question behind the visit. 412 questions get asked of your content in a typical minute.

03ATTRIBUTE

From crawl to conversion.

We connect the agent read to the human session it pre-educated, and to the deal it influenced. The 4.4× conversion channel finally has a number next to it.

04SURFACE

Gaps you can fix.

When an agent asks something your site can't answer, you see it. 31 of every 412 questions hit a wall. Those are the pages costing you the shortlist, ranked by how often agents want them.

The growth curve
26× in 5 months
Claude agent traffic, Nov to May.
~20-day doubling
And accelerating.
The default funnel
Measured, or not.
See it on your own traffic

Run the read on your domain. See what's already happening.

Point us at your site. In one report you'll see which agents are reading you right now, which pages they pull, what they ask, and what your current stack is throwing away. Your traffic. No code change. No commitment.

10m
We read your edge logs
A first agent-traffic snapshot of your domain, in minutes.
14d
It runs live on your traffic
Counting, splitting by model, attributing to conversion. No tag manager.
You see the funnel you were missing
Your agents, your pages, your gaps, your conversions. You decide what comes next.

Legacy analytics shows you yesterday's humans. Agent Analytics shows you today's buyers.

The research happens before the click, in a channel your tools can't see. Read it while it's happening, or keep reporting on the wrong funnel.

See your agent traffic, free