AI agent traffic: how to measure the visits your analytics can't see.
Automated requests passed human ones on Cloudflare's network this year, and many AI agents look like ordinary Chrome. Here is how to find agent visits in logs, your CDN and GA4, and what to report.
AI agent traffic is the share of your website's visits made by AI systems acting for a person: fetching a page to answer a question, comparing your prices, or filling in your form. It is growing fast, and most analytics setups barely see it.
How much web traffic is AI agents?
On 3 June 2026 Cloudflare's CEO said automated requests had passed human ones for the first time. Cloudflare Radar put automated requests at 57.5% of HTML web traffic, against 42.5% from humans. That figure includes search crawlers, scrapers and monitoring, not only AI agents, so read it as "bots are now the majority", not "agents are".
Agent-specific numbers are less certain. The HUMAN Security 2026 report, as cited by WorkOS, measured agentic AI traffic growing by roughly 7,851% year over year. Growth from a small base, but a clear direction.
The three kinds of AI traffic
| Kind | Examples | How it shows up |
|---|---|---|
| Training crawlers | GPTBot, ClaudeBot, CCBot | Named user agent, bulk crawling, no visitor behind it |
| User-triggered fetchers | ChatGPT-User, Claude-User, Perplexity-User, Google-Agent | Named user agent, one fetch when a person asks a question or gives a task |
| Browser agents | Chrome auto browse, Claude in Chrome, Perplexity Comet, ChatGPT agent | Often an ordinary Chrome user agent; sometimes a signature header such as Signature-Agent |
The middle row is the easiest win: each request is a real person's question or task reaching your site. The last row is the hardest, because the request looks like a person in a browser. ChatGPT agent, for example, has been observed browsing with a normal Chrome user agent plus a Signature-Agent: "https://chatgpt.com" header.
How to measure AI agent traffic
- Start with server or CDN logs. Agents that fetch HTML without running your analytics script never reach GA4. Export a week of access logs and paste them into our AI agent log analyzer, which groups requests by known AI user agents.
- Log signature headers. Add
Signature-AgentandSignature-Inputto your log format, so signed agents show up even when the user agent says Chrome. - Use your CDN's bot categories. Cloudflare and other CDNs label verified bots and signed agents separately. Their dashboards are often the quickest view.
- Separate AI referrals in GA4. People who click a link in ChatGPT or Perplexity are humans, not agents, but they came via AI. Group them with our GA4 AI traffic regex.
- Test task success yourself. Logs show visits, not outcomes. Once a month, run your three money tasks through an agent and record pass or fail.
Which pages agents visit tells you what they want
Group agent requests by page type. Fetches of pricing, comparison and documentation pages usually mean someone asked an assistant to evaluate you. Requests to checkout or booking that never complete point to a step an agent cannot finish. That second list is your fix list.
What to report each month
- Agent requests by agent family (OpenAI, Anthropic, Perplexity, Google and others), with the trend.
- Agent requests to money pages: pricing, booking, sign-up and checkout.
- AI referral sessions and conversions in GA4.
- Task success rate from your own monthly agent tests.
Engagement metrics built for people, like bounce rate and time on page, mislead with agents. An agent that reads your price in two seconds and leaves has done its job.
Questions people ask
What is AI agent traffic?
Requests to your website made by AI systems acting for a person, such as an assistant fetching your page to answer a question or a browser agent filling in your form. It is different from training crawlers, which collect content in bulk.
How much web traffic comes from AI agents?
Cloudflare Radar showed automated requests at 57.5% of HTML web traffic in June 2026, but that includes all bots. There is no reliable public figure for AI agents alone; measure your own share from server logs.
Does GA4 track AI agent traffic?
Mostly not. Many agents fetch pages without running JavaScript, so GA4 never sees them. GA4 does see people who click through from AI assistants, which you can group into their own channel.
Should I block AI agent traffic?
Usually not on pricing, booking and checkout pages, because user-triggered agents are working for potential customers. Block or limit training crawlers separately if you want to, with robots.txt.
Want this mapped onto your product?
See how our AAO work runs, or send your store link and a founder will reply personally.
