The AI card sits below the geography and technology cards on your dashboard.
Three populations, kept apart
Most analytics products sort traffic into two buckets: people, and everything else they throw away. TrueStat keeps three.
| What it is | Where it shows | |
| Humans | People with browsers | The main tiles and every breakdown |
| AI crawlers | Assistants and training crawlers fetching your pages | This panel |
| Search crawlers | Googlebot, bingbot and the rest, indexing for search | This panel, in its own category |
Keeping AI crawling separate from search crawling is the point. They are different operators doing different things for different reasons, and folding Googlebot in with GoogleOther — as a simple "is this a bot" flag does — makes the number meaningless.
How the card is laid out
Four cards across the top, two tabs underneath. The cards pick what is counted; the tabs pick how it is broken down. Both choices survive each other, so you can look at training crawlers by operator, switch to pages, and still be looking at training crawlers.
The four cards
| Card | What it counts |
| AI answers | Fetches by an assistant answering someone's question right now — ChatGPT-User, Claude-User, Perplexity-User. A person is waiting at the other end. |
| Indexing | Ordinary search crawling — Googlebot, bingbot, Applebot, PerplexityBot. It keeps you findable in search and has nothing to do with AI training. |
| Training | Bots collecting text to train models — GPTBot, ClaudeBot, Bytespider, CCBot. Nobody is reading today; the page is going into a corpus. |
| AI referrals | People, not crawlers: someone clicked a link in an assistant's answer and landed on your site. |
The assistant/training split is the one worth watching. They have opposite
implications and call for different robots.txt decisions — blocking GPTBot
stops training while ChatGPT can still cite you; blocking Googlebot removes you
from search entirely.
Click a card and the list below changes to match it.
The number on a card counts the whole category. The list under it is ranked and long sites have a tail — a single day on a busy site can spread indexing across 180 separate paths. On most sites the rows add up to the card; on a large one they will not, and the card is the complete figure. Open Show all to see every row, with its own total at the foot of the list.
The two tabs
Crawlers — which operators, ranked. OpenAI, Anthropic, Google, Amazon, Yandex, Baidu and the rest, each with its own icon. This answers "who is reading me".
AI pages — which of your paths they fetched, ranked. See AI traffic by page.
Machine-readable files — llms.txt, your sitemap, the .md version of a page
— appear in that same list with a different icon, so you can tell them apart
from a page a person would read.
With AI referrals selected, both tabs show the pages people landed on, and which assistant sent them.
Verification
Under the chart, the share of crawler visits confirmed as genuinely from that operator. See How reliable is it.
The two dashboard tiles
Above all of this, on the main tile row:
AI crawler views — total crawler page views in the range. It ignores the "Hide bots" filter, because it exists to report what that filter removes.
Verified crawlers — the share confirmed by IP range rather than merely
claimed. A dash means no crawler visited; 0% means crawlers visited and none
could be verified. Those are opposite findings. See
How reliable is it.
Bot filtering does not apply here
Every card on this panel ignores the "Hide bots" toggle, on purpose. Turning bots off would empty the one feature you came for.
The AI panel's own filter is crawler type, so you can narrow the whole dashboard to, say, AI training traffic only.
Not the same as the AI channel
Your Traffic sources → Channels card has an entry called AI. That is a different measurement:
The AI channel counts people who clicked a link inside a ChatGPT, Perplexity or Claude answer and landed on your site.
This panel counts crawlers fetching your pages. No human involved.
Supply and demand. Read them together and you get "the assistants are reading me, and here is whether that turns into visits" — which neither answers alone. See Channels.