Visits from AI assistants
People who arrive from ChatGPT, Claude, Perplexity, Gemini, Copilot and others land in an AI assistants channel, by referrer or by the utm_source the assistant adds to its links.
Search crawlers, AI crawlers and AI agents read your pages every day. Little Friend counts them apart from people, shows how sure it is about each one, and lets you choose which get in.
Automated requests have their own count. A crawler's requests never add to your page views, and each AI request counts under one purpose: AI training, AI search indexing, Assistant fetching for a user, AI agent or agentic browser.
| Class | Meaning |
|---|---|
| Search crawler | Indexes pages for a search engine, like Googlebot or Bingbot. |
| AI crawler | Collects pages for AI training or retrieval, like GPTBot or ClaudeBot. |
| User-directed AI agent | Fetches a page because a person asked an AI assistant to, like ChatGPT-User. |
| Uptime and monitoring | Uptime checks and monitoring services. |
| Link preview | Builds a link preview when someone pastes your URL into a chat or a post. |
| Suspected automation | Scripted traffic that hides or misstates who runs it. |
| Unknown | Not enough signal to say. |
A user agent is a claim. Every verdict carries the evidence behind it, so "GPTBot" from OpenAI's published addresses reads differently from "GPTBot" anywhere else.
| Evidence | What it means |
|---|---|
| No evidence | Nothing backs up who runs it. |
| Self-declared (user agent) | The user agent names an operator. Anyone can send any user agent, so this is a claim. |
| Verified network (DNS or published IP range) | The request came from the operator's network: a reverse DNS check or a published IP range matched. |
| Verified request signature | The request carried a valid cryptographic signature from the operator (Web Bot Auth). |
| Authenticated credential | An authenticated credential identified the client. That proves the client, not its operator. |
People who arrive from ChatGPT, Claude, Perplexity, Gemini, Copilot and others land in an AI assistants channel, by referrer or by the utm_source the assistant adds to its links.
For each company that runs an assistant, Little Friend divides the AI requests it made by the visits its assistants sent back, so you see who reads a lot and sends little.
Little Friend reads your robots.txt and lists the disallowed routes each crawler requested anyway.
The door runs in your Worker, proxy or server and decides on each request before your app runs: allow, slow down, block, require a signature. Every project starts in dry run, so you see what your rules would do before they change anything.
| Preset | What it does |
|---|---|
| Open | Let every agent in and record what it does. Every project starts here. |
| No training | Block crawlers that collect pages to train AI models. Search engines and assistants still get in. |
| Verified only | Block agents that fail their operator check, and slow down agents that cannot show who runs them. |
| Commerce | Checkout, cart and account pages need an agent acting for a signed-in user. Browsing stays open. |
Most crawlers never run JavaScript, so a browser script alone can't see them. Little Friend reads the requests themselves.
Ask Claude about your traffic Google Analytics alternative Little Friend vs Google Analytics
Little Friend is free during the beta. Sign up, paste one script tag, and watch your first visit arrive.
No card needed.