About this plugin
AI-O Optimiser measures the AI activity that reaches your WordPress site, and tells you whether AI systems and search engines can actually get to it. Everything in the first list below runs on your own site and needs no account and no API key.
Works as soon as you activate it:
- AI crawler and assistant activity — which AI systems have fetched your pages, and when. GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, Applebot, Google-Extended, Amazonbot and others, separated into discovery crawling, live assistant fetches and AI referrals.
- Edge-block detection — whether a CDN, firewall or security service is quietly refusing AI systems. A site can look completely normal in a browser while this is happening, so nobody finds out.
- llms.txt and AI guidance files.
- System and environment checks.
- AI Deep Review Prompt — a ready-made prompt to paste into any AI chat for a review of your site. No API key involved.
Nothing above is capped, metered or time-limited, and nothing asks for an email address first.
What is not in this edition
au/ai-o-optimiser/. They are not included and not disabled — that code is not in this plugin at all. Each of the three screens describes what its workspace does, so you can decide whether you want it:
- Metadata — scans every page’s title and description, groups what is missing, duplicated, or too long or short to survive, and applies approved changes in bulk.
- Schema — reads the finished page the way Google does, shows which plugin causes each structured-data conflict, and fills real gaps without duplicating what is already correct.
- Business details (NAP) — keeps your name, address and phone consistent across your site, your Google Business Profile, and the directories that list you.
The plugin distinguishes discovery/index crawling, live assistant fetches, AI referrals, platform/search evidence and sampled visibility. Crawler counts are not presented as people, prompts, citations or confirmed AI traffic.
Every recommendation the plugin makes — schema entity types, metadata, content opportunities, NAP corrections — is advisory. Suggestions are drawn from evidence AI-O can see and are applied only when an administrator confirms them, because whether a suggestion fits a particular page is an editorial judgement. Search engines and AI systems decide independently what they crawl, index, rank and cite, so no outcome is guaranteed.
NAP follows the same evidence discipline. The administrator-confirmed business identity is canonical. Once the administrator explicitly selects and imports the correct Google Business Profile location, that provider-backed identity becomes the practical baseline for managing external listings; automated checks are supporting evidence and administrator review of visible Name, Address and Phone is the only confirmation path.
Performance and privacy
Ordinary public requests use a deliberately small passive request-classification path. Provider, NAP-audit, Metadata workflow and admin code is excluded from normal visitor requests. Managed Schema runtime loads publicly only when managed fallbacks exist.
0 performance validation programme, so AI-O does not claim zero or negligible overhead.
Detailed request rows are retained for a bounded period while compact daily aggregates support longer-term reporting. Large admin jobs use resumable/background processing where implemented.
IP addresses are stored as salted one-way hashes. Query strings/referrers are reduced according to privacy settings. Connector Hub OAuth credentials and Google refresh tokens remain on the central Connector Hub; customer sites receive bounded evidence/results.
External services
This plugin can connect to external services to provide some of its features. No connection is made and no data leaves your site unless an administrator explicitly configures and enables the corresponding feature.
au until they reconnect) that centralises Google OAuth for Search Console, Google Analytics 4 (Data API) and Google Business Profile, so this plugin never stores your Google refresh tokens directly. When an administrator connects one from Settings or Dashboard → Traffic Impact, your site registers with the Hub (site URL and a generated connection identifier) and later exchanges signed requests for report data or listing details relayed from Google.
au/terms/
au/privacy-policy/
com using the administrator’s own GA4 Measurement ID and API secret.
com/privacy
Crawler identity verification — off by default. com, on a schedule and caches them locally, so checking a visiting request is done against a stored list rather than a live call. The requests are plain GETs for public JSON files: no query parameters, and nothing about your site or its visitors is sent.
Google and Apple publish no range list and document forward-confirmed reverse DNS instead, so for those the plugin resolves the requesting address and resolves the resulting hostname back again, which sends DNS queries from your server. Nothing here runs unless the setting is switched on.
com/policies/privacy-policy/
com/legal/privacy
ai/hub/legal/privacy