The traffic your analytics cannot see.
Two things are happening on your site that a pageview counter misses entirely: people arriving from an AI assistant's answer, and the assistants themselves fetching your pages. Mrkr reports both.
What is AI traffic analytics?
AI traffic analytics measures two distinct things. First, humans who clicked through from an AI assistant's answer, identified by the assistant's referrer. Second, the AI and search crawlers that fetched your pages as raw HTML, which no JavaScript tracker can see because they never run it. You need both to know how AI is treating your site.
Almost every analytics tool reports the first one badly and the second one not at all. That is a measurement gap, and right now it sits underneath the single thing marketing teams most want to know.
- AI and search crawler hits in 30 days
- 25,564AI and search crawler hits in 30 days
- human pageviews on the same site, same window
- 2,946human pageviews on the same site, same window
- more crawler fetches than human pageviews
- 8.7xmore crawler fetches than human pageviews
- crawlers in the catalogue, matched server side
- 32crawlers in the catalogue, matched server side
Measured on a live site running Mrkr over 30 days. The crawler figures come from the server-side beacon at /api/data/crawl; the human pageviews from the ordinary browser tracker on the same site over the same window.
Half one: people from an AI answer.
When someone asks an assistant a question, reads the answer, and clicks a citation, that visit arrives with the assistant’s domain as its referrer. Mrkr groups those into one view: how many visitors, what share of your traffic they are, which assistants sent them, and which pages they landed on.
The landing-page list is the useful part. It tells you which of your pages an assistant considered worth citing, which is the only direct feedback loop you get on whether your content is being read by models at all.
Who was actually reading that site.
The top ten crawlers from that same 30-day window on a live site running Mrkr. Note how much of it is model training rather than search indexing, and that the assistant categories are the ones fetching on a real person's behalf.
| Crawler | Provider | Category | Hits in 30 days |
|---|---|---|---|
| Meta-ExternalAgent | Meta | Model training | 9,249 |
| Bingbot | Microsoft | Search index | 4,732 |
| ClaudeBot | Anthropic | Model training | 2,619 |
| Googlebot | Search index | 1,990 | |
| Amazonbot | Amazon | Search index | 1,679 |
| ChatGPT-User | OpenAI | AI assistant | 1,330 |
| OAI-SearchBot | OpenAI | Search index | 864 |
| YandexBot | Yandex | Search index | 796 |
| Applebot | Apple | Search index | 624 |
| PerplexityBot | Perplexity | Search index | 457 |
Measured on a live site running Mrkr over 30 days. Categories are Mrkr's own classification: assistant means a live fetch on a person's behalf, search means indexing, training means collecting data to train a model.
Half two: the crawlers themselves.
Crawlers request your HTML and leave. They do not download the tracker, they do not execute it, and they do not send a beacon. Every browser-based analytics product is structurally blind to them.
Mrkr reads them from the server instead. Your edge worker or framework middleware forwards each request’s User-Agent and path to a beacon endpoint, and Mrkr matches it against the catalogue and counts it. The catalogue lives on Mrkr’s side, so a new bot appearing next month is recognised without you shipping anything.
How to get an AI crawler to read you at all.
Serve the answer in the HTML
Crawlers do not run JavaScript. A client-rendered page is an empty shell to every bot in the table above.
Allow the agents you want
Training, search and assistant agents are separate lines in robots.txt. Blocking ChatGPT-User blocks a person who asked.
One question per URL, near the top
Assistants extract passages, not pages. A self-contained answer in the first screen is what gets lifted.
Publish a machine-readable summary
Plain headings, a current sitemap, and an llms.txt an assistant can read instead of guessing from a landing page.
Open the AI traffic view
The live demo includes the AI traffic page with real demo data, the assistant breakdown, and the crawler panel. No signup.
Open the live demoThe honest limits.
Only as complete as the beacon
Routes your edge does not forward are not counted. Mrkr counts what it is told about rather than modelling the gap.
User agents can be spoofed
Matching is on the User-Agent string, with no reverse DNS check. It reports what identified itself, not origin.
AI referrals are a floor
Some surfaces strip the referrer, and an answer read in a mobile app can arrive as direct. Treat the count as a minimum.
Questions, answered.
Keep reading
- Server-side tracking, honestly explained
Why the crawler beacon has to be server-side, and what else does not.
- Bot traffic filtering
The other side: keeping bots out of your human numbers entirely.
- Realtime analytics
The five-minute live window, and what updates when.
- Analytics adblockers do not block
The managed first-party proxy, and how filter lists actually match.
- Bots and spam documentation
Every signal the bot gate checks, and what happens to a blocked hit.
- Every Mrkr feature
The full index of what the product measures.
Your first visitor is already here.
Drop in the script and watch them land. It takes about a minute.