VigIA abilities, governed through the Bridge

An agent can pull AI-crawler traffic stats, top crawlers and top crawled pages, see which crawlers are blocked and which robots.txt rules exist, then block or unblock a crawler and add or remove a robots.txt Disallow rule.

Abilities
95 read2 write2 destructive
Active installs
1K+
Rating
100% (19 ratings)
Version
2.6.6
Requires
WP 6.9+, PHP 7.4+
Last updated
2026-09-18 11:50pm GMT

What has to be true first

Needs WordPress 6.9 or later with VigIA active. Every ability checks manage_options; the four write/delete abilities (block-crawler, unblock-crawler, add-robots-disallow, remove-robots-rule) are additionally gated by a filter kill-switch (vigia_can_write_via_abilities, default true) a site owner can use to disable mutations while keeping the read abilities working.

  • The four write/delete abilities (block-crawler, unblock-crawler, add-robots-disallow, remove-robots-rule) additionally check the vigia_can_write_via_abilities filter (default true), which a site owner can set to false to disable them while keeping the read abilities working

The 9 VigIA abilities

Grouped by what each one can change. Every one starts off until you enable it.

Read 5

  • Read

    Get Crawler Statistics

    Returns statistics about AI crawler visits including total visits, unique crawlers, and unique pages crawled.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-get-crawler-stats
  • Read

    Get Top Crawlers

    Returns a list of the most active AI crawlers sorted by visit count.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-get-top-crawlers
  • Read

    Get Top Crawled Pages

    Returns a list of the most crawled pages on the site.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-get-top-pages
  • Read

    Get Blocked Items

    Returns the list of currently blocked crawlers and IP addresses.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-get-blocked-items
  • Read

    Get Robots.txt Rules

    Returns the current AI crawler rules configured in robots.txt.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-get-robots-rules

Write 2

  • Write

    Block Crawler

    Blocks an AI crawler by User-Agent pattern or IP address; blocked crawlers receive a 403 response.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-block-crawler
  • Write

    Add Robots.txt Disallow Rule

    Adds a Disallow directive for an AI crawler in robots.txt.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-add-robots-disallow

Destructive 2

  • Destructive

    Unblock Crawler

    Removes a block by its ID.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-unblock-crawler
  • Destructive

    Remove Robots.txt Rule

    Removes a Disallow or Allow rule for a crawler from robots.txt.

    Permission
    manage_optionsAdministrators
    MCP tool
    aafm-bridge-vigia-remove-robots-rule

How to switch these on

Four steps from two active plugins to a governed connection.

  1. Install VigIA and Agent Abilities for MCP

    Both plugins need to be active on the same WordPress site. VigIA registers its own abilities; this plugin discovers and governs them.

  2. Open the Other plugins screen

    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.

  3. Enable one ability at a time

    Every ability from VigIA starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.

  4. Connect as a least-privilege user

    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.

Frequently asked questions

Does VigIA work with the Bridge?

Yes. It registers nine crawler-analytics abilities in the core Abilities API with clear readonly/destructive annotations, so the Bridge can discover and expose each one once enabled.

What has to be true for VigIA's abilities to register?

The four write/delete abilities (block-crawler, unblock-crawler, add-robots-disallow, remove-robots-rule) additionally check the vigia_can_write_via_abilities filter (default true), which a site owner can set to false to disable them while keeping the read abilities working.

Does VigIA need anything special to work with the Bridge?

Needs WordPress 6.9 or later with VigIA active. Every ability checks manage_options; the four write/delete abilities (block-crawler, unblock-crawler, add-robots-disallow, remove-robots-rule) are additionally gated by a filter kill-switch (vigia_can_write_via_abilities, default true) a site owner can use to disable mutations while keeping the read abilities working.

More SEO plugins

An agent can read and change Rank Math's SEO, sitemap, redirection, breadcrumb, and website-identity settings, read per-post SEO scores, schema markup, and link reports, run and fix a site-wide SEO audit, and manage tracked brands in the AI Visibility feature.

SEO4M+ active installs
18 read11 write
Built-in integration tooView abilities

An agent can read and update a post's SEO title, description, focus keyword and canonical URL, find posts missing SEO data or with low TruSEO scores, manage custom robots.txt rules, and pull a homepage or site-wide SEO audit.

SEO2M+ active installs
9 read4 destructive
Built-in integration tooView abilities

Verified from VigIA'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, Fernando Tellado or VigIA. Back to the full directory.

Back to the plugin directory

Bridge VigIA, keep the same control.

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.