Ariham SEOAgent
Ariham SEOAgent is a hands-free SEO growth engine for WordPress. It connects to Google Search Console and Google Analytics 4 to read real traffic and ranking data for every post on your site, then uses that data — optionally combined with Gemini or OpenAI — to detect problems, generate prioritised recommendations, and apply safe fixes automatically. Unlike traditional SEO plugins that show you a checklist to fill in, Ariham SEOAgent acts like a background analyst that never sleeps: it scores every page on a 0–100 SEO scale, surfaces the highest-impact opportunities first, and can apply safe metadata updates for you on a schedule — with full rollback if anything looks wrong. Connect your existing tools — Ariham SEOAgent enhances what you already have: Ariham SEOAgent reads and writes to the SEO plugins you already use. It does not replace them. Google Search Console — pulls real queries, impressions, clicks, average position, and CTR per post so recommendations are based on actual search performance, not guesses. Google Analytics 4 — pulls sessions, engagement rate, and average time-on-page to identify pages losing traffic or readers leaving quickly. Google Site Kit — if Site Kit is already installed and authorised, Ariham SEOAgent uses its connection bridge to access Search Console data without requiring a separate OAuth setup. Yoast SEO — reads and writes meta titles, descriptions, and focus keywords to Yoast’s fields. Rank Math — reads and writes meta and focus keywords to Rank Math’s meta keys. SmartCrawl — integrates with SmartCrawl’s redirect manager and meta fields. The SEO Framework — reads and writes to TSF’s post meta. AIOSEO & SEOPress — meta write support included. Redirection plugin — can create and manage 301 redirects through Redirection’s database when it is active. What it does on a daily basis: Fetches fresh Search Console and GA4 data for all published posts. Scores each post across seven SEO dimensions: metadata completeness, title/description optimisation opportunity, content depth, content freshness, search-intent alignment, internal linking, and image alt text. Detects six signals per post: missing meta, optimisation opportunity, thin content, content refresh needed, intent mismatch, and declining performance. Builds a prioritised queue of recommendations — each with a confidence score, a “safe vs risky” classification, and a before/after preview. In manual mode: presents the queue in the Pending Approvals admin screen for you to approve or dismiss one by one. In Autopilot mode: automatically applies recommendations classified as “safe” above a confidence threshold you configure, capped at a daily limit. Every applied change is logged with full before/after values and is one-click reversible from the Rollback Center. Core features: Real-data scoring — every decision is backed by actual Search Console and GA4 numbers, not keyword-density calculations. AI-powered suggestions — optional Gemini (Google AI) and OpenAI/OpenAI-compatible integrations generate keyword-rich meta titles, meta descriptions, and focus-keyword suggestions tuned to your existing ranking data. Autopilot with guardrails — safe-only auto-apply mode, configurable confidence floor, daily change limit, and instant rollback. You stay in control. Full audit trail — every recommendation, every applied fix, and every rollback is recorded in the Activity Log with timestamps, before/after values, confidence scores, and what triggered the change. Internal link engine — detects orphan pages and inserts contextual internal links to help distribute PageRank and reduce crawl depth. Schema injection — auto-injects Article, BlogPosting, FAQPage, HowTo, and BreadcrumbList JSON-LD structured data via wp_head. 404 monitoring and redirect management — logs 404s and creates 301 redirects through whichever redirect plugin you already have active. WP-CLI suite — 10 CLI subcommands for power users: analyze, optimize, report, rollback, fetch-gsc, fetch-ga4, score, opportunities, status, logs. Clean uninstall — removes every custom table, option, post meta key, transient, and scheduled event when uninstalled. Privacy and data handling: No data leaves your server until you explicitly connect a Google account. No remote call is made on activation. OAuth tokens and API keys are stored encrypted (AES-256-CBC) in your WordPress database. External Services This plugin communicates with the following third-party services only after you provide credentials and authorise the connection. No external call is made on plugin activation or on the front-end. Google APIs (required for core functionality) After you complete the Google OAuth flow, the plugin communicates with: accounts.google.com — OAuth 2.0 authorisation and token exchange oauth2.googleapis.com — Access-token refresh searchconsole.googleapis.com — Search Console query data (impressions, clicks, position, CTR) for your verified property analyticsdata.googleapis.com — GA4 sessions, engagement rate, and time-on-page analyticsadmin.googleapis.com — Listing your GA4 properties Google Privacy Policy | Google Terms of Service Google PageSpeed Insights (optional, opt-in) Disabled by default. When you turn on “Fetch Core Web Vitals” under Ariham SEOAgent → Settings, a weekly background job sends your published post URLs to www.googleapis.com/pagespeedonline to retrieve Core Web Vitals and Lighthouse scores. No PageSpeed request is ever made unless you explicitly enable this option. Google Privacy Policy | PageSpeed Insights API Terms Google Gemini AI (optional) When you save a Gemini API key, AI-generated meta suggestions are fetched from generativelanguage.googleapis.com. Gemini API Terms OpenAI / OpenAI-compatible endpoint (optional) When you configure an OpenAI API key, meta suggestions are fetched from api.openai.com (or a custom base URL you specify). This can point to any OpenAI-compatible provider. OpenAI Privacy Policy | OpenAI Terms of Use No user data is sent to any third-party service until you explicitly configure and activate that integration.
VigIA – AI Visibility, Analytics & Control
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 * Physical files at the site root, or served by WordPress when the root is not writable * On multisite, every site gets its own files, mapped domains included * 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) through the official MCP Adapter plugin. The server is off by default: turn it on in VigIA > Extras > MCP, where VigIA also offers to install MCP Adapter if the site does not have it. Requirements WordPress 6.9 or later (provides the Abilities API) The free MCP Adapter plugin. A site where another plugin already runs the adapter works too, and the MCP tab says which copy is in use Quick connect (recommended) Open VigIA > Extras > MCP, enable the MCP server 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-your-site-example https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD" Quick Connect names the server after the site (vigia-your-site-example), so the same client can hold several sites with VigIA. 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.
