Skip to content
snorklee
AI traffic Analytics Clone watch Pricing Manifesto Documentation Contact Sign in Try free for 14 days
AI traffic · passively measured, never guessed

Your site's complete AI visibility: crawled, fetched, visited.

What AI bots read on your site, what an AI opens live to answer someone, and the visitors ChatGPT, Perplexity or Claude send you. All of it measured on your real traffic — no fake questions sent to AIs, no guessed visibility.

tab · visibilite-ia Demo data
AI FUNNEL30 D
Crawled by AIs4 812
Fetched live317
Visited from an AI chat236

The three stages, plainly: Crawled = an AI bot passed over your pages · Fetched live = an AI opened a page to answer a question · Visited = a human arrived from an AI chat. Each stage is counted separately, with no cookie at all.

In plain terms: we watch what AIs actually do with your pages — how much they read them, what they come to fetch, who they send you — instead of guessing your visibility.

Real, not simulated

Measured, not guessed.

Most AI visibility tools guess your presence by asking AIs thousands of made-up questions. Snorklee reads your site's real AI traffic instead.

Typical AI visibility tools

  • Source: made-up questions, sent to AIs
  • Metric: an estimated presence (a percentage)
  • Data: fabricated, outside your site

Snorklee

  • Source: your site's real AI traffic
  • Metric: observed crawls, live fetches and visits
  • Data: your own, cookieless, hosted in Europe

Snorklee doesn't claim to know the exact question behind a fetch or a visit (nobody receives that information) — it shows the AI traffic actually received.

Seen in your dashboard

AIs already read your site. Now you can see it.

Three dashboard cards, exactly as they appear: which AI bots come to you, how many visits arrive from ChatGPT or Perplexity, and which pages AIs read to answer.

AI activity detected crawlers + visits Every assistant recognised by name: on one side the bots that read your site (ChatGPT, Claude, Perplexity, Gemini), on the other the visitors who came from an AI chat.
AI presence score + timeline Presence score, AI bot passes, live fetches and AI chat visits — tracked over time.
Fetched pages & breakdown URLs + providers The pages AIs fetch and visit, and the breakdown by provider (OpenAI, Anthropic, Perplexity, Google).
The bots we can recognise

Every AI bot we know how to spot.

Every AI bot is recognised as it passes, then gathered into your dashboard cards: AI activity detected, AI activity over time and AI crawler breakdown. Human visits from AI chats are counted separately, from the link they clicked.

We keep this list current and, every night, we fetch the official address lists published by OpenAI, Perplexity and Anthropic. That's what lets us say a hit really is who it claims to be, not just self-declared.

OpenAI

3 user-agents
  • GPTBotassociated with model training
  • ChatGPT-Useron-demand browsing
  • OAI-SearchBotSearchGPT engine

Anthropic

3 user-agents
  • ClaudeBotClaude indexing crawler
  • anthropic-ailegacy Anthropic agent
  • Claude-Webon-demand browsing

Google

1 user-agent
  • Google-Extendedassociated with Gemini / Vertex AI

Perplexity

2 user-agents
  • PerplexityBotindexing crawler
  • Perplexity-Useron-demand browsing

Mistral

1 family
  • MistralAI / MistralbotMistral crawler (Le Chat)

Meta

2 user-agents
  • FacebookBotassociated with Llama / Meta AI
  • Meta-ExternalAgentMeta AI external agent

ByteDance

1 user-agent
  • BytespiderByteDance AI crawler (Doubao)

xAI

2 user-agents
  • Grokbotindexing crawler
  • Grok-Useron-demand browsing

Other LLMs & archives

9 user-agents
  • Applebot-ExtendedApple Intelligence
  • cohere-aiassociated with Cohere
  • CCBotCommon Crawl archive (base dataset for many LLMs)
  • YouBotYou.com engine
  • DuckAssistBotDuckDuckGo Assist
  • AmazonbotAmazon training (Alexa+)
  • PetalBotHuawei AI engine
  • DeepSeekBotDeepSeek crawler (China)
  • Diffbotstructured extraction (used by multiple LLMs)
Why it matters

AI traffic is no longer marginal.

In 2025-2026, ChatGPT, Perplexity, Gemini and their peers are becoming important access points to information. Users ask questions and often get answers built from web pages — sometimes with an outbound link, sometimes without a direct visit.

Your current tools can't see it. GA4 files 60 to 70% of traffic coming from AI assistants under “Direct”, and AI bots often represent 20 times the human traffic they send back — invisible to a classic analytics tool, which never sees a bot go by.

Snorklee gives you a readable view: which bots come by, which pages they read, which ones an AI opens live to answer — and the pages “read but never visited”, your best pages to work on first. A new signal, alongside search, social and direct traffic.

Honest note: we measure AI visibility (who reads you, how often). We don't promise placement in ChatGPT or Perplexity answers — that depends on the AI itself and nobody controls it.

Check my AI visibility — free →
The AI traffic tab

Everything the tab shows you.

Eight cards, all fed by your real traffic: the journey and its curves, the standout moments, the share of your visits coming from an AI, the sources, the bots and the pages. What's probable stays separate from what's certain.

Funnel Crawled → Fetched → Visited

3 stages + curves

The three counters with their change vs the previous period and a daily curve per stage — never added together: each stage keeps its own unit.

AI moments

timeline

First visit from an AI, first live fetch, weekly high for AI share, peak of bot passes: the standout moments, spotted automatically and dated — with the AI's logo.

AI share of traffic

daily %

The share of your human visits coming from an AI assistant, day by day — to see whether the AI era already weighs on your acquisition.

