A WordPress AI crawler tracking plugin must read real server traffic, not JavaScript. Tag-based analytics record zero bot hits because crawlers never run the script.
A WordPress AI crawler tracking plugin logs every AI bot hit by reading server-side request data, so it captures GPTBot, ClaudeBot, and PerplexityBot visits that Google Analytics cannot see.
Quick answer: A WordPress AI crawler tracking plugin records AI bot visits by capturing them at the server request level, where crawlers actually arrive, instead of relying on a browser JavaScript tag that bots never execute. The right plugin classifies each request by user-agent, verifies it against published IP ranges, and reports which bot (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Bytespider, Amazonbot) hit which URL, when, how often, and with what HTTP status. citAEOtion ships a WordPress collector that does exactly this and sends the classified data to a dashboard, turning raw crawler traffic into a readable per-bot, per-page report.
Why a JavaScript analytics plugin will not work
Most WordPress "analytics" plugins inject a script that runs in the visitor browser. AI crawlers request the HTML and leave without running scripts, so a tag-based plugin logs none of them. If your goal is to know whether ChatGPT or Perplexity is reading your posts, a browser-tag plugin is the wrong tool by design. You need something that observes the request itself, on the server, before any rendering. That server-side view is what lets you detect AI crawlers that browser tags miss.
What to look for in a WordPress AI crawler tracker
- Server-side capture. The plugin must read the actual request (user-agent, IP, URL, status), not fire a browser pixel. This is the single feature that decides whether it sees bots at all.
- Bot classification by real hits. It should identify each crawler by its user-agent token and group traffic by vendor and purpose (training, search index, live fetch), based on requests that truly landed.
- IP verification. Good trackers confirm a claimed GPTBot against OpenAI's published range so spoofed headers do not pollute your data.
- Per-page and per-bot reporting. You want to see which URLs draw crawlers and which get ignored, plus the HTTP status each bot received, so you catch a bot hitting a 404 or a redirect loop.
- Timestamps and frequency. Crawl cadence over time tells you whether AI interest in your content is rising or flat.
- Low overhead. Collection should not slow page loads or bloat the database.
How the citAEOtion collector works, at a high level
citAEOtion installs a lightweight WordPress collector that observes incoming requests server-side and records the signals that identify a crawler: the user-agent, the source IP, the requested URL, the HTTP status, and the timestamp. It classifies each hit by bot and category from that real traffic, verifies against published crawler IP ranges, and passes the classified events to the citAEOtion dashboard. There you get one screen showing which bot hit which page, when, how often, and with what status code. The collector measures what reached your server; it does not guess from prompts. See exactly how the collector and dashboard fit together.
Why "read the server, not the browser" is the whole point
This is the wedge that separates real AI crawler tracking from marketing analytics. Browser tools such as Google Analytics miss AI bots because bots do not run JavaScript. Prompt-based tools like some visibility trackers ask a model questions and infer whether it knows your site, which is a guess. A server-log collector sees the ground truth: the request that actually happened. citAEOtion is built on that ground truth, which is why we call it the GA for AI. It does this measurement for you, on your WordPress site, without you reading a log by hand. Single-site tracking is $34.99 per month, with agency plans and a Founders Club discount for early accounts.
Frequently Asked Questions
Does a WordPress AI crawler plugin slow down my site?
A well-built server-side collector adds minimal overhead because it records request metadata rather than running heavy scripts on every page load. Look for a plugin that logs efficiently and does not bloat the database.
Can I just use Google Analytics for this?
No. Google Analytics uses a JavaScript tag that AI crawlers never execute, so it reports zero bot visits. Tracking AI crawlers requires server-side capture.
Which AI bots does a good plugin track?
GPTBot, OAI-SearchBot, and ChatGPT-User from OpenAI; ClaudeBot from Anthropic; PerplexityBot; plus Bytespider, Amazonbot, and Meta-ExternalAgent, each identified by its user-agent and verified by IP.
How is this different from a prompt-based AI visibility tool?
Prompt tools ask an AI model questions and infer whether it knows your brand. A log-based plugin measures the real crawler requests that hit your server, so it reports facts rather than estimates.
Does the plugin verify bots or just read user-agents?
The stronger plugins verify. They cross-check a claimed crawler against the vendor published IP range so a spoofed user-agent does not count as a real GPTBot or ClaudeBot hit.
Vendor reference on responsible crawling: Anthropic support, ClaudeBot crawling and site-owner controls.