# 5-Minute WordPress AI Crawler Tracking Plugin Setup Guide (2026)

https://citaeotion.ai/wordpress-ai-crawler-tracking-plugin/

TLDR: The citAEOtion Collector is a WordPress AI crawler tracking plugin you install in about five minutes to log every AI bot at the server level and sort it by what each one wants.
The citAEOtion Collector is a WordPress AI crawler tracking plugin that installs in about five minutes: upload it, activate it, paste your API key, and save. It logs every AI crawler hit at the server level, the part Google Analytics cannot see, and sends it to your dashboard sorted by what each bot wants.
Quick answer: Set up the citAEOtion WordPress AI crawler tracking plugin in four steps: upload the Collector .zip, activate it, paste your API key under Settings, and save. From there it logs every AI crawler hit - GPTBot, ClaudeBot, PerplexityBot and more - and sorts them into four categories (AI Training, AI Search, AI Assistant, Data Scraper) with per-page counts, so you can prove crawlers reach your content and hand clients a branded report with real numbers.
Most "AI visibility" advice hands you a guess. You type a few prompts into ChatGPT or Perplexity, see whether your brand shows up, and call it a measurement. It is not. It is a guess about what people ask and a guess about what the model says back. citAEOtion does the opposite: it reads the record your server already keeps. Every time an AI bot requests a page, your server logs the bot, the page, the time, and the response. The Collector reads that record, names every crawler, and sends it to your dashboard - and the whole thing stands up in about five minutes, inside WordPress.
It matters more every month. On June 3, 2026, Cloudflare's Matthew Prince shared Radar data showing automated traffic had passed humans for the first time in the history of the web - 57.5 percent of all requests. When most of your visitors are machines, the question stops being how you rank on Google and becomes what the bots reading you actually do with your pages. You cannot answer that blind.
Track first, decide second
Most site owners do the opposite. They get nervous about AI scraping, install a block-everything plugin, and never look again. The problem is that blocking blind throws away the upside with the downside. A training crawler feeding your content into a model is how you get cited later. An assistant crawler fetching you live is how you get pulled into an answer right now. Block all of them and you have quietly removed yourself from the engines your buyers are starting to trust. citAEOtion's stance is simple: see everything first, then decide what to allow, throttle, or block - on evidence, not fear.
Install the citAEOtion Collector in about five minutes
The piece that goes on your site is the Collector - a lightweight WordPress plugin that detects AI crawler visits and ships them to your dashboard. No code, no prompts, no third-party analytics to wire up.
Step 1: Download the Collector
In your citAEOtion account, open the Setup tab and download the citAEOtion Collector (a standard WordPress .zip).
Step 2: Upload and activate
In WordPress, go to Plugins, then Add New, then Upload Plugin. Choose the Collector .zip, click Install Now, and when it finishes, click Activate.
Step 3: Paste your API key
Go to Settings, then citAEOtion, and paste the API key from the API Key tab of your account. Click Save. That is the entire configuration - there is nothing else to set.
Step 4: Watch the events flow
Open your citAEOtion dashboard. The first crawler event appears as soon as a bot visits a page, usually within minutes. From here the Collector runs 24/7 in the background, sending every AI crawler hit to your dashboard while you do nothing. If nothing shows within an hour, it is almost always one of three things: the API key has a stray space, your server cannot reach citaeotion.ai because of a firewall or DNS issue, or Settings then citAEOtion is showing a Last Error worth reading.
Reading your citAEOtion dashboard
The Collector sends the data; the dashboard is where you read it. It answers the only three questions that matter: which AI bots came, which pages they took, and when. What makes it different from every analytics tool you already run is the categories - because a bot that trains on you, a bot that decides whether you get cited, and a bot that just takes are three completely different things for your business, and lumping them together teaches you nothing. citAEOtion sorts every crawler into four:

Category
What the bot is doing
What it means for you

AI Training
Pulling your content into model training (GPTBot, ClaudeBot)
Shapes what the model knows about you; moves first, so it predicts citations

AI Search
Indexing you to answer searches inside AI engines
Decides whether you get named in the answer

AI Assistant
Fetching you live to answer a user's question now
Pulls you into an active answer this second

Data Scraper
Taking your content, attribution optional
Costs you bandwidth; throttle it on evidence, not a hunch

Under each category you get per-page counts - exactly which posts and pages each bot is hitting, how often, and the trend over time. Publish a new article and watch GPTBot arrive within the hour, and you know it is being ingested. See a high-value page that no AI crawler ever touches, and you know something is keeping them out. None of this shows up in Google Analytics, because AI crawlers do not run JavaScript - your normal analytics counts them as nothing at all.
Blocking, on evidence instead of fear
Once the data is in front of you, citAEOtion lets you act on it: allow the bots you want feeding and citing you, throttle the scrapers burning your bandwidth for nothing, block the ones that ignore the rules. The difference is that every one of those calls is now made from a record of what that exact bot did on your site, not a blanket rule that takes out the good crawlers along with the bad. Most "AI blocker" plugins make that decision for you, blind. citAEOtion gives you the data first so the decision is yours.
For agencies: real receipts, your logo
This is where it pays for itself if you run an agency. citAEOtion tracks every client site, and the reports export branded as yours - your logo, your service, no third-party tool in sight. So when a client asks what you are doing about AI search, you do not hand them a prompt tool's guess that falls apart the moment someone checks it. You hand them a clean report showing GPTBot crawled forty of their pages last month, and exactly which ones - real server data, the kind that survives scrutiny. That is the difference between reselling snake oil and reselling receipts. You do not have to understand the plumbing. You have to walk into the meeting as the one who clearly does.
Track first. The rest follows.
Guessing what the bots think of you is not a strategy. Reading what they actually did is. The citAEOtion Collector installs in five minutes and shows you the real picture the same day. That is the whole thesis in one line: the GA of AI. Full data. No BS.
See how the tracking works, or start reading your own crawler data.
Frequently Asked Questions
Will the Collector slow down my WordPress site?
No. The citAEOtion Collector is lightweight and sends crawler events in the background, so it does not block page rendering. The performance impact is negligible on standard hosting and effectively invisible on a VPS or dedicated server.
Does citAEOtion block AI crawlers by default?
No. It tracks first. Blocking is a deliberate choice you make once you can see the data: citAEOtion lets you allow, throttle, or block each bot individually, based on what it actually did on your site rather than a blanket rule.
Can I see which specific pages each AI bot visits?
Yes. Your citAEOtion dashboard shows per-page counts for every logged crawler, with the page URL, the timestamp, and the category. You can see exactly which of your posts and pages pull the most AI crawler attention, and which get ignored.
Does it work with caching plugins and CDNs?
Yes. The Collector logs crawler requests at the WordPress server layer, so it works alongside the usual caching plugins and CDN setups. Some edge-level caching can absorb a small share of bot requests before they reach the origin, but standard configurations log cleanly.
Is logging crawler data a privacy problem?
No. AI crawlers are automated bots, not people. citAEOtion records bot user-agents and the URLs they requested - standard server data, with no personal information about human visitors involved.
See your live AI crawler feed

---
Site: citAEOtion - https://citaeotion.ai/
LLM index: https://citaeotion.ai/llms.txt | Full text: https://citaeotion.ai/llms-full.txt