AI Block Editor – Gutenberg Block Generator & AI Assistant vs VigIA – AI Visibility, Analytics & Control

AI Block Editor adds a Gutenberg blocks assistant inside the WordPress editor. Describe what you want to add or change, and AI Editor will place, arrange, and update WordPress blocks directly in the editor. Use it for complex block layouts or simple edits. It supports the latest OpenAI models and lets you use your own API key. When your theme uses theme.json, AI Editor can follow your global styles, presets, and design tokens like colors, typography, spacing, and layout so generated blocks match your site’s design system. Major updates released in May 2026: theme.json style matching, selected block editing, and newer AI models with reasoning controls. Features Natural language block creation: Describe your desired content in plain language and the AI will handle the rest. Core Gutenberg blocks: AI Editor can use core Gutenberg blocks to create complete page sections and complex layouts, not just add single blocks one at a time. Selected block editing: Select one or more blocks in Gutenberg and ask AI Editor to update the selected content or layout. Custom block editing: Custom and third-party blocks can be edited after you add and select them. AI Editor uses the markup it can see for the selected block, so review the result because custom blocks may have private fields, dynamic rendering, or plugin-specific rules the AI cannot fully infer. Existing content lookup (WordPress 6.9+): AI Editor can look up existing WordPress posts, pages, and public custom post types for context, then use that text while helping you create or edit content. Theme-aware output: For themes that use theme.json, AI Editor can use your theme’s presets and editor settings to keep generated layouts consistent with your site’s colors, spacing, typography, and other design styles. Abilities API support: On WordPress 6.9+, connect custom WordPress Abilities API features to AI Editor so it can use site-specific data or actions while helping in the editor. Resizable sidebar: Drag the left edge of the AI Editor sidebar to make the chat panel wider. GPT model selection: Choose from the GPT models supported by AI Editor and available to your OpenAI account. Reasoning effort controls: Choose how much reasoning the model should use for faster simple edits or more careful complex layout work. Conversation context controls: Limit how many recent chat messages are sent with each request. Prompt caching: AI Editor keeps repeated system instructions stable so OpenAI prompt caching can reuse shared context when available, helping monitor API usage and reduce repeated input processing. Theme compatibility check: Review whether the active theme is a good fit for AI Editor’s Gutenberg and theme style workflow. BYOK: Use your own OpenAI API key. Language translation: Multilingual support. Prompt Examples “Add this article as a magazine-style layout using blocks: (paste article here).” “Create a layout for an About Us page, including sections for a mission statement, team members, and contact.” “Add 3 columns, each with a pricing plan.” “Create a table comparing the caffeine content of popular drinks.” “Rewrite this testimonial block to sound more concise.” “Update the selected columns for better balance.” Getting The Best Results Quickly add content blocks: Ask AI Editor to add headings, sections, buttons, lists, tables, columns, and other core blocks for your content. Turn full copy into blocks: Paste a full page draft or section copy and let AI Editor structure it into blocks. Use existing site content: Ask AI Editor to work from existing posts, pages, or custom post types when the request needs site context. With lower models or no reasoning, be explicit, such as “use the current page content as context” or “find posts about pricing and add a summary section.” Choose settings for the task: Select an available model and adjust reasoning effort based on the complexity of the requested layout or edit. Select the right amount of content: If the change depends on a parent layout, columns, group spacing, or surrounding section structure, select the whole relevant block or section and say what you want changed. Use narrow selections for simple edits: If you only need a specific text, button, heading, or single block changed, select just that block and give a direct instruction. Settings Navigate to Settings -> AI Editor to configure the plugin. OpenAI API Key: Add your own OpenAI API key. Requests are sent from your WordPress site to OpenAI. GPT Model: Choose the model AI Editor should use. Reasoning Effort: Choose none, low, medium, or high. Lower values are faster for simple edits; higher values can help with larger layouts or more careful restructuring but may take longer and use more tokens. Theme Style Context For AI: A short style note used as design direction. AI Editor can rewrite the active theme description with AI. Raw theme presets are handled separately, so this field should stay short and human-readable. Limit Conversation Context Sent To OpenAI: Turn on/off trimming of older chat messages before sending a new request. Max Messages In Conversation Context: Set how many recent messages are kept when conversation context trimming is enabled. The default is 50. Theme Compatibility For AI Editor: Run a compatibility check for the active theme. It reviews Gutenberg support, block theme signals, editor style support, and available theme presets so you can spot where manual cleanup may be needed. Note: AI Editor is powered by OpenAI’s GPT technology. For more information on the data handling and privacy aspects, please refer to OpenAI’s Privacy Policy and Terms of Service. Connect Custom Abilities On WordPress 6.9+, developers can connect custom abilities registered with the WordPress Abilities API to AI Editor. If your plugin or theme registers a custom ability, add an AI Editor config to the ability meta. Example: 'meta' => array( 'ai_editor' => array( 'action_name' => 'get_product_details', 'description' => 'Use this when the user asks for current product details from WooCommerce.', ), ) AI Editor will only use abilities that explicitly opt in. Keep ability results focused and avoid returning large private datasets or unrelated site data. Requirements PHP 7.0+ is recommended, WordPress 5.8+, with Gutenberg active. An OpenAI API key is required.

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.