An agent can pull the site's AI-crawler analytics summary, recent crawler activity, robots.txt block status, a page's AI Visibility Score, and an MCP traffic summary. Everything is read-only reporting, nothing is changed on the site.
View AI Crawlers Visibility, Analytics & Control on WordPress.org
Needs WordPress 6.9 or newer for the core Abilities API and the AI Crawlers Visibility plugin active with its Agent Connect setting switched on. Every ability it registers requires the plugin's own admin capability, so a lower-privilege connected user cannot call any of them even through the Bridge.
Grouped by what each one can change. Every one starts off until you enable it.
Returns a summary of AI crawler traffic recorded by the plugin.
Returns the most recent AI crawler requests logged by the plugin.
Returns the current robots.txt AI rules and blocked-crawler status.
Runs the plugin's AI Visibility Score check on a given URL and returns the grade and findings.
Returns a summary of MCP tool traffic the plugin has logged.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. AI Crawlers Visibility, Analytics & Control registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from AI Crawlers Visibility, Analytics & Control starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. It registers five read-only abilities in the core Abilities API behind a moai-av namespace, so the Bridge can discover and expose them once an operator enables the setting.
The plugin's Agent Connect / MCP abilities setting must be turned on (an admin toggle under Settings, AI Visibility) before the abilities register. Each call also re-checks that the connected user holds the plugin's admin capability, in addition to the toggle being on.
Needs WordPress 6.9 or newer for the core Abilities API and the AI Crawlers Visibility plugin active with its Agent Connect setting switched on. Every ability it registers requires the plugin's own admin capability, so a lower-privilege connected user cannot call any of them even through the Bridge.
An agent can read OttoKit's SaaS connection status, access-control settings, system health (cron jobs, database table, webhook log counts), configured automation triggers, which supported integrations are active, and paginated webhook execution logs.
Once an operator turns on the relevant feature toggles, an agent can read a site's exposed settings, users, and post content and terms, and can ask the plugin's AI experiments to draft or suggest excerpts, titles, slugs, meta descriptions, editorial notes and updates, summaries, translations, classifications, type-ahead text, image alt text, generated images, and comment moderation or reply suggestions, though running the content-generation ones also needs an AI connector configured.
An AI agent can create a new AutomatorWP automation, add triggers or actions to an existing one, and run or execute an automation's actions immediately, using AutomatorWP's own no-code automation builder.
Verified from AI Crawlers Visibility, Analytics & Control's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, miniOrange or AI Crawlers Visibility, Analytics & Control. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.