Which AI assistants have read your site, which of your pages they read, and how far you can trust the number.
| Page | Covers |
| Recording crawlers from your server | Set this up first — without it the panel sees almost nothing |
| What this panel shows | The four cards, and what each one counts |
| Which crawlers are recognised | The current list, by operator and by reason |
| AI traffic by page | Which of your pages the assistants actually read |
| Humans vs AI over time | Reading the two series together |
| Why other analytics tools cannot show you this | The one-line reason, which is about collection rather than reporting |
| How reliable is it | How a crawler is identified, and the honest limits |
The panel is empty until you add server-side tracking
The tracking script runs in a browser and most AI crawlers do not use one, so the script never loads and the visit is never recorded. On a real site the gap is large: 4 crawler visits recorded against 203 human ones over three days, two of the four being test requests.
Recording crawlers from your server is one HTTP call from your backend. It is the only thing that fills this panel.
Two things to read before you quote a number from this panel
It currently undercounts, and by an unknown amount. Most AI crawlers request raw HTML and never run JavaScript, so a browser tracking script — ours or anyone else's — cannot see them. How reliable is it explains what that means for your numbers today and what is being built about it.
Google-Extended will never appear here, and its absence is not a gap. It makes no requests at all. See Which crawlers are recognised.
Available on every plan
AI visibility is included on both tiers, at every traffic step. It is not gated behind the higher tier and it is not an add-on. It is the reason to choose TrueStat, and putting it behind an upgrade would hide the only argument we have.