Claude CMS analytics now reads your web server’s own log as well as counting visitors without cookies. So you can see what most dashboards can’t: which AI assistants and crawlers read your pages, how often, and how few of those reads ever turn into a visit.
Ask ChatGPT or Perplexity a question and the assistant will often read a few web pages, then answer from them. The person gets what they needed without ever visiting. For the website that supplied the answer, that read is invisible in ordinary analytics: they run in the visitor’s browser, and an assistant’s fetcher never runs a browser script.
Your web server sees it anyway. Every request, from a person or a program, lands in the server’s access log with the name of whatever made it. Claude CMS now reads that log for you. In the first three weeks after we switched it on for claudecms.com (17 September to 9 October 2026):
Analytics that only run in the browser would have shown us the visits and nothing else. A fetch is not a visit, and one conversation can fetch the same page more than once, so these are not conversion rates. But the gap is the point: most of the reading never shows up as traffic.
Claude CMS analytics now draws on two sources, and each one sees what the other can’t:
| The browser beacon | The server log | |
|---|---|---|
| Counts | People: anyone whose browser loads the page | Machines: AI assistants, AI crawlers and search engines |
| Shows you | Pages, sources and campaigns, time on page, scroll depth, country and device | Which agent, which pages, how often, and its robots.txt checks |
| Can’t see | Bots, because they never run the script | What people do once a page has loaded |
| Cookies | None | None: it is the server’s own record |
Put together, you see both audiences a website now has: the people who visit it, and the assistants that read it on people’s behalf.
Claude CMS recognises 25 AI agents and search engines by the name they announce, and sorts them into four kinds:
For each one you see how often it came, which pages it read and how often it checked your robots.txt. Beside them, the visitor side shows the people those assistants send: a visit from ChatGPT, Claude, Perplexity, Gemini, Copilot or nine other assistants is credited to the one that sent it.
The visitor side needs no cookies. Each visit gets a code worked out from a key that changes every day, plus the visitor’s IP address and browser. Only the code is stored, so nobody can be followed from one day to the next, and the IP address itself is never kept. Nothing is saved on the visitor’s device, and visitors can switch counting off.
You get the figures you would expect: visitors, sessions, top and landing pages, sources and campaigns, countries and devices, page speed, and clicks out and downloads. Uptime monitors and scanners that drive a real browser from cloud servers are set aside automatically. On three of the newest sites we host, they were close to nine in ten of the early “visitors”.
Analytics is part of Claude CMS hosting, with nothing to buy, install or configure. Sites deployed on our hosting have it from day one. An older site switches it on with one sentence to Claude, and the Analytics page in your account shows the sentence to copy. Every visit is kept for 90 days, then as daily totals for 16 months.
The log needs our hosting. Reading a server’s log takes access to the server, so the AI readers panel is on sites we host. A self-installed site still gets the visitor figures. Either way, two things stay with you: mention the analytics in your privacy notice, and give visitors a visible way to opt out. Claude can add both for you.
Because the figures live in your own site’s database, Claude can read them too: ask which AI bots read your pricing page this week, and it will look. You will find the dashboard under Analytics in your Claude CMS account, and the cookieless analytics page goes through every feature.