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.

michael_greenberg

PHPEnkoder is a port of the excellent <a href="http://hivelogic.com/enkoder" rel="nofollow ugc">Hivelogic 
Enkoder</a> to PHP and, more specifically, 
to WordPress. It is used to display text in a way that users can see 
and bots can’t.
The encoding system is directly and unabashedly stolen from the 
BSD-licensed source of Hivelogic Enkoder, which works by randomly 
encoding a piece of text and sending to the browser self-evaluating 
Javascript that will generate the original text. This works in two 
ways: first, a bot must first have a fairly complete Javascript 
implementation (in particular, it must have <code>eval</code>); second, the 
decoding process can be made arbitrarily computationally 
intensive. This is similar to the idea of charging computational 
payments to send e-mail, only this is actually implemented.
By default, PHPEnkoder scrambles e-mails in plaintext and in <code>mailto:</code> 
links. It additionally provides a shortcode for manual scrambling, 
used like so: <code>[enkode text="shown to non-JS browsers"]this will be 
scrambled[/enkode]</code>.

PHPEnkoder

Encodes mailto: links and e-mail addresses with JavaScript to stifle webcrawlers.  Automatically turns plaintext e-mails into (enkoded) links.

Aiso AI Crawler Analytics vs PHPEnkoder