Sources

assistant logos

ChatGPT, Perplexity, Claude, Gemini & co: who sends you humans, how many visits, and the trend — recognised server-side, never estimated.

AI crawlers

family + purpose

Every bot by family, with its observed purpose: training collection, search indexing, or live fetch while answering.

Pages as AIs see them

the lever

Page by page: crawled, fetched, visited. Pages “read, never visited” rise to the top — AIs consume your content without sending anything back: your first traffic reserve.

Pages visited from an AI answer

top visits

Where the humans sent by assistants land — ranked by real visits, with the change vs the previous period.

Invisible AI traffic (estimated)

separate tier

Arrivals spotted from an excerpt of your text, and an estimate of the direct traffic that lands right after an AI has fetched a page (we look at the timing overlap, page by page). Always labelled “Estimated” — never mixed with the real numbers.

All these cards are available as soon as your 14-day free trial starts.

How it works

Two ways we spot the AIs.

  1. Visitors from AI chats: your tag is enough. When a visitor clicks a link in ChatGPT, Claude or Perplexity, their browser opens your page and says where it came from. Snorklee recognises the assistant and files the visit on the “AI” side, with its name — nothing more to install.
  2. AI bot passes: capture on your server. GPTBot, ClaudeBot or PerplexityBot read your page without ever displaying it the way a browser would: a classic tag never sees them go by. To count them, add the small server-side code Snorklee provides (Express, Cloudflare, Vercel/Netlify, PHP, WordPress plugin) — ready-to-use code and a step-by-step guide, without even creating an account.
  3. Bot identity verified. Anyone can pretend to be GPTBot by changing one line of code. When a bot's vendor publishes the list of its addresses, Snorklee checks every hit against it: impostors are removed from your numbers, and the dashboard tells you how many.
  4. It all comes together in the AI traffic tab. No cookie for either measurement. The AI traffic tab brings together the Crawled → Fetched live → Visited journey, the share of visits coming from an AI, the standout moments, the sources, the bots by family and the pages involved.
  5. Our privacy setup is documented. Our whole infrastructure is spelled out: Clever Cloud for the app, PostgreSQL and Cellar/S3; Scaleway Paris for the audit generator and domains; Brevo for email; DB-IP / Eris Networks to place a country from the IP address.
Référence

Who these bots actually are.

People often ask us whether GPTBot and ChatGPT-User are the same bot. They are not. The first collects pages to train a model; the second opens your page while an AI answers someone. Blocking both under one policy means cutting off traffic you meant to keep. So here, bot by bot, is what each one does — and which ones publish their IP addresses, which is what lets you check they really are who they claim to be.

Bot Vendor What it does Identity verifiable
GPTBot OpenAI Collects to train a model Yes — published IP ranges
OAI-SearchBot OpenAI Indexes for search Yes — published IP ranges
ChatGPT-User OpenAI Reads the page live to answer Yes — published IP ranges
ClaudeBot Anthropic Collects to train a model Yes — published IP ranges
Claude-User Anthropic Reads the page live to answer Yes — published IP ranges
PerplexityBot Perplexity Indexes for search Yes — published IP ranges
Perplexity-User Perplexity Reads the page live to answer Yes — published IP ranges
Google-Extended Google Collects to train a model No — no ranges published
Applebot-Extended Apple Collects to train a model No — no ranges published
Meta-ExternalAgent Meta Collects to train a model No — no ranges published
Bytespider ByteDance Collects to train a model No — no ranges published
CCBot Common Crawl Collects to train a model No — no ranges published
Amazonbot Amazon Undetermined purpose No — no ranges published
mistralai-User Mistral Reads the page live to answer No — no ranges published
DuckAssistBot DuckDuckGo Reads the page live to answer No — no ranges published
PetalBot Huawei Collects to train a model No — no ranges published

A number is worthless if you do not know what it proves. Our three stages do not measure the same thing and do not count the same unit: we never add them up. Here is what each one establishes — and, more importantly, what it does not.

Stage How it is captured What it proves What it does not prove
Crawled Bot user-agent, read server-side A bot fetched this page Does not prove the page will be cited
Fetched live Bot whose stated purpose is “assistant” An AI opened the page during a conversation Does not say what the AI did with it
Visited Visit referrer (chat.openai.com, perplexity.ai…) A human came from an AI answer Misses arrivals with no referrer
FAQ

Frequently asked questions.

Does Snorklee guarantee placement in ChatGPT answers?
No. It measures visibility (who crawls, how often), not placement.
How are AI bots counted?
Server-side via a beacon; visits from chats via the referrer.
Which assistants are detected?
GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others, on a maintained list.
Do you send prompts to the AIs?
No, never. Snorklee runs no synthetic prompts and extrapolates no visibility: it passively observes what AIs actually do on your site — bot crawls, live fetches and visitors sent from chats.
Do I need a cookie or a consent banner?
No. AI traffic is measured server-side for crawlers and via the referrer for visits from a chat, with no cookie and no banner. First-party data, cookieless, hosted in Europe.
How is this different from a typical AI visibility tool?
Typical AI visibility tools estimate your visibility by sending thousands of made-up prompts to AIs. Snorklee reads the AI traffic your site actually receives: bot crawls, live fetches and visits from chats. It's measured, not guessed.
How much does it cost?
One plan, Snorklee One: from €8/month ex. VAT, all included — full analytics, AI traffic, up to 10 sites. 14-day free trial, cancel online anytime.

Start measuring your AI traffic today.

14-day free trial, cancel online anytime. Or run a free GDPR audit of your site (instant result, no signup).