# AI Traffic: proof the machines are actually coming

> For the complete site index for AI agents, see [llms.txt](https://airpulse.ai/llms.txt). Docs index: [docs.md](https://airpulse.ai/docs.md).

> In the product: Analytics → AI Traffic. Canonical: https://airpulse.ai/docs/ai-traffic

Everything else measures what engines say; AI Traffic measures what they do on your site.

Connect a domain (or upload server logs) and AI activity separates into three streams: AI Crawler (training and indexing bots), AI Search (retrieval fetches made while composing an answer), and AI Assistant (visits from assistants following through). The AI Citations card counts human visits referred by AI assistants — the number that ultimately justifies the whole program. Bot Signatures documents who is who; Blocked Requests shows what your infrastructure turned away, and the Pulse strip calls out notable crawlers.

![AI Traffic dashboard showing 123.0K total AI requests split into AI Search, AI Crawler and AI Assistant, 20 unique crawlers, 347 blocked requests and 32 AI citations](https://airpulse.ai/docs/ai-traffic.jpg)

*AI Traffic → Insights, minutes after a domain connection: 123.0K AI requests, 20 unique crawlers, Bytespider alone at 3,248 visits.*

## Terms on this screen

- **AI crawler** — A bot (GPTBot, ClaudeBot, Bytespider, PerplexityBot…) fetching your pages for training or indexing. Blocking the wrong ones erases you from future answers.
- **AI referral** — A human session that arrived from an AI assistant’s answer — AI’s equivalent of organic search traffic.
- **Bot signature** — The fingerprint (user-agent plus IP ranges) used to attribute requests to a specific AI operator.