VigIA – AI Visibility, Analytics & Control
by Fernando Tellado 5 (19 reviews)

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.

VigIA ranks #4,980 among WordPress.org plugins with 2,000+ active installations, is #135 of 2,168 in the Analytics category, a 5/5 rating from 19 reviews, and was last updated Oct 8, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v2.8.0 Current Version v2.8.0
Updated 3 weeks ago Last Update on 08 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#135 of 2,168 in Analytics Top 10% by installs Downloads +25.3% this week Actively maintained
View on WordPress.org
Rank
#4,980
— No change
Active Installs
2K+
+4%
KW Avg Position
25.4
0.4 worse
Downloads
38.2K
+257 today
Support Resolved
100%
— No change
Rating
100%
Review 5 out of 5
5 (19 reviews)

Next Milestone 3K

Total Progress 80.2%
2K+ 3K+
797
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 198 more installs to reach 3K+

Rank Changes

4,961 4,972 4,984 4,995 5,006 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
4,933 5,005 5,076 5,148 5,219 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Current #4,980
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 200 400 600 800 1K 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
0 200 400 600 800 1K 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
19 reviews
Overall 100%
5
19 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Support Threads Overview

Resolved
Unresolved
3
Total Threads
3
Resolved
0
Unresolved
100%
Resolution Rate

Security History

Source: WPVulnerability

No known vulnerabilities on record for VigIA. Checked 2 months ago.

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners who want to know how AI systems like ChatGPT, Claude, and Perplexity are accessing their content. It tracks and categorizes visits from 50+ AI crawlers so site owners can analyze trends and inform robots.txt decisions.

  • Detects 50+ AI crawlers
  • Visual analytics dashboard
  • Period comparison
  • Custom crawler patterns
  • CSV data export
  • Dashboard widget
  • Local data storage

Frequently Asked Questions

Common questions about VigIA – AI Visibility, Analytics & Control

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.
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.
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.
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.
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; product .md endpoints embed schema-like data (price, sale price, SKU, stock status, rating) directly in the YAML frontmatter.
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.
Yes! In the main analytics page, scroll down to "Custom crawlers" and add your own User-Agent patterns to track.
All data is stored in your WordPress database in a custom table (wp_vigia_visits). No data leaves your server.
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.
Yes. On a network each site keeps its llms.txt and llms-full.txt in its own uploads folder and WordPress serves them at that site's address, be it a subdomain, a subdirectory or a mapped domain. Generate them from VigIA > Extras > LLMs on each site. If the main site already has physical files at the network root, set its Delivery to Served by WordPress first: the web server answers a file in that folder on every domain of the network, ahead of each site's own. On a single site the files are physical files at the site root unless you choose Served by WordPress under Delivery, which is the option to pick when that folder is not writable.

Sign In / Register

You need to sign in or register to use this feature.