How to Track AI Crawlers in WordPress (GPTBot, ClaudeBot and More)
Quick answer: AI crawlers like GPTBot and ClaudeBot hit your WordPress site every day and never show up in Google Analytics. Here is how to see them, confirm they are real, and read what their visits actually mean.
⚡ Key takeaways
- → AI crawlers run no JavaScript, so GA4 never records them. To see GPTBot, ClaudeBot and PerplexityBot you have to read server-side requests.
- → A user-agent string is trivial to fake, so verify each bot before you trust the count.
- → The visit's intent matters: a training crawl and a live-answer fetch mean very different things for your visibility.
- → CiteTrack AI logs and verifies 50+ AI bots inside WordPress and classifies why each one came.
AI crawlers are visiting your WordPress site right now. You just cannot see them.The problem is that the place most people look, Google Analytics, is completely blind to bots. So the very traffic that decides whether ChatGPT or Perplexity will ever quote you does not show up in your analytics at all.This guide shows you how to actually see those crawlers, how to tell a real GPTBot from an impostor, and how to read what the visits mean for your AI visibility.
Why Google Analytics never shows AI crawlers
GA4 measures humans. It fires when a browser loads your page and runs its JavaScript tracker. AI crawlers request your raw HTML and leave; there is no browser and no script execution, so GA4 records nothing. You could be crawled thousands of times a month by OpenAI, Anthropic and Perplexity and see a flat zero in your analytics. The only place these bots reliably appear is in your server's own request logs, which is where any real AI crawler tracking has to look.
The AI crawlers worth knowing
You do not need to memorize every bot, but a handful matter most for AI citations.
| Crawler | Run by | What its visit usually means |
|---|---|---|
| GPTBot | OpenAI | Training and indexing for ChatGPT |
| OAI-SearchBot | OpenAI | Building ChatGPT's search index |
| ChatGPT-User | OpenAI | A live fetch while answering someone now |
| ClaudeBot | Anthropic | Training and indexing for Claude |
| PerplexityBot | Perplexity | Indexing for Perplexity answers |
| Google-Extended | Gemini and AI Overviews access |
The fuller list and what each one does is in the Crawl Academy lesson on GPTBot, ClaudeBot and PerplexityBot.
Step one, see who is crawling you

Start by reading your server access log, where every bot leaves a row. You can do this manually by filtering the log for known user-agents, but that is slow and error-prone. The free AI Crawler Log Analyzer does it for you: paste a log file and it shows which AI bots visited, how often, and which pages they read, all in your browser with nothing uploaded. It is the fastest way to get a first picture of your AI crawl activity.
Step two, verify the bot is real
Here is the trap that ruins most bot tracking. Anyone can set their user-agent to "GPTBot," and scrapers do it constantly to look legitimate. If you count by name alone, your numbers are inflated by impostors, and a fake GPTBot hitting your login page can look like AI interest when it is just an attack. Real verification uses reverse-DNS confirmation and published IP ranges to prove a request actually comes from OpenAI, Anthropic or Perplexity. Insist on it, or treat raw counts with suspicion. The full verification method takes two DNS lookups and catches every impostor.
Step three, read the intent behind the visit

Not all crawls mean the same thing. A bot fetching your page to train a model is different from a bot fetching it live to answer someone's question right now. The second kind, like ChatGPT-User, is a leading indicator that you are appearing in an AI answer, because a real person triggered it. Tracking that separates a flat hit count from a real visibility signal. A spike in live-answer fetches on a page is one of the earliest hints that you are being cited.
Step four, watch for crawl waste and blocks
Once you can see the crawlers, two patterns are worth watching. The first is crawl waste, AI bots spending their visits on thin archives or filtered URLs instead of your money pages; trimming that focuses their attention where it counts. The second is accidental blocks. If a bot you want suddenly stops appearing, check your robots.txt and host rules, because a silent block is the most common self-inflicted reason citations dry up. The free AI Crawlability Checker confirms which bots your rules currently allow.
How CiteTrack tracks crawlers continuously

A log analyzer gives you a snapshot; continuous tracking gives you the picture over time. CiteTrack AI's crawler analytics runs inside WordPress, logging 50+ AI bots as they arrive, verifying each one with reverse DNS, flagging spoofs, classifying intent, and showing your most-crawled pages and how often each engine returns. The data stays in your own database with hashed IPs, so nothing leaves your site. If you want to connect crawler data to citation tracking and revenue attribution, the full WordPress analytics stack shows how the three layers fit together.
Frequently asked questions
How do I see which AI bots crawl my WordPress site?
Read your server access log, where every bot leaves a request, or use a tool that does it for you. The free AI Crawler Log Analyzer turns a log file into a readable view of which AI bots visited and which pages they read. For continuous tracking, CiteTrack AI logs them live inside WordPress.
Why don't AI crawlers show in Google Analytics?
GA4 runs client-side JavaScript and AI crawlers do not execute JavaScript, so they never trigger its tracking. They only appear in server-side requests, which is where AI crawler tracking has to look.
How do I know a GPTBot visit is real?
Verify it. A user-agent string is easy to fake, so a real check confirms the request comes from OpenAI's published network using reverse-DNS and IP-range checks. Without verification, your bot counts are inflated by impostors and scrapers.
What is the difference between a training crawl and a live fetch?
A training crawl feeds a model; a live fetch, like ChatGPT-User, happens when an engine grabs your page to answer someone right now. The live fetch is a leading indicator that you are appearing in an AI answer, which is why intent classification matters.
Should I block AI crawlers?
Usually not, if you want citations, because a blocked bot cannot quote you. The exception is deliberate choices about training access. Most sites accidentally block the very fetchers they want; the crawlability checker shows what your rules currently allow.
Where to go from here
Crawler tracking is one layer. To see whether those crawls actually turn into citations, add citation tracking on WordPress so you can close the loop. The full WordPress analytics stack connects crawlers, citations, and revenue attribution in one view. And if you want the foundational concepts, the Crawl Academy covers what AI crawlers are, the specific bots you will see, and how to verify they are real.
See it in your own WordPress dashboard
Find out if AI recommends you — or a competitor
Install CiteTrack AI and see exactly who crawls you, who cites you, and what it earns. Flat pricing from $59/year, 14-day money-back guarantee.
Want to see if AI cites pages like this?
CiteTrack AI tracks your AI crawlers, citations, and the revenue they drive, inside WordPress.
Explore: Features · Crawl Academy · Glossary · Compare · Pricing
