Some AI bots collect training data. Some build the index that AI search answers from. And some read your page right now, because a real person just asked an AI assistant a question. Sitenumbers tells them apart, so you know which visits actually matter.
Each AI company runs separate bots for separate jobs, and says so in its own documentation. Sitenumbers recognises each bot by name and checks that it really comes from the company it claims to.
Someone asked an AI assistant a question, and the assistant opened your page to answer it.
This is a visit on behalf of a real person. It never shows up in your visitor numbers, because the person may never click through. It is the closest thing to a direct measure of how often AI assistants use your content.
Your page is being added to the index an AI search answers from.
Being indexed is what makes it possible for an assistant to find and cite your page later. Pages these bots never fetch can't show up in their answers.
Your page was collected as material for training AI models.
Useful to know, and something you may want to allow or block. It doesn't by itself mean your page will appear in AI answers.
Other tools only see the people who click a link in an AI answer. Sitenumbers also sees how often assistants read your pages for their users, so you can compare the two, page by page.
A page that AI reads often but nobody clicks may be answering the question on its own. A page that gets read and clicked is doing its job.
AI analytics is easy to oversell. Here is exactly where the line is.
Some assistants also send people without a referrer, so part of their traffic looks like direct visits. Sitenumbers says so on the dashboard instead of guessing.
AI bots don't run JavaScript, so the tracking script you add for people never sees them. Sitenumbers counts them on your server or CDN instead. Pick the way that fits your site.
Only the bot's name, the page, the response status and the time are kept. Bot IP addresses are used once to confirm the bot is genuine, then discarded.
Copy a ready-made prompt from your site settings into Claude Code, Cursor or ChatGPT. It adds crawler tracking to your own stack, whatever it is.
Connect your Cloudflare account and Sitenumbers sets everything up for you. No code, no deploys.
Install the plugin, paste your site key, done.
One package and one line of middleware for Next.js, Express and edge functions.
Deploy our Worker on your Cloudflare zone. It passes every request through untouched and reports crawler hits in the background.
A small script reads your access log every minute and sends only crawler hits. Nothing else leaves your server.