VigIA - AI Visibility, Analytics & Control
| 开发者 |
fernandot
ayudawp |
|---|---|
| 更新时间 | 2026年4月29日 17:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- 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 55+ others)
- Provides detailed analytics with charts, statistics, and exportable reports
- 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 individual posts and pages (Markdown for Agents standard)
- Generates JSON-LD structured data with Site Identity and AI Discovery signals
- Exposes abilities for AI agents and automation tools (WordPress 6.9+)
- 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
- AI Share & Summarize integration: see share button clicks per page
- Recent activity log with filters and paginated navigation
- Period comparison functionality
- CSV export 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 individual posts/pages as optimized markdown for AI agents
- Dedicated .md URL endpoints (e.g., /your-post.md)
- Accept: text/markdown content negotiation
- Discoverability via link headers and HTML alternate tags
- YAML frontmatter with title, date, author, categories, tags, and more
- Respects blocking rules (blocked crawlers get 403)
- Respects LLMs.txt exclusion filters
- Analytics integration: tracks markdown requests per crawler
- X-Markdown-Tokens response header
- 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, and The SEO Framework 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
- OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User
- Anthropic: ClaudeBot, Claude-Web, Claude-SearchBot
- Google: Google-Extended, GoogleOther, Gemini-Deep-Research
- Perplexity: PerplexityBot, Perplexity-User
- Meta: Meta-ExternalAgent, FacebookBot
- Microsoft: BingBot
- ByteDance: Bytespider
- Amazon: Amazonbot
- Apple: Applebot-Extended
- And many more...
安装:
- 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
屏幕截图:
常见问题:
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.
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, and The SEO Framework.
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.
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.
更新日志:
- Fix: Fatal error "Cannot redeclare WP\MCP\constants()" when both VigIA and the standalone
mcp-adapterplugin are active. VigIA now skips its bundled adapter bootstrap if the standalone copy has already been loaded
- NEW: One-click MCP setup. The MCP Adapter and php-mcp-schema dependencies now ship bundled inside the plugin, so the server is active right after install — no
composer installand no terminal required - NEW: "Quick connect" panel in VigIA > Extras > MCP that generates a dedicated
VigIA MCPApplication Password and renders ready-to-paste connection commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) that fits any other MCP client (Codex CLI, Continue, Cline, Antigravity, Zed, etc.) - NEW: Safe JSON merger for Cursor and Claude Desktop. Paste your current config file, the plugin parses it, splices VigIA into
mcpServerspreserving everything else (preferences, other servers) and returns a valid file ready to save back, with no manual comma juggling - NEW: Detection and revocation flow for an existing
VigIA MCPApplication Password directly from the MCP tab - NEW: "What can I ask my AI now?" section in the MCP tab with example prompts so users immediately see what the connection unlocks
- NEW: Read-only mode is now a one-click toggle in the MCP tab (option
vigia_mcp_read_only). Thevigia_can_write_via_abilitiesfilter still works for developers who prefer to force it from code and takes precedence over the toggle - Changed: Claude Desktop snippet now launches
mcp-remotevianpxas a stdio-to-HTTP bridge (the only way Claude Desktop can currently talk to a remote HTTP MCP server). Requires Node.js installed on the machine. Claude Code and Cursor speak HTTP MCP natively and need no bridge - Changed: Manual setup snippets moved into a collapsed "Manual setup (advanced)" block to avoid competing with Quick connect; inactive-server message now references a missing
vendor/directory instead of a missing Composer install - Fix:
vigia/get-blocked-items,vigia/get-top-pagesandvigia/block-crawlerabilities were calling non-existent methods and returned a 500 when invoked. They now resolve correctly and the output surfaces fields that were being discarded (namefor blocked items,crawler_countfor top pages)
- NEW: Native MCP server that exposes VigIA abilities at /wp-json/vigia/v1/mcp through the official WordPress MCP Adapter, ready to plug into Claude Code, Cursor or Claude Desktop
- NEW: MCP tab in VigIA > Extras with adapter status, endpoint URL, Application Password setup, connection snippets for Claude Code, Cursor and Claude Desktop, list of exposed abilities and the read-only mode snippet
- NEW: Filter
vigia_can_write_via_abilitiesto disable mutating abilities (block, unblock, robots changes) while keeping read-only abilities working - useful when granting MCP access with Application Passwords - Fix:
vigia/block-crawlernow validates IP addresses with FILTER_VALIDATE_IP, matching the behavior of the AJAX blocking handler - Performance: results of
vigia/get-crawler-stats,vigia/get-top-crawlersandvigia/get-top-pagesare now cached for 5 minutes via transients to keep MCP clients from hammering the database - Changed: Version history moved to a dedicated changelog.txt file served from the plugin's public SVN, keeping readme.txt focused on the current release
- Dev: introduced composer.json declaring the optional
wordpress/mcp-adapterdependency
- Fix: Removed stray whitespace before PHP opening tag in class-visibility-analyzer.php that caused "headers already sent" warnings and could break other plugins functionality
- Fixed: AI Visibility Analyzer now detects sitemaps.xml (plural) in addition to sitemap.xml, sitemap_index.xml and wp-sitemap.xml For older changelog entries, please check the changelog.txt file