bentannenbaum

<p>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 <strong>those fetches are the new impressions</strong>. Most analytics tools never show them, because AI crawlers don’t run JavaScript and don’t appear in client-side analytics.</p>
<p><strong>Aiso AI Crawler Analytics reads the requests that actually hit your server</strong> 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.</p>
<h4>What you get</h4>
<ul>
<li><strong>Headline KPIs</strong> — total AI-crawler hits, “chat impressions” (live fetches during AI answers), distinct crawlers, and pages crawled.</li>
<li><strong>By AI platform</strong> — ChatGPT (OpenAI), Claude (Anthropic), Perplexity, Google/Gemini, Microsoft Copilot, Meta AI and more.</li>
<li><strong>By crawler / user-agent</strong> — the exact bots (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Googlebot, Bingbot, Bytespider, Applebot…).</li>
<li><strong>By purpose</strong> — training vs. citation-indexing vs. <strong>live chat impressions</strong> 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><strong>By page</strong> — which URLs AI assistants read most, with per-page impression counts.</li>
<li><strong>Over time</strong> — a daily activity chart so you can see trends and spikes.</li>
<li><strong>Live hit log</strong> — recent crawler visits with country and a source-IP verification badge that flags possible spoofed user-agents.</li>
<li><strong>CSV export</strong> — hand clients a report in one click.</li>
</ul>
<h4>Built for agencies</h4>
<p>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 <strong>nothing sent anywhere</strong>.</p>
<h4>Privacy-first</h4>
<p>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.</p>
<h3>External services</h3>
<p>This plugin connects to the Aiso API (https://www.getaiso.com) <strong>only when you enable syncing by connecting an account</strong>. 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.</p>
<ul>
<li><strong>When data is sent:</strong> only while “Send data to Aiso” is enabled in Settings, and only for AI-crawler hits (not human visitors).</li>
<li><strong>What is sent:</strong> 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><strong>What is not sent:</strong> human-visitor analytics, post content, or personal data of your readers.</li>
</ul>
<p>By connecting an account you agree to Aiso’s terms and privacy policy:</p>
<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>
<p>If you never connect an account, the plugin makes no external requests and stores all data locally on your own server.</p>


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.

aicrawlerguard.com

<p>AI Crawler Guard detects popular AI-focused crawlers and lets you block or allow them from scraping your WordPress site. Everything runs locally—rules, decisions, logs, and history stay on your server.</p>
<ul>
<li>Built-in signatures for common AI bots, plus optional custom patterns</li>
<li>Global and per-crawler allow/block controls</li>
<li>Local crawler registry with first/last seen timestamps and hit counters</li>
<li>Lightweight logs with optional retention cap</li>
<li>No external calls or remote storage</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 5.8 or newer</li>
<li>PHP 7.4+</li>
<li>Works with Classic Editor, Gutenberg, WooCommerce, and major managed hosts</li>
<li>Respects wp-admin, wp-login, REST API, cron, and CLI contexts automatically</li>
</ul>
<h3>Performance</h3>
<ul>
<li>Detection runs once per front-end request (small O(n) UA scan)</li>
<li>No blocking of social preview bots (Facebook, Meta, Twitter, LinkedIn) by default</li>
<li>Assets load only on plugin admin pages and stay under 10 KB</li>
<li>Logs stay capped by your configured limit with auto-pruning</li>
</ul>
<h3>Privacy</h3>
<p>All detection logic and data storage live entirely inside WordPress. No data is sent to third-party services in v1.</p>


AI Crawler Guard

Detect and control AI crawler access with local logging and history.

Aiso AI Crawler Analytics vs AI Crawler Guard