AI bot analytics · live
AI bots are reading your site. You can't see them.
GA, Plausible, and Fathom can't see AI crawlers — they fire from JavaScript, and bots don't run any. Geordy logs every request to every file, by bot, by format, by page.
Why your dashboard says zero when reality says thousands.
JavaScript pixels — the foundation of GA, Plausible, Fathom — only fire when a real browser executes them. AI crawlers never do.
JS-pixel analytics counts the humans your script tag executes for — 0 for every AI crawler. You see no AI activity, so you assume there isn't any.
Logs every request to every file Geordy serves.
By bot, by format, by page — no JavaScript involved.
You see the real consumption layer your other tools miss entirely.
The screen you've been missing.
Every AI request to every file you serve — by engine, by format, over time. The whole consumption layer, on one screen.
AI Bot Crawls
Track how AI bots access your structured content
| Bot | Total | YAML | Markdown | LLMs.txt | Schema | RSS | Manifest | Humans.txt | OG |
|---|---|---|---|---|---|---|---|---|---|
| 2,885 | 198 | 429 | 451 | 468 | 216 | 344 | 516 | 263 | |
| 2,587 | 477 | 64 | 389 | 179 | 371 | 429 | 353 | 325 | |
| 2,297 | 419 | 373 | 481 | 544 | 87 | 130 | 188 | 75 | |
| 2,274 | 177 | 197 | 429 | 150 | 480 | 535 | 194 | 112 | |
| 2,235 | 376 | 294 | 124 | 308 | 295 | 196 | 444 | 198 |
The read layer, finally on the record.
AI engines pull your content constantly and silently — then decide what to cite from what they found. Geordy writes down every visit, so the layer that shapes your AI visibility stops being a black box you have to guess at.
See who's reading — and what they take.
Every hit carries a fingerprint: which engine, which file, which status, how recently. Here is what that visibility makes possible.
Know exactly which AI is on your site.
Every bot that touches a Geordy-served file is matched against its user-agent — so GPTBot, ClaudeBot, PerplexityBot, Google-Extended and dozens more are named, not lumped into “other.” New entrants surface the moment they first crawl.
- Matched by user-agent, not guessed from IP
- 47+ engines known out of the box
- New crawlers appear on their first visit
See which files each engine reads.
ClaudeBot may reach for markdown while GPTBot pulls schema.json and Perplexity leans on llms.txt. Per-engine, per-format counts show where each system looks first — so you know which formats matter for which surface.
- Per-engine × per-format breakdown
- Spot the formats an engine ignores
- Prioritise what actually gets read
Find the reads that never made it.
Filter by status code to surface 4xx and 5xx — the crawls that failed. A soft-404, a bad redirect, a timeout: each is a page an engine tried to cite and couldn't. Fix it and the citation comes back within reach.
- Isolate 4xx / 5xx AI crawls in one filter
- See the exact URL and engine that failed
- Every broken read is a recoverable citation
Know when each engine last read you.
Publish an update and you're left guessing when AI will notice. Geordy timestamps every crawl — so you can see which engines came back this morning, which have gone quiet for days, and whether your latest content has been picked up yet.
- Last-seen timestamp per engine
- Spot engines that have gone quiet
- Confirm fresh content actually got re-read
Slice it your way.
Resolution by day, week, or month, across any date range. Zoom from a single overnight spike out to a whole season of trends — without leaving the view.
Take it anywhere.
Pull the raw numbers into your own stack, and get pinged the moment a brand-new engine starts crawling your site — so you never miss a new reader.
Stop guessing what AI sees. Watch it happen.
Connect a property in fifteen minutes. See your first bot visits within hours.