Analytics for AI-agent traffic

Google Analytics can't see your most important new visitors.

AI agents read your site every day — deciding whether to recommend you. Agentlens shows you which ones, what they read, and what they can't.

14 verified agents · +38% m/m AI referrals · data in under an hour

voltaic.dev
Last 30 days

Agent visits

12,847

AI referrals

1,184 +38%

  • GPTBot

    OpenAI

    3,184 Verified
  • ClaudeBot

    Anthropic

    2,419 Verified
  • PerplexityBot

    Perplexity

    1,926 Verified
  • Amazonbot New

    Amazon

    412 Verified
+ 10 more agents Open the live demo →

How it works

Two planes of traffic. Two ways to measure.

Crawlers and humans behave differently, so Agentlens measures them differently — at the server for agents that never run JavaScript, in the browser for the humans they send you.

PLANE 01 · SERVER

Crawlers never run JavaScript.

GPTBot, ClaudeBot and PerplexityBot fetch raw HTML and leave. One middleware line records them at the edge — matched by user agent, then verified against the IP ranges each operator publishes.

npm i @agentlens/next

// middleware.ts
import { withAgentlens } from "@agentlens/next";
export default withAgentlens({ siteKey: "al_…" });

PLANE 02 · BROWSER

A cookieless snippet, under 2KB.

Catches the humans AI sends you — referrals from ChatGPT, Perplexity, Copilot, Gemini — and flags likely automated browsers. No cookies, no fingerprinting, no consent banner required.

<script defer
  src="https://app.agentlens.1labs.ai/al.js"
  data-site="al_…"></script>

Verified means user agent and published IP range confirmed. Likely means heuristics only. We label them differently everywhere, because a guess is not a fact.

Agents overview

Know every agent on your site.

Who's crawling, how often, what changed. Each agent comes with its operator, its purpose, whether it respects robots.txt — and an alert the day a new one shows up.

  • ~20 agents in the registry, refreshed weekly from operator sources
  • First-seen alerts: know the day Amazonbot finds you
  • Per-agent trends, page lists, and robots-compliance

Amazonbot started crawling Tuesday

First seen Jun 3 · 412 visits since

New agent

Agent visits · 30 days

daily

  • GPTBot OpenAI 3,184
  • ClaudeBot Anthropic 2,419
  • PerplexityBot Perplexity 1,926

AI-referred sessions · 30 days

1,184 +38% m/m

referrer-based

  • ChatGPT
    485 41%
  • Perplexity
    391 33%
  • Copilot
    166 14%
  • Gemini
    142 12%

Referrer-based. Answer engines that strip referrers aren't counted.

AI referrals

The chart that proves AI sends you customers.

When ChatGPT or Perplexity recommends you, a human clicks through. Agentlens attributes those sessions by source and landing page — so "AI is sending us customers" stops being a feeling and becomes a number you can put in a deck.

Top landing page for voltaic.dev: /docs/quickstart — 387 sessions

Readability audit

Find out what agents can't read.

Agents only recommend what they can read. The audit checks your robots.txt against every agent in the registry, your llms.txt, and whether your content survives without JavaScript — then hands you the exact fix for every failure.

Each check is run against your live site, with a copy-paste fix card — not a score with no instructions.

Pass

robots.txt allows all 14 verified agents

14/14
Pass

llms.txt present and fresh

updated 12d ago
Fail

/changelog is client-side rendered

FIX

Server-render your changelog — agents see a 217-byte shell. Your changelog is invisible to every crawler on this page.

Weekly report

Forward it to your CEO.

Every Monday: which agents read you, what they read, what AI sent you, and the one thing to fix. A public share link, a print-clean layout, and white-label on the Agency plan — built to be the email that gets forwarded.

See a real shared report →

Agent traffic report

Jun 1 – Jun 7, 2026

voltaic.dev

Agent visits

3,012 +12%

AI referrals

296 +9%

Readability

2/3 checks

  • GPTBot 742 +9%
  • ClaudeBot 561 +14%
  • PerplexityBot 438 −3%
  • Amazonbot 318 new

Perplexity read your 2024 pricing page 212× this month — it may be quoting prices that changed in January.

Generated by Agentlens · agentlens.1labs.ai

Cookieless. No personal data. The snippet is under 2KB. We count visits, not people.

GDPR-light by design — no consent banner needed for the sites you measure. Read the privacy policy — it's short on purpose.

Pricing

Honest plans. Plain limits.

Free

See your agents. Forever free.

$0 /mo

Start free
  • 1 site
  • 10k agent events / month
  • 30-day retention
  • Agents overview, referrals, readability audit
Most popular

Pro

For sites where AI visibility matters.

$29 /mo

Start free
  • 5 sites
  • 250k agent events / month
  • 12-month retention
  • New-agent + crawl-spike alerts
  • Weekly email reports + share links

Agency

Report AI visibility to your clients.

$79 /mo

Start free
  • 25 sites
  • 1M agent events / month
  • Everything in Pro
  • White-label reports
  • Client share links

Annual billing: $290/yr Pro · $790/yr Agency — two months free. Billing by Polar (merchant of record). Cancel anytime.

FAQ

Fair questions, straight answers.

Can't a bot just fake its user agent? +

Yes — and that's exactly why we have two labels. "Verified" means the user agent matched AND the request came from an IP range the operator publishes (or passed a reverse-DNS check). Spoofed UAs fail that check. "Likely" means the signals point to an agent but we couldn't confirm the source, so we say so. We will never present a guess as a fact.

What exactly does "Verified" mean? +

OpenAI, Anthropic, Perplexity, Amazon, Google, Apple and others publish the IP ranges their crawlers use. When a request's user agent matches a known agent and its IP is inside that agent's published ranges, we label it Verified. User-agent match without IP confirmation is labelled Likely — a different chip, in every table, always.

How is this different from Google Analytics? +

GA runs in the browser, so it only sees visitors that execute JavaScript. AI crawlers don't — GPTBot, ClaudeBot and PerplexityBot are invisible to it by design, and GA actively filters known bots out of reports. Agentlens measures from the server, where crawlers actually appear, then adds AI-referral tracking on top. Keep GA for humans; use Agentlens for everything it can't see.

Do I need a cookie banner to use Agentlens? +

No. The snippet sets no cookies, stores no personal data, and does no fingerprinting. It counts visits, not people — there is no identifier to consent to. (This marketing site shows a notice anyway, to say exactly that.)

What data does the snippet collect? +

Per pageview: the path, the referrer hostname, and a user-agent classification. The IP address is used once — salted-hashed for bot classification — then discarded; we never store raw IPs. Under 2KB of JavaScript, sent via a beacon. The full list is in the privacy policy, and it's short.

Can I cancel anytime? +

Yes. Billing is handled by Polar, our merchant of record — cancel in one click from the customer portal, keep access until the end of the period you paid for, and export your data for 30 days after. No retention mazes.

They're already reading your site. Start watching them back.

Free plan, no card. Data appears within an hour of install — usually minutes.

Built with ProductOS