Skip to content
snorklee
Sign in Start free
Features AI traffic Pricing Manifesto Docs Audit Contact Sign in
AI presence · the same metrics as the dashboard

Track your AI presence just like in the dashboard.

The front page uses the same units as the dashboard: AI presence score, AI crawls, AI chat visits, detected agents, cited pages and AI distribution. Crawlers and chat visits stay separate, aggregated and without analytics cookies.

Server-side recognised sources

The detection base behind AI presence.

Each AI crawler is detected server-side, then aggregated into the dashboard tiles: detected AI agents, AI activity over time and AI distribution. Human visits from AI chats are read separately from the referrer.

OpenAI

3 user-agents
  • GPTBotmodel 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-ExtendedGemini / Vertex AI training

Perplexity

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

Mistral 🇫🇷

1 family
  • MistralAI / MistralbotMistral crawler (Le Chat)

Meta

2 user-agents
  • FacebookBotLlama / Meta AI training
  • 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-aiCohere training
  • 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.

Without monitoring AI traffic, it is harder to see which pages these systems care about. Some informational queries may move through AI assistants: some crawl your pages, some send referral traffic, and others do not always send visitors back.

snorklee gives you a readable view: how many hits come from each recognised AI source, which pages are consulted, and how that channel evolves. It is an editorial signal alongside search, social and direct.

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

Exactly the dashboard tiles

The front page describes what the dashboard shows.

Labels and units are aligned with the AI presence section: AI presence score, AI crawls, AI chat visits, detected agents, cited pages, distribution and full report.

AI presence score

/ 100

The same indicator as the dashboard: a composite score computed only from actually observed signals, with AI crawls and AI chat visits.

AI agents detected

crawlers + chats

The same tile separates AI crawlers exploring your site from human visits arriving from an AI chat such as ChatGPT or Perplexity.

AI activity over time

timeline

The full report uses the dashboard interactive timeline to compare AI crawls and AI chat visits over the selected period.

Pages cited by AIs

URLs

The same logic as the dashboard tile: pages receiving traffic from AI assistants are listed with the observed sources.

AI distribution

purpose + provider

As in the dashboard, signals are split by purpose — training, search, assistant — and by observed provider.

Full report

dashboard popup

The dashboard Full report button opens the same set: KPIs, timeline, detected agents, cited pages and distribution, without a separate dedicated page.

This page does not promise anything the dashboard does not show: it describes the same aggregated and anonymous signals, with the same tile names.

How it works

Server-side detection, zero friction.

  1. Server-side User-Agent inspection. The tracker sends an HTTP event to /api/event. The server reads the User-Agent header, matches it against a list of known AI sources and tags the event with channel="ai" and the product name.
  2. No analytics cookie for this measurement. snorklee does not set analytics cookies for this measurement. Hits recognised as AI are separated from human traffic and shown as aggregated metrics.
  3. Aggregation in the AI presence section. The dashboard shows the same counters this page promises: AI presence score, AI crawls, AI chat visits, detected agents, cited pages and distribution by purpose/provider.
  4. Privacy documentation available. The stack is documented: Clever Cloud for the app, PostgreSQL and Cellar/S3; Scaleway Paris for the audit generator and domains; Brevo for email; DB-IP / Eris Networks for IP geolocation.

Start measuring your AI traffic today.

30-day free trial, no credit card. Or run a free GDPR audit of your site (instant result, no signup).