VigIA – AI Visibility, Analytics & Control
Monitor 60+ AI crawlers, control access via robots.txt, and boost your AI visibility with llms.txt, JSON-LD, Markdown for Agents & Visibility Score.
Safe pick
Yes — VigIA is a safe, well-maintained plugin to use in 2026. It runs on 1K+ sites, is rated 5/5 and was last updated 1 week ago, and scores 86/100 on our health check.
- Actively developed — last update 1 week ago
- Tested with the latest WordPress (7.1)
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where VigIA stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| AI | #74 |
| analytics | #35 |
| Claude | #21 |
| gpt | #6 |
| llms | #12 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 19 reviews
About VigIA
From the official readme · v2.6.6Description
VigIA (Spanish for “lookout” or “watchman”, incorporating “IA” – Spanish for “AI”) is a complete AI visibility toolkit for WordPress. Monitor 60+ AI crawlers, control access to your content, and optimize how AI systems discover and understand your site.
What does VigIA do?
- Scores your AI visibility with a 100-point analyzer covering 20 checks across 5 categories
- Tracks AI crawlers visiting your site (GPTBot, ClaudeBot, PerplexityBot, and 60+ others)
- Provides detailed analytics with advanced filters, server-side pagination, and exportable reports with metadata banner
- Blocks unwanted crawlers via PHP (403 response)
- Manages robots.txt rules for AI crawlers with compliance monitoring
- Sends email alerts about crawler activity (daily, weekly, or monthly)
- Generates llms.txt files to help AI systems understand your site
- Serves markdown endpoints for posts, pages, taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products with schema-like data
- Generates JSON-LD structured data with Site Identity and AI Discovery signals
- Exposes abilities for AI agents and automation tools (WordPress 6.9+)
Key Features
AI Visibility Analyzer
* 100-point scoring system with letter grades (A+ to F)
* 20 individual checks across 5 categories
* Access & AI Discovery (37 pts): robots.txt, AI bot directives, Content Signals, llms.txt, sitemap, RSS feed
* Structured Data & Semantic Context (25 pts): JSON-LD schemas, Open Graph, Twitter Cards, meta description, canonical URL
* Content Structure & Readability (20 pts): heading hierarchy, semantic HTML5, image alt text, content/HTML ratio
* AI Interaction & Distribution (8 pts): markdown delivery, AI share buttons
* Access Performance (10 pts): TTFB measurement
* Smart recommendations with direct links to VigIA features and plugin suggestions
* Analyze any page on your site with URL autocomplete selector
* Results cached for 24 hours with manual re-analyze option
Analytics Dashboard
* Total visits, unique crawlers, and pages crawled statistics
* Timeline chart with daily breakdown
* Category distribution (AI Training, AI Search, AI Assistant, Data Scraper)
* Top crawlers and most crawled pages tables with paginated navigation
* Share Buttons & AI-powered Summaries integration: see share button clicks per page
* Recent activity log with content type and HTTP status columns (color coded by status family)
* Advanced filters: multi-select crawler picker, content type, HTTP status code, and configurable date range
* Server-side pagination with four-button pager (first, previous, next, last) — operates over the full database, not just the latest 500 rows
* Period comparison functionality
* CSV export with a metadata banner (site name, site URL, export type, date range, export timestamp, applied filters)
* “Export filtered CSV” button that downloads exactly what the active filters return, with vigia-filtered-YYYY-MM-DD.csv filename
* Content type detection distinguishes Home, Post, Page, Product, custom CPTs, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File, Admin / login attempts (/wp-admin, /wp-login.php), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other
Crawler Blocking
* Block crawlers via PHP with 403 Forbidden response
* Quick block dropdown in analytics dashboard
* Manage blocks from Extras page
* Works on any server (Apache, Nginx, LiteSpeed, etc.)
Robots.txt Management
* Add Disallow rules for AI crawlers
* Visual preview of your robots.txt
* Compliance monitoring: see which crawlers ignore your rules
* One-click blocking for non-compliant crawlers
* Works with both physical and virtual robots.txt
Email Alerts
* Daily, weekly, or monthly reports
* Three detail levels: Minimal, Normal, Complete
* Non-compliant crawler warnings
* Activity comparison with previous period
Markdown for Agents
* Serve posts, pages and any public post type as optimized markdown for AI agents
* Serve taxonomy archive pages (categories, tags, WooCommerce product categories, custom taxonomies) as markdown — disabled by default, opt in per taxonomy
* Dedicated .md URL endpoints (e.g., /your-post.md, /category/news.md, /product-category/electronics.md)
* Accept: text/markdown content negotiation on posts and taxonomy archive pages
* Discoverability via Link HTTP headers and <link rel="alternate" type="text/markdown"> HTML tags
* YAML frontmatter for posts: title, date, modified, author, image, categories, tags, post type, lang
* YAML frontmatter for taxonomy terms: title, description, url, type, taxonomy, parent, count, image (term meta), lang
* WooCommerce product frontmatter adds schema-like fields: sku, product_type, price, regular_price, sale_price, currency, availability, stock_quantity, rating, rating_count, review_count
* Taxonomy term body includes the term description (rendered through the_content), the list of direct child terms in hierarchical taxonomies, and an excerpt of the latest posts/products assigned to the term
* Product listings inside product_cat archives include an inline summary with formatted price, “was X” on sale items, star rating and out-of-stock flag
* Respects blocking rules (blocked crawlers get 403) and LLMs.txt exclusion filters
* Per-term noindex detection from Yoast SEO, Rank Math, All in One SEO and SEOPress
* Analytics integration: tracks markdown requests per crawler
* X-Markdown-Tokens response header
* Filters: vigia_markdown_post_eligible, vigia_markdown_term_eligible, vigia_markdown_term_posts_limit
* Follows the Cloudflare Markdown for Agents standard
LLMs.txt Generator
* Select content by post type with one click
* Filter by taxonomies (categories, tags, custom)
* Manual include/exclude with AJAX search
* Exclude by URL patterns (wildcards supported)
* SEO plugin integration (auto-exclude noindex content)
* Auto-regeneration (daily, weekly, monthly)
* Robots.txt integration (add llms.txt and llms-full.txt references)
* Generate llms.txt and llms-full.txt files
* Full content or excerpt mode
* Compatible with Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer
JSON-LD Structured Data
* Generate WebSite and Organization/Person schema for site identity
* AI Discovery: ReadAction pointers to llms.txt, llms-full.txt, and Markdown for Agents endpoints
* Social profiles and sameAs links for brand identity across the web
* SearchAction for Google sitelinks search box
* Media library integration for logo selection
* SEO plugin conflict detection (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework)
* Choose output page (front page or any published page)
* Live JSON-LD preview with real-time updates
* Smart integration with LLMs.txt and Markdown for Agents features
Supported AI Crawlers
VigIA monitors 60+ AI crawlers including:
- OpenAI: GPTBot, OAI-SearchBot, OAI-AdsBot, ChatGPT-User
- Anthropic: ClaudeBot, Claude-SearchBot, Claude-User, Claude-Code
- Google: Google-Extended, GoogleOther, Gemini-Deep-Research, Google-NotebookLM
- Perplexity: PerplexityBot, Perplexity-User
- Meta: Meta-ExternalAgent, FacebookBot, Meta-WebIndexer
- Amazon: Amazonbot, Amzn-SearchBot, bedrockbot
- Mistral: MistralAI-User, MistralAI-Index
- Microsoft: BingBot
- ByteDance: Bytespider
- Apple: Applebot-Extended
- And many more…
Privacy Focused
VigIA stores visitor data locally in your WordPress database. No data is sent to external servers.
Abilities API
VigIA is one of the first WordPress plugins to implement the Abilities API introduced in WordPress 6.9. This API allows AI agents, automation tools, and external systems to discover and interact with VigIA’s functionality in a standardized, secure way.
What are Abilities?
Abilities are self-contained units of functionality that VigIA exposes through WordPress’s central registry. Each ability has defined inputs, outputs, and permissions, making it easy for automation tools to understand and use them.
Available Abilities
VigIA registers the following abilities:
Analytics
vigia/get-crawler-stats– Get statistics about AI crawler visits (total visits, unique crawlers, pages crawled)vigia/get-top-crawlers– Get a ranked list of most active AI crawlersvigia/get-top-pages– Get the most crawled pages on your site
Blocking
vigia/get-blocked-items– List all blocked crawlers and IP addressesvigia/block-crawler– Block a crawler by User-Agent patternvigia/unblock-crawler– Remove an existing block
Robots.txt
vigia/get-robots-rules– Get current AI crawler rules in robots.txtvigia/add-robots-disallow– Add a Disallow directive for a crawlervigia/remove-robots-rule– Remove a robots.txt rule
Use Cases
- Automated monitoring: AI agents can query crawler statistics and alert you to anomalies
- Reactive blocking: Automation tools can block crawlers that repeatedly ignore robots.txt
- External dashboards: Aggregate data from multiple WordPress sites with VigIA installed
- WP-CLI integration: Future command-line access through the Abilities API
- n8n / Make workflows: Build custom automation flows using VigIA’s abilities
Requirements
The Abilities API ships with WordPress 6.9 and later. On older WordPress versions, VigIA works normally but abilities and MCP are not available.
MCP Server (Model Context Protocol)
VigIA exposes its 9 abilities as native MCP tools to any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Codex CLI, Antigravity, Continue, Cline, Zed and similar) using the official WordPress MCP Adapter. The adapter ships bundled with the plugin, so the MCP endpoint is active right after installation — no Composer step or terminal access required.
Requirements
- WordPress 6.9 or later (provides the Abilities API)
Quick connect (recommended)
Open VigIA > Extras > MCP and click “Generate password and connection commands”. The plugin creates a dedicated Application Password named VigIA MCP and renders ready-to-paste commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) for any other MCP client.
The plain password is shown only once. If you lose it, revoke the entry from the same panel and generate a new one.
Endpoint
https://your-site.example/wp-json/vigia/v1/mcp
The endpoint uses HTTP Basic auth with the WordPress Application Password. The user must have the manage_options capability.
Connecting Claude Code
Quick Connect builds the full command for you. The shape is:
claude mcp add --transport http vigia https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD"
Claude Code merges the new entry into its config file automatically — no risk of breaking other servers.
Connecting Cursor
Save the JSON block from Quick Connect as ~/.cursor/mcp.json. You can also reach this file from inside Cursor at Settings → Cursor Settings → MCP.
If the file already exists with other content, see the FAQ.
Claude Desktop and other clients
Claude Desktop does not speak HTTP MCP, so it needs a small bridge and a config file of its own. Any other client (Codex CLI, Continue, Cline, Antigravity, Zed, or your own) takes the two raw values Quick Connect exposes: the server URL and the Authorization header. Both cases are covered in the FAQ, together with how to merge VigIA into a config file that already exists without losing what is in it.
Read-only mode
If you only want your AI to consult VigIA (not change anything), enable “Read-only mode” in the MCP tab. While on, write actions (block, unblock, robots changes) return a permission denied error. Read actions (statistics, top crawlers, blocked items, robots rules) keep working.
The toggle stores a vigia_mcp_read_only option that hooks into the vigia_can_write_via_abilities filter. Developers can still force read-only from a mu-plugin:
add_filter( 'vigia_can_write_via_abilities', '__return_false' );
The mu-plugin filter at the default priority takes precedence over the toggle.
Who can reach the endpoint
The endpoint requires the capability to manage options, the same one every tool behind it already asked for. The vigia_mcp_transport_capability filter can lower that bar; each tool keeps its own permission check.
After connecting
Restart your MCP client after adding the server so it picks up the new tools. Then try a few prompts to confirm everything is wired up:
- “Show me VigIA crawler stats for the last 7 days.”
- “List the top 5 most crawled pages on this site.”
- “Add a robots.txt Disallow rule for TestBot and then list the current AI crawler rules.”
The third example exercises a read + write + read round-trip, which is the most complete sanity check.
Support
Need private support or custom development?
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need.
Need help or have suggestions?
Love the plugin? Please leave us a 5-star review and help spread the word!
About AyudaWP
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.
Installation
- Upload the plugin files to
/wp-content/plugins/vigia/or install through the WordPress plugins screen - Activate the plugin through the ‘Plugins’ screen in WordPress
- Navigate to VigIA > AI Score to check your AI Visibility Score
- View crawler analytics in VigIA > Analytics
- Configure blocking rules, llms.txt, markdown, and JSON-LD in VigIA > Extras
Frequently asked questions
What is the AI Visibility Score?
The AI Visibility Score is a 100-point rating system that measures how well your site is prepared for AI crawlers and AI-powered search. It checks 20 signals across 5 categories: access and discovery, structured data, content structure, AI interaction, and performance. You get a letter grade (A+ to F) and specific recommendations to improve.
Does this plugin slow down my site?
No. VigIA adds minimal overhead by checking the User-Agent string on each request. The check is very fast and only writes to the database when an AI crawler is detected.
What’s the difference between robots.txt blocking and PHP blocking?
Robots.txt is advisory – crawlers should respect it but may choose to ignore it. PHP blocking returns a 403 Forbidden response, effectively preventing access regardless of whether the crawler respects robots.txt.
Will blocking crawlers affect my SEO?
Blocking AI training crawlers (like GPTBot or ClaudeBot) will not affect traditional search engine rankings. However, blocking AI search crawlers might affect how your content appears in AI-powered search results.
What is Markdown for Agents?
Markdown for Agents is a standard for serving web content as clean markdown to AI agents. Instead of processing full HTML, agents receive lightweight markdown with structured metadata. VigIA supports both dedicated .md URLs and Accept: text/markdown content negotiation. Enable it in VigIA > Extras > Markdown for Agents. This feature also covers taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products. Term archives include the term description, the list of child terms in hierarchical taxonomies and an excerpt of the latest entries…
Which content types does the activity table classify?
VigIA classifies each crawler hit into one of these buckets, indexed in the database so filters and CSV exports are instant: Home (the / path), Post, Page, Product, any other public custom post type, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File (PDFs, images, downloads), Admin/login attempt (/wp-admin, wp-login.php — useful to spot bots probing the admin), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other.
Can I add custom crawlers to monitor?
Yes! In the main analytics page, scroll down to “Custom crawlers” and add your own User-Agent patterns to track.
Where is the data stored?
All data is stored in your WordPress database in a custom table (wp_vigia_visits). No data leaves your server.
What is llms.txt?
The llms.txt file is a standard for helping AI systems understand your website’s content and structure. It provides a machine-readable overview of your site that AI can use to better represent your content. Learn more at llmstxt.org.
Which SEO plugins are supported for noindex detection?
VigIA supports automatic noindex detection from: Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer.
What is the Abilities API?
The Abilities API is a new feature in WordPress 6.9 that allows plugins to expose their functionality in a standardized way. This enables AI agents, automation tools, and external systems to discover and use plugin features programmatically. VigIA implements 9 abilities for analytics, blocking, and robots.txt management.
How do I connect Claude Desktop?
Save the JSON block from Quick Connect as claude_desktop_config.json in your user Library (this is not the system Library at the root of the disk): macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json Linux: ~/.config/Claude/claude_desktop_config.json On macOS, the easiest way to reach the folder is to open Finder, press ⌘ Shift G, paste ~/Library/Application Support/Claude/ and hit Enter. On Windows, press Win+R and run %APPDATA%\Claude. Important: Claude Desktop only speaks stdio to local processes, so the snippet does…
How do I add VigIA to an MCP config file that already exists?
If your claude_desktop_config.json or ~/.cursor/mcp.json already exists, do not paste the full Quick Connect block on top of it. Pasting on top discards everything else (preferences, other MCP servers) and the app will start with defaults. Always make a backup of the file first. Then open it with any text editor that preserves JSON. There are two scenarios. Scenario 1 — the file has content but no mcpServers block yet. This is common when you have used Claude Desktop before but never configured MCP servers. The file might look like this: { "preferences": { "menuBarEnabled": false, "..."…
Can I use an MCP client other than Claude Code, Cursor or Claude Desktop?
Most MCP clients accept HTTP transport with a custom Authorization header. The Quick Connect panel exposes the two raw values you need — the server URL and the Authorization header — so you can drop them into whatever configuration format your client expects. Browser-only assistants without an MCP client (AI Studio, ChatGPT web) cannot connect. They need a desktop or CLI client that speaks MCP over HTTP.
What does JSON-LD do?
JSON-LD (JavaScript Object Notation for Linked Data) is structured data that helps search engines and AI systems understand your site identity and content. VigIA generates two types of JSON-LD: Site Identity (WebSite + Organization/Person schema with social profiles) and AI Discovery (ReadAction pointers to your llms.txt and Markdown for Agents endpoints). This makes your AI-ready content discoverable through structured signals. Enable it in VigIA > Extras > JSON-LD.
Changelog
Fixes a stale rewrite rule that could loop redirects when handing Markdown to Visibility, non-Latin post, page and category addresses resolving to the wrong content, and a live script tag surviving in the site name.
2.6.6
Fixes a stale rewrite rule that could loop redirects when handing Markdown to Visibility, non-Latin post, page and category addresses resolving to the wrong content, and a live script tag surviving in the site name.
- Improved: The Markdown-for-agents description in the JSON-LD now uses the same wording as the Visibility sibling, so an AI agent reading either plugin’s structured data sees one consistent claim.
- Fix: The
.mdrewrite rule stayed registered after VigIA started deferring Markdown for agents to the Visibility sibling, because nothing regenerated it when that hand-over began. Combined with a request the sibling could not resolve either, the stale rule could turn into a redirect loop on a nonexistent.mdaddress. VigIA now notices the hand-over on every request and flushes the rule once, on either side of it, and also flushes on deactivation. - Fix: A tag-shaped string with an unpaired attribute quote, such as an
<a href="javascript:...>with no closing quote, survived the tag-stripping pass shared by llms.txt, llms-full.txt, the Markdown documents, and the site name and tagline, leaving a live tag in a file nothing renders as HTML. - Fix: The site name and tagline were decoded but not cleaned afterwards, so a script tag typed into either field, something a multisite sub-site administrator can do without full HTML permission, came back live everywhere they are reused: llms.txt, the Markdown documents, JSON-LD and report emails.
- Fix: A post, page or category with a non-Latin address (Cyrillic, Greek, Arabic, CJK) served the wrong Markdown document or a 404 instead of its own: a child page served its parent, a single-word slug 404’d, and a category never resolved. The address was being stripped of the very encoding a non-Latin slug is made of before VigIA tried to match it. Crawler visit logs for these addresses also recorded the path with the whole non-Latin segment missing; both are now recorded and matched correctly, and shown decoded in the crawler activity table and in report emails.
2.6.5
llms.txt and llms-full.txt now come out as clean plain text: no byte order mark at the start, no HTML entities in titles, and page summaries that no longer weld a heading to the paragraph under it.
- Improved: Both files are now built in the language of the site, not in the language the administrator reads wp-admin in. The section headings are the names WordPress gives your content types, so on a Spanish site generated from an English admin they used to come out as Posts and Pages.
- Improved: The JSON-LD preview in the settings screen now escapes angle brackets when it hands the site name to the browser. Nothing changes on screen; it is what allows the site name to be decoded everywhere else without opening a way to close the script tag from the site title.
- Fix: llms.txt and llms-full.txt began with a UTF-8 byte order mark, three bytes written on purpose so editors would detect the encoding. UTF-8 needs no mark, and those bytes are content: the first heading was no longer the first thing in the file, and a strict Markdown parser read it as a paragraph instead of a title. Both files are now written without it, and a mark arriving inside the content is stripped.
- Fix: Titles came out with HTML entities in them, so a post called Bull&Bear was listed as Bull&Bear while its own summary, a few words later, showed the ampersand correctly. Nothing renders these files as HTML, so the code was what an agent read. Titles, term names, authors and the body of llms-full.txt are now decoded, in the index, in llms-full.txt and in the Markdown documents and their frontmatter.
- Fix: The summary of a page with no hand-written excerpt welded its blocks together, so a heading ran straight into the paragraph below it and read as one broken sentence. The markup was carrying that full stop and stripping the tags threw it away. Block boundaries are now kept as sentence breaks, in llms.txt and in the description of the Markdown documents.
- Fix: The page assigned as Posts page in Settings > Reading was listed with neither a summary nor a Markdown link, the only entry in the file missing both. WordPress shows the blog loop there and never renders that page own content, which is usually empty. It is now described as the blog index.
- Fix: The site name and the tagline came out escaped, as WordPress stores them that way, so a site called Musee d'Art appeared like that in the heading of both files, in the JSON-LD name, and in the subject of the report emails. All of them now show the name as its owner typed it.
- Fix: A summary was cut by bytes rather than by characters, so the cut could land in the middle of an accented letter and write an invalid byte into the file.
- Fix: A summary that contained a comparison written without a space, such as 5<10, lost everything after it. The character was stored as an entity and decoding it back handed the rest of the line to a tag that never closed. This showed in the description of the Markdown documents, and it now keeps the whole text while still taking out anything shaped like a tag.
- Fix: The body of a Markdown document carried through any HTML that had been stored as an entity, so a script tag written by someone able to publish arrived as a live tag in a document an agent may render. It now goes through the same filter as the summaries, in the text and in list items. Fenced code blocks and inline code are left exactly as they were: HTML there is what the page is about, not markup, and nothing renders it.
2.6.4
- Improved: The bundled WordPress MCP Adapter is updated to the current upstream release. There is nothing to install: it ships inside the plugin, as always.
- Improved: The MCP server now refuses to start when the adapter that ends up loaded no longer takes the permission callback that guards the endpoint, rather than letting it fall back to the adapter own default, which any subscriber meets. No adapter in circulation behaves that way, so nothing changes today.
- Fix: VigIA clashed with other plugins that bundle the same MCP Adapter, such as the standalone MCP Adapter plugin. The log filled with Constant WP_MCP_DIR already defined and Constant WP_MCP_VERSION already defined, and the site went down with a fatal Cannot redeclare class WP\MCP\Autoloader when the other copy loaded first. VigIA no longer runs the adapter standalone plugin file, which is what declared those names, and starts the classes directly, the same way WooCommerce, WP Rocket and Elementor do.
2.6.3
- Improved: The MCP endpoint now asks for the same capability as the tools it exposes. It was left at the default of the bundled adapter, which any subscriber meets, so a logged-in user with no rights over the site could reach the endpoint and list the available tools. Running any of them was never possible, because all nine ask on their own for the capability to manage options, and that has not changed. A vigia_mcp_transport_capability filter is there for an install that needs a different bar.
2.6.2
- Improved: The Markdown responses now carry an X-Content-Type-Options: nosniff header, so a browser cannot second-guess their content type and decide to treat them as HTML.
- Fix: The content search in the LLMs.txt generator did not escape post titles correctly before listing the results, so a title containing quotes could break out of an HTML attribute and run script in the browser of the administrator running the search. Titles come from anyone who can publish, the Author role included. The escaping function now encodes quotes, the same way the rest of the plugin already did.
- Fix: On multisite, robots.txt, llms.txt and llms-full.txt sit at the network root and are one set of files for every site in the network, yet any subsite administrator could rewrite them. Only the main site writes them now. Subsites keep their own rules and keep serving them through the virtual robots.txt, which is per site.
- Fix: Dismissing the activation notice checked that the request came from a page of the plugin, but not that whoever sent it was allowed to change a site option. It now checks the capability like every other handler does.
2.6.1
- Improved: The Markdown version of an entry is built once and kept, instead of being converted from scratch on every request. On a 55 KB entry the response went from 74 to 22 milliseconds. It is rebuilt as soon as the entry changes, or a term whose document lists it.
- Improved: A Markdown response may now be reused for an hour, where it used to tell every agent and proxy not to store it at all. The document is the same one for whoever asks, built as a logged-out visitor, so there was nothing to protect by refusing to cache it. On a site with crawler blocks configured it is marked private instead, so a cache in front of the site never gets to answer for a crawler your site would have turned away.
- Improved: The MCP tools now tell the client what each of them does to your site. The five that read are marked read-only, and of the four that change something, blocking a crawler and adding a Disallow rule are marked as additive, while unblocking a crawler and removing a rule are marked as destructive. All nine looked alike until now, so asking for crawler statistics got the same approval prompt as blocking a crawler in Claude Desktop, Claude Code or Cursor.
- Improved: The bundled WordPress MCP Adapter is updated from 0.5.0 to 0.6.1, along with the php-mcp-schema library it depends on. There is nothing to install: both ship inside the plugin, as always.
- Fix: A page that also answers in Markdown now says so on its HTML response too, with a Vary: Accept header. Without it a shared cache, a CDN or a proxy, stores the HTML with no idea the address has a second form, and can later hand that HTML to an agent asking for Markdown. This covers the HTML WordPress generates, not what a page cache serves straight from disk, and Cloudflare ignores Vary on HTML, where the equivalent is a Cache Rule.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best VigIA alternatives
All AI plugins →
FAQ
VigIA: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 28, 2026
Is VigIA free?
Yes. VigIA is free to download and use from the official WordPress.org plugin directory.
Is VigIA safe to use in 2026?
Yes — VigIA is a safe, well-maintained plugin to use in 2026. It runs on 1K+ sites, is rated 5/5 and was last updated 1 week ago, and scores 86/100 on our health check.
How many websites use VigIA?
VigIA is active on 1K+ WordPress websites and has been downloaded 32,385 times since it launched in January 2026. It was downloaded 5,843 times in the last 30 days.
Does VigIA work with WordPress 7.1?
Yes. The developer has tested VigIA up to WordPress 7.1.2, the latest release. It requires WordPress 6.9 or newer.
What PHP version does VigIA need?
VigIA requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was VigIA last updated?
The latest version, 2.6.6, was released on September 18, 2026 (1 week ago).
Who makes VigIA?
VigIA is developed and maintained by Fernando Tellado.
What are the best alternatives to VigIA?
The most popular alternatives to VigIA are Elementor Website Builder (10M+ installs), All in One SEO (2M+ installs) and AI Agent by SiteGround (1M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
