bentannenbaum

Search is moving inside AI assistants. When someone asks ChatGPT, Claude, Perplexity or Google’s AI a question, those assistants quietly fetch real web pages — and those fetches are the new impressions. Most analytics tools never show them, because AI crawlers don’t run JavaScript and don’t appear in client-side analytics.
Aiso AI Crawler Analytics reads the requests that actually hit your server and turns them into a clean, agency-ready dashboard right inside wp-admin. Think of it as the “AI visibility” companion to your security log — focused entirely on AI search performance instead of threats.
<h4>What you get</h4>
<ul>
<li>Headline KPIs — total AI-crawler hits, “chat impressions” (live fetches during AI answers), distinct crawlers, and pages crawled.</li>
<li>By AI platform — ChatGPT (OpenAI), Claude (Anthropic), Perplexity, Google/Gemini, Microsoft Copilot, Meta AI and more.</li>
<li>By crawler / user-agent — the exact bots (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Googlebot, Bingbot, Bytespider, Applebot…).</li>
<li>By purpose — training vs. citation-indexing vs. live chat impressions vs. search vs. agentic browsing, so you know whether a bot is just training a model or actively quoting you in an answer.</li>
<li>By page — which URLs AI assistants read most, with per-page impression counts.</li>
<li>Over time — a daily activity chart so you can see trends and spikes.</li>
<li>Live hit log — recent crawler visits with country and a source-IP verification badge that flags possible spoofed user-agents.</li>
<li>CSV export — hand clients a report in one click.</li>
</ul>
<h4>Built for agencies</h4>
Connect the plugin to a free Aiso account and every site you manage reports into one central place, so your AI-visibility data is kept long-term and viewable across your whole portfolio. Not an agency? The plugin works completely on its own — install it and the dashboard fills up locally with nothing sent anywhere.
<h4>Privacy-first</h4>
Visitor IPs are anonymised by default (stored only as a salted hash). The plugin records AI-crawler requests, not your human visitors, and never transmits any data externally until you explicitly connect an Aiso account.
<h3>External services</h3>
This plugin connects to the Aiso API (https://www.getaiso.com) only when you enable syncing by connecting an account. It is used to (a) optionally generate an API key for your site and (b) store your AI-crawler hits centrally so they are retained long-term and can be viewed across multiple sites.
<ul>
<li>When data is sent: only while “Send data to Aiso” is enabled in Settings, and only for AI-crawler hits (not human visitors).</li>
<li>What is sent: the requested path and URL, the crawler’s user-agent, the detected bot and company, an optionally-hashed source IP, a two-letter country code, the HTTP status, a timestamp, your site URL, and your Aiso API key.</li>
<li>What is not sent: human-visitor analytics, post content, or personal data of your readers.</li>
</ul>
By connecting an account you agree to Aiso’s terms and privacy policy:
<ul>
<li>Terms: https://www.getaiso.com/quick_links/terms_of_service</li>
<li>Privacy policy: https://www.getaiso.com/quick_links/privacy_policy</li>
</ul>
If you never connect an account, the plugin makes no external requests and stores all data locally on your own server.

Aiso AI Crawler Analytics

See which AI assistants — ChatGPT, Claude, Perplexity, Google and more — crawl your site, broken down by assistant, crawler, purpose and page.

zicygp

Zicy AI Access Monitor helps site owners understand when known AI crawlers and AI assistant retrieval agents access their WordPress content.
The plugin logs self-identifying AI-related User-Agents, summarizes raw visits into daily totals, and provides an admin dashboard for reviewing AI access patterns across your site. It is designed for AI visibility, AI search optimization, and content monitoring workflows.
What it tracks:
<ul>
<li>Search crawlers — AI systems that may crawl content for search or answer retrieval workflows, such as OAI-SearchBot and PerplexityBot</li>
<li>Training crawlers — AI-related crawlers that may access content for model training or dataset-building workflows, such as GPTBot, ClaudeBot, CCBot, Amazonbot, Bytespider, CohereBot, Mistral-ai, and Meta-WebIndexer</li>
<li>User proxies — AI assistant fetchers that retrieve pages when responding to user requests, such as ChatGPT-User, Claude-User, Perplexity-User, Gemini-Deep-Research, Google-Agent, and BingPreview</li>
<li>AI control agents — AI-related User-Agents such as Google-Extended that may represent AI data-use control behavior rather than ordinary search crawling</li>
</ul>
How it works:
<ol>
<li>Matching visits are recorded as temporary raw logs.</li>
<li>URLs are normalized to reduce duplicates caused by common tracking parameters.</li>
<li>IP addresses are anonymized by default before being stored.</li>
<li>Each night at 02:15 site time, raw logs older than today are summarized into daily totals.</li>
<li>Raw logs that have been rolled up are deleted.</li>
<li>Daily summary records are retained so you can review historical AI access activity.</li>
</ol>
In your WordPress admin dashboard:
<ul>
<li>View daily summaries of known AI bot and AI assistant access</li>
<li>See today’s raw logs before the next rollup</li>
<li>Filter by date, bot, type, or signature</li>
<li>Review top pages accessed by AI assistant user proxies</li>
<li>Compare week-over-week activity for top pages</li>
<li>See vendor diversity indicators for accessed pages</li>
<li>Export daily summary data as CSV</li>
<li>Receive weekly email summaries with top accessed pages</li>
<li>Generate copy-ready AI Tracking Briefs for selected pages</li>
</ul>
Why it matters:
<ul>
<li>See which known AI systems are accessing your content</li>
<li>Identify which pages AI assistants retrieve most often</li>
<li>Support AI search optimization and AI visibility reporting</li>
<li>Understand differences between crawler, training, control, and user-triggered AI access</li>
<li>Build structured page briefs that can be used in AI visibility workflows</li>
</ul>
Bot allowlist includes:
<ul>
<li>OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User</li>
<li>Anthropic: ClaudeBot, Claude-User, Claude-SearchBot</li>
<li>Perplexity: PerplexityBot, Perplexity-User</li>
<li>Google: Google-Extended, Gemini-Deep-Research, Google-Agent</li>
<li>Microsoft: BingPreview</li>
<li>Amazon: Amazonbot</li>
<li>Common Crawl: CCBot</li>
<li>ByteDance: Bytespider</li>
<li>Cohere: CohereBot</li>
<li>Mistral: Mistral-ai</li>
<li>Meta: Meta-WebIndexer</li>
</ul>
Developers can extend or modify the allowlist with the <code>gp_aibal_ai_bots</code> filter.
Important detection note:
This plugin detects only self-identifying User-Agents. It does not guarantee that every visit is from the claimed company or system, because User-Agent headers can be spoofed. The plugin should be used as a visibility and reporting aid, not as a security or access-control tool.
<h3>Privacy</h3>
Zicy AI Access Monitor is designed to keep raw request-level data temporary.
The plugin stores matching AI-related access events in your WordPress database, anonymizes IP addresses by default, rolls raw logs into daily summaries, and deletes rolled-up raw logs. Daily summaries are retained for reporting. The plugin does not send logged access data to Zicy or any third-party service.
Site owners are responsible for ensuring that their use of access logging complies with applicable privacy laws and their own privacy policy.

Zicy AI Access Monitor

Monitor known AI crawlers and AI assistant fetches, with daily rollups, CSV exports, weekly summaries, and page briefs.

Aiso AI Crawler Analytics vs Zicy AI Access Monitor