ActionPanel AI – Site Agent & Troubleshooter vs VigIA – AI Visibility, Analytics & Control

ActionPanel AI is an AI assistant built into wp-admin that can create and edit WordPress content, troubleshoot problems, and carry out maintenance — all from a chat panel inside your dashboard. Instead of switching between the block editor, Site Health, plugin screens, settings pages, and docs, you describe what you want in plain English. ActionPanel AI reads the relevant parts of your site, proposes changes, and — with your approval — applies them. Create and manage content Posts and pages: Draft new posts and pages, rewrite or extend existing content, and edit block content directly. New drafts and edits are yours to review before anything goes live. Custom post types and fields: Create and update custom post types and custom fields on sites using Advanced Custom Fields (ACF) or JetEngine. Menus, categories, and tags: Build and reorganize navigation menus and manage categories, tags, and other taxonomy terms. Media: Add and organize items in the media library and set featured images. You can also share an image in chat for ActionPanel AI to use while it works. SEO: Update SEO titles, descriptions, canonical URLs, and social (Open Graph) metadata through your active SEO plugin — Yoast SEO, Rank Math, or All in One SEO. Site design: Adjust block templates, template parts, and global styles, or apply custom CSS to specific pages. Cloning: Duplicate an existing post or page as a draft to use as a starting point. Troubleshoot and maintain Site troubleshooting: Ask what might be broken, why a page is returning an error, why links are failing, or what to check after a site change. Performance checks: Review plugin bloat, autoloaded options, homepage assets, scheduled task backlogs, and other common causes of slow WordPress sites. Plugin and theme review: Find outdated, duplicated, inactive, or potentially risky plugins and themes, then get plain-language next steps. Site Health summaries: Turn WordPress Site Health, REST/runtime details, and maintenance signals into a prioritized explanation of what matters. WooCommerce checks: Review common store setup areas such as checkout pages, payment gateways, shipping zones, and basic configuration. Debug log help: When log reads are enabled, use sanitized excerpts from a readable WordPress debug log file to help explain errors and warnings. Guided maintenance actions: When write operations are enabled, ActionPanel AI can propose supported maintenance actions — such as clearing caches, flushing rewrite rules, running scheduled tasks, and updating allowlisted settings — and explain what they do before you approve them. Common tasks Use ActionPanel AI when you need to: Draft a new post or page or revise existing content. Update SEO titles and descriptions or fix metadata across your content. Build or reorganize a navigation menu, categories, or tags. Check whether a site is ready for plugin, theme, or WordPress core updates. Understand why a page, checkout, form, or permalink may not be working. Review plugin clutter and get a plain-English summary of Site Health and maintenance issues. Investigate slow pages without jumping between multiple admin screens. Built for wp-admin workflows ActionPanel AI lives in the WordPress dashboard, keeps recent conversations available in a sidebar, and includes starter prompts for common content, maintenance, and troubleshooting tasks. It is designed for site owners, content creators, developers, agencies, and support teams who want faster help rather than spending hours in admin screens or documentation. Site context it can use To answer questions and make changes, ActionPanel AI can use selected WordPress context such as post and page content (including block content and custom fields), menus, categories and tags, media details, block templates, template parts, and global styles, along with plugin and theme details, Site Health results, REST/runtime information, scheduled tasks, performance signals, WooCommerce setup, same-site page checks, and approved debug log excerpts. Write operations are optional and turned off until you enable them. When enabled, they cover content and site changes (such as posts, pages, custom post types and fields, menus, taxonomy terms, media, SEO fields, templates, and global styles) as well as maintenance actions (such as clearing caches, flushing rewrite rules, running scheduled tasks, and updating allowlisted settings). You stay in control Admin-only access inside WordPress. Reads and writes can each be turned on or off in ActionPanel settings. Optional per-request approval before site data is shared. Optional read-only debug log sharing that can be turned off anytime. Live-impacting changes — publishing, editing, or deleting existing content, and maintenance actions — require explicit approval; safe draft-only writes may be approved automatically when that setting is enabled. External Services This plugin connects to an external service at https://api.actionpanelai.com. Plugin UI JavaScript/CSS assets are bundled locally in the plugin (not remote-loaded), and any external links shown in the UI are only opened through user-initiated navigation. Requests are sent when: An administrator allows WordPress to send requests to ActionPanel AI and uses chat, content, or diagnostic tools. The assistant reads site data or content needed to answer a question or make a requested change. An administrator asks the assistant to create or edit content and, where required, approves the change. Account/login features are used. Optional log reads are enabled to read sanitized excerpts from a readable WordPress debug log file when WP_DEBUG is enabled and WP_DEBUG_LOG is set to true or an absolute file path. WordPress personal data export/erase tools are used for ActionPanel AI data. Data may include (depending on feature use): Chat messages. Images you attach in chat. Post and page content, including block content and custom fields, that the assistant reads or is asked to create or edit. Menu, taxonomy, media, template, template-part, and global-style data for content and design changes. SEO field values read from or written through your active SEO plugin. Site diagnostics/context. Site configuration summaries, including plugin/theme details, WordPress settings, REST/runtime, and performance diagnostics. Same-site diagnostic HTTP results, such as response status, selected headers, asset URLs, and redacted text previews from pages an administrator asks the assistant to inspect. Sanitized excerpts from a readable WordPress debug log file (only if enabled). Sampled or masked user/account metadata used for troubleshooting. Sanitized home-root server configuration snippets and drop-in metadata. Allowlisted theme or upload file metadata or text contents, plus plugin manifests, needed for troubleshooting. Session/auth metadata required for service operation. Email address and site URL for account and privacy workflows. Safeguards: External API calls are disabled by default on fresh installs until an administrator completes setup. Write operations are optional and disabled until an administrator enables them. “Per-Request Approval for Reads” can require a preview and approval before site data is shared. Log reads are optional, read-only, require WP_DEBUG plus WP_DEBUG_LOG set to true or an absolute debug log file path, and can be turned off at any time. AI initiated write operations require explicit approval before live changes are applied; only safe draft-only writes may be auto-approved, and only when that setting is enabled. Service policies: Privacy Policy: https://actionpanelai.com/privacy/ Terms of Service: https://actionpanelai.com/terms/ Privacy ActionPanel AI can send prompts and selected site context to external ActionPanel AI services when used. Depending on feature use, this can also include conversation history, images you attach in chat, post and page content (including block content and custom fields) that is read or edited, menu, taxonomy, media, template, and global-style data, SEO field values, configuration summaries, plugin/theme details, selected WordPress settings, sampled or masked user/account metadata, sanitized home-root server configuration snippets, plugin/drop-in metadata, and allowlisted theme or upload file metadata or contents needed for troubleshooting. Optional log sharing includes sanitized excerpts from a readable WordPress debug log file only when enabled. The plugin does not create, write, rotate, or relocate log files. Anonymous plugin session chat data is retained for up to 7 days before automatic deletion. Data Export and Erasure For account-linked data, WordPress Tools -> Export Personal Data and Tools -> Erase Personal Data can request site-scoped export/erase by email. The plugin exposes a public privacy-proof REST endpoint that returns only a challenge signature and site host; this lets ActionPanel AI verify site control before processing remote personal data export or erasure requests. Source Code For Bundled Assets The distributed JavaScript/CSS bundle in /build is generated from source included in this plugin package at: /assets-src/frontend Build/reproduction notes are included at: /assets-src/BUILD.md

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 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 crawlers vigia/get-top-pages – Get the most crawled pages on your site Blocking vigia/get-blocked-items – List all blocked crawlers and IP addresses vigia/block-crawler – Block a crawler by User-Agent pattern vigia/unblock-crawler – Remove an existing block Robots.txt vigia/get-robots-rules – Get current AI crawler rules in robots.txt vigia/add-robots-disallow – Add a Disallow directive for a crawler vigia/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? Official website WordPress support forum YouTube channel Documentation and tutorials 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.