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.

Arnan

Tired of spam bots in your WordPress and ClassicPress website? Do you want to get rid of false registrations and other spammy nonsense? Don’t wan’t to use a clumsy and user-unfriendly Captcha? Don’t want to use a Captcha from Google or other big-tech company period?
Meet No-Bot Registration, easy to use, superior protection without making it hard for your visitors. Easily blacklist (partial) email addresses and domains so they can no longer register an account.
Create one or more questions and a set of possible answers for them and visitors have to answer your question when they register. 
If they answer wrong, they get denied their account.
Questions can be as simple as “1 + 1”, with possible answers being 1, one or uno. That way you can plan for eventualities and how people interpret your question.
<h4>Features</h4>
<ul>
<li>Protect registration forms</li>
<li>Protect the WooCommerce checkout form if you let people register from there</li>
<li>Protect your blog comment form</li>
<li>Prevents comment spam, trackback spam and other nuisances with ease</li>
<li>Set up multiple security questions to further confuse bots</li>
<li>Blacklist any email, domain or tld you don’t like</li>
<li>Configurable notification messages for users failing the security tests</li>
</ul>

No-Bot Registration

Prevent bots from creating accounts by blacklisting domains and usernames and present people with a human friendly security question.

Aiso AI Crawler Analytics vs No-Bot Registration