About this plugin
Referral traffic from AI assistants is hard to measure: apps and many browsers send no referrer, so it lands in “direct”. Hand-checking AI answers is noisy too, because the same question gets different sources on different days.
Every AI assistant still has to fetch your pages from your server. RowanWeb Bot Traffic records those requests and sorts them by what the bot is doing, so you can track your visibility in AI answers (GEO) from data your site already has.
Bots sorted by intent
Bots are grouped by why they visit, not just by name:
- Citation — an AI assistant reads the page right now to answer a person: ChatGPT-User, Claude-User, Perplexity-User, MistralAI-User, DuckAssistBot and others. This is the closest server-side signal of your site being shown to people in AI answers.
- AI search indexing — the page is added to an AI search index for future answers: OAI-SearchBot, Claude-SearchBot, PerplexityBot, YandexAdditional and others.
- Model training — content collected for training: GPTBot, ClaudeBot, CCBot, Bytespider, meta-externalagent and others.
- Classic search — Googlebot, Bingbot, YandexBot and others, for comparison.
The bundled list covers about 60 bots and was checked against the operators’ own documentation wherever it exists. ChatGPT agent, which uses a regular browser user agent, is recognized by its signature header.
What you see on the dashboard
- Requests by intent with the change against the previous period.
- Filters for the whole dashboard: today, 7, 14, 30, 60 or 90 days (as far as your retention setting allows) or your own dates, plus bots, intents and HTTP status codes. The CSV export follows the same filters.
- A daily chart by intent or by bot, with your own event markers (“updated llms.txt”, “rewrote 40 articles”), so you can see what happened after a change.
- The pages AI bots read, with citations, indexing and training per page. The HTML and.md versions of the same post are counted together. You can also switch to raw paths to see requests for robots.txt, llms.txt and feeds.
- Requests by post type and category, and by HTTP status code.
- The most active bots with their intent, requests for.md files and llms.txt, and suspicious requests per bot.
- New bots that need a look. Unknown user agents are reviewed automatically once a day: uptime monitors, SEO tools, link previews, placeholder contacts and one-off visits are filtered out, so a new AI crawler is not lost among them. You can hide a bot you are not interested in, and an admin notice tells you when a new bot keeps coming back.
- Suspicious activity: requests for /.env, /.git/config, backup files and debug endpoints sent under AI bot names. They are kept out of the numbers above.
Privacy
The plugin records only requests whose user agent looks like a bot. Visitors are never recorded, and IP addresses are stored only for bot requests. Query strings are dropped, so tracking parameters and tokens in URLs are not saved.
Detailed data is kept for 90 days by default; you can choose from 30 days to a year in the settings. Everything is removed when you delete the plugin.
Sites behind Cloudflare or a proxy
If the site is behind Cloudflare or another proxy, set this up in Bot Traffic → Settings → Client IP address. Forwarded headers are trusted only from Cloudflare addresses, from a Cloudflare Tunnel running on the same server, or from the proxy addresses you list, so a bot cannot fake its IP.
Pro version
RowanWeb Bot Traffic Pro is a separate, paid version. Everything described above works fully in this free plugin. Pro adds:
- Cloudflare as a data source — counts bot visits served from the Cloudflare cache, which never reach PHP.
- Bot verification — checks each request against the official IP lists published by OpenAI, Anthropic, Perplexity, Google, Apple, Microsoft and others, or by reverse DNS, and keeps spoofed bots out of the numbers.
- Noise-aware event effect — compares the period after an event with a baseline that accounts for the day of the week and day-to-day spread, and shows the change with a confidence interval or says “within noise”.
External services
Freemius (optional opt-in, licensing and updates of the Pro version)
The plugin includes the Freemius SDK, which handles the separate Pro version’s licensing and updates. In this free version, Freemius only shows an optional opt-in screen after activation.
- When: only if you choose to opt in (or activate a Pro license).
- What is sent: your site URL, WordPress and PHP versions, plugin version, site language, and the admin’s name and email address, plus plugin activation, deactivation and uninstall events. If you skip the opt-in, nothing is sent.
- Freemius Terms of Service, Privacy Policy and details on what is collected.
Cloudflare Analytics API (Pro version only, optional)
com).
- When: once an hour by WP-Cron, only after you enter a Zone ID and an API token in the settings. The free version never contacts Cloudflare.
- What is sent: your zone ID, your API token (as authorization) and the time window. Cloudflare returns the user agent, IP address, host, path, status and response size of bot requests to your own site.
- Cloudflare Terms of Use and Privacy Policy.
Official bot IP lists (Pro version only)
The free version makes no requests to these services. org.
- When: once a week by WP-Cron.
- What is sent: a plain download request, nothing from your site.
- Bots that are checked by reverse DNS (Yandex, Baidu, Petal and as a fallback Google and Bing) are looked up through your server’s own DNS resolver.
Third-party libraries
- Chart.js 4.6.1, MIT License — the daily chart on the dashboard. Bundled locally in lib/chart.js/, nothing is loaded from a CDN. Source: https://github.com/chartjs/Chart.js
Support
ru/en/