New at ContentCon: meet Contentstack Canoe. See what AI says about your brand.
Contentstack Canoe
Log in Start free
Start free Menu
Enterprise

Agent traffic

See which AI agents read your site, check they are who they say they are and serve them pages they can read. People see your site exactly as before.

Enterprise feature

Agent traffic is part of the Enterprise plan. To turn it on for your workspace, talk to us.

What you get

  • Who reads your site. Every AI agent that visits, and whether it is who it says it is.
  • Agent demand. The prompts where AI agents read your pages but leave your brand out of the answer. Start at the top.
  • Agent-ready pages. A clean markdown or fully rendered copy of a page for AI agents, with the same content. People and Googlebot always get your normal page.
  • People and agents. With Lytics connected, what AI tells the audiences that matter to you.

Set it up

  1. Connect your site. Open your brand's settings and select Integrations. Pick one: Cloudflare installs a Worker on your zone with an API token you create in Cloudflare. Custom edge is a small snippet for any CDN, edge function or Node server.

  2. Add Lytics (optional). Connect Lytics to bring your audiences in as personas.

  3. Turn on agent-ready pages. Start in Shadow, check the results, then switch to On. See Agent-ready pages.

Settings, Integrations: Connect your site with Cloudflare or Custom edge, and Audience data with Lytics, each with a Setup guide link and Connect.
Settings > Integrations before anything is connected.

Owners and admins connect, change and disconnect integrations. Everyone in the workspace can see the results.

Read the Agent Traffic tab

Open a monitor and select Agent Traffic under Diagnose. Pick 24 h, 7 days or 30 days.

The Agent traffic header with the 24 h, 7 days and 30 days switch, the views Overview, Agents, Pages, Agent-ready pages and Audience, and tiles for AI answers, agent visits, verified share, pages read and AI referrals.
The top of the tab for a fictional brand.
Overview
The numbers that matter, live activity, where agents came from and the prompts to fix first, each linked to its recommendations.
Agents
Every agent with its requests, verified share and last visit. Open one to see when it comes back and where from.
Pages
The pages agents read, how many agents read each and the prompt it answers for, with coverage.
Agent-ready pages
The markdown and prerendered page settings and their results.
Audience
Results by audience and AI-referred visits, with Lytics connected.

Live activity

Each row is one answer or one crawl, such as “Someone asked ChatGPT about /pricing”, with where it came from and one verification label. Open a row to see how Contentstack Canoe knows.

Live activity: rows such as Someone asked ChatGPT about /pricing and GPTBot read 2 pages for training, each with network, data center, country and a verification label. The first row is open and shows how we know, the agent, requests, network, location, data center and pages.
The first row open on How we know.

Verification labels

Verified by Cloudflare
Cloudflare marked the request as a verified bot or a signed agent. Only for sites connected with Cloudflare.
Verified
Came from the agent's published network, or carried a valid signature for it.
Verified vendor
Came from the vendor's network, which several of its bots share.
Likely
Strong signals match the agent, but not full proof.
Signed, unknown signer
Carried a valid signature from a signer that isn't in the agent list yet.
AI tool
An AI tool, such as a coding assistant, fetched the page for a person.
Unverifiable
The vendor publishes no way to check this agent.
Unverified
Named an AI agent, but the claim couldn't be checked.
Spoofed
Named an AI agent, but came from a network that agent never uses.

More insights

Each one shows only when its source is there. Nothing shows as zero when it's simply not available.

Blocked by Cloudflare
AI agent requests Cloudflare blocked or challenged before they reached your site. Needs Zone > Analytics > Read. Cloudflare samples these counts.
AI Crawl Control
Your Cloudflare setting for each AI crawler: allow, block or charge. Needs Zone > Bot Management > Read.
AI referrals
People who reached your site from a link in an AI answer, by assistant and page. It's a minimum: app visits often carry no referrer, and most people never click.
robots.txt
Whether your robots.txt allows each agent, and requests to pages it disallows. Agents that fetch a page for a person aren't expected to follow it.
Gemini and Claude Code
Gemini's live fetch, which sends only Google as its user agent, counts as Gemini. Claude Code shows as an AI tool: it runs on a developer's machine, so it can't be verified.
The Agents view: each agent with its vendor and type, requests, verified share, requests blocked by Cloudflare and last visit.
Agents with Cloudflare connected and Zone > Analytics > Read granted.

Agent-ready pages

Off by default. Each option moves from Off to Shadow to On.

  1. Shadow. In Agent-ready pages, select Shadow next to Markdown for agents or Prerendered pages. Nothing changes for anyone. Contentstack Canoe records what agents would have received and prepares copies of the pages they ask for.

  2. Check. Shadow results shows what agents would have received. Content checks compares each copy with your normal page. A copy is served only when it passes, so agents get the same content and key facts as your page.

  3. On. Select On when the results look right. You can go back to Shadow or Off at any time.

Agent-ready pages with Off, Shadow and On for Markdown for agents and Prerendered pages, and More settings.
Both options start Off.
  • Preview a page shows what a person gets and what an agent would get for any URL on your site.
  • Serving needs an edge in front of your site: Cloudflare, Vercel, Netlify or a Deno proxy. A Node.js install, or a Cloudflare install that runs in front of your own Worker, reports visits only.
  • Pages that set cookies or private caching may be personalized, so they never get an agent copy.

Troubleshooting

The tab says “Waiting for the first agent visit”

Your site is connected but no visit has arrived. Open Integrations and select Check now on your integration. It names the step that failed.

My own test visit shows as Spoofed or Unverified

That's expected. A request from your laptop with an AI agent's name doesn't come from that agent's network.

Agent demand is empty

It needs verified visits to pages tied to your prompts. Check Coverage under Pages. New visits can take up to 15 minutes to show in the ranking.

I don't see the Agent Traffic tab

Agent traffic is an Enterprise feature that's turned on per workspace. Talk to us.