Infy SEO – Image SEO Optimizer
Rank higher on Google Images without touching your media library by hand. Image SEO Optimizer writes WCAG-compliant alt text, SEO-friendly filenames and titles for thousands of WordPress images at once — using your choice of Gemini, Claude or GPT. Rename safely: every filename change is auto-301-redirected. Looking for more features? Check out Image SEO Optimizer Pro. Why Image SEO Optimizer? Images are crucial for SEO, but manually optimizing hundreds of images is time-consuming. Our plugin solves this by: Saving Hours of Manual Work – AI optimizes images in seconds Improving SEO Rankings – Search engines love properly optimized images Enhancing Accessibility – AI-generated alt text helps screen readers Smart Filename Management – SEO-friendly filenames with automatic URL updates across page builders Key Features AI-Powered Metadata Generation Generate SEO-friendly filenames automatically Create descriptive alt text (accessibility + SEO) Generate optimized image titles Extract relevant keywords Multiple AI Providers Google Gemini – Gemini 3.1 Flash-Lite, Gemini 3.5 Flash-Lite OpenAI – GPT-4.1 mini Anthropic Claude – Claude 4.5 Haiku Switch between providers anytime Use your own API keys (full control over costs) Or, on WordPress 7.0+, use WordPress AI Connectors (Settings → Connectors) — no plugin API key required Page Builder Integration Gutenberg – Full WordPress Block Editor support Elementor – Complete integration with automatic URL updates WPBakery – Seamless integration Visual Composer – Full compatibility Uncode – Full compatibility Divi – Full support across page content, Divi Library, and Theme Builder Automatic URL updates when renaming files No broken images after filename changes SEO Features Real-time SEO score calculation (0-100 scale) 6-component scoring algorithm (100 points total) Detailed score breakdown by field Visual indicators for optimization status Track optimization progress across your media library Smart Dashboard Visual media library overview See optimization status at a glance Filter by optimized/unoptimized images Search and sort capabilities Image usage tracking (where images are used) Usage Tracking & Analytics Monitor API usage by provider Track costs and requests Daily/monthly usage statistics Export usage data Visual charts and graphs Cost estimation tools 301 Redirect Protection Automatic 301 redirects when images are renamed Preserves SEO value — no broken links from search engines, social shares, or external sites Covers all image sizes (thumbnails, crops, originals) Smart redirect chain resolution (A→B→C becomes A→C) Hit tracking to monitor redirect usage Configurable expiry (6, 12, 24 months, or never) Zero impact on normal page loads — only activates for old image URLs Advanced Features 60+ Languages – Generate metadata in any supported language Changelog Tracking – Complete audit trail of all changes Inline Editing – Edit AI suggestions before saving Encrypted API Keys – Secure storage using WordPress salts Rate Limiting – Prevent excessive API usage Developer-Friendly REST API (infyp/v1) — optimize images and manage settings programmatically 38 action hooks for workflow integration 80 filter hooks for customization Clean, documented codebase WordPress Coding Standards compliant Extensible architecture Well-documented API How It Works Install & Activate – Quick installation from WordPress.org Add API Key – Add at least one AI provider API key Configure Settings – Choose your preferred AI model and language Optimize Images – Single-click optimization or bulk operations Monitor Results – Track SEO scores and usage statistics Perfect For Bloggers – Optimize featured images and content automatically Photographers – Proper image descriptions at scale Agencies – Manage multiple client sites efficiently Content Creators – Focus on content, not manual image optimization Anyone with Images – Every WordPress site needs image SEO What Makes Us Different Unlike basic image SEO plugins, Image SEO Optimizer: Actually “Sees” Images – AI vision models understand image content Natural Descriptions – Not keyword-stuffed robotic text Context-Aware – Understands your content and brand Multilingual Native – True multilingual support, not translations Smart URL Updates – Prevents broken images across page builders 301 Redirect Protection – Automatic redirects preserve SEO when renaming files Full Transparency – You own your API keys, control your costs Privacy & External Services This plugin connects to third-party AI services that you configure with your own API keys. Images are sent to these services for analysis and metadata generation: Google Gemini API * Service: Google AI image analysis * Privacy Policy: https://policies.google.com/privacy * Terms of Service: https://policies.google.com/terms * When used: When you select Gemini as your AI provider and optimize images OpenAI API * Service: OpenAI image analysis * Privacy Policy: https://openai.com/privacy * Terms of Service: https://openai.com/terms * When used: When you select OpenAI as your AI provider and optimize images Anthropic Claude API * Service: Anthropic Claude image analysis * Privacy Policy: https://www.anthropic.com/privacy * Terms of Service: https://www.anthropic.com/terms * When used: When you select Claude as your AI provider and optimize images Important Notes: * Images are ONLY sent to the service you configure * You use your own API keys (you control the relationship with the provider) * No automatic data collection by plugin authors * No tracking or analytics without your explicit consent * You can review each provider’s privacy policy before using their service Optional Newsletter & Telemetry (Opt-in Only) During the setup wizard, you can optionally subscribe to our newsletter. If you choose to opt in, we collect the following non-personal site information to help improve our plugin: Environment Data: * WordPress version, PHP version, MySQL version * Server software, memory limit * Site URL, locale, timezone * Multisite status, WP_DEBUG status Plugin & Theme Data: * Image SEO Optimizer plugin version * Active theme name and version * List of active plugins (names only) * Detection of common plugins (WooCommerce, Yoast, Rank Math, Elementor) Content Statistics: * Total media library count * Image count (images only) * Post, page, and product counts User Data (from your WordPress account): * Email address (for newsletter delivery) * Display name * WordPress user role This data is: * Only collected if you explicitly check the opt-in checkbox * Sent to: https://infypress.com/wp-json/ai-products/v1/newsletter/subscribe * Used to improve our plugin and send relevant updates * Never sold to third parties * You can unsubscribe at any time For more details, see our Privacy Policy. Google Search Console Integration This plugin includes an optional Google Search Console integration that connects to several Google services: Google OAuth 2.0 — Used to authorize access to your Google Search Console account. Endpoints: accounts.google.com, oauth2.googleapis.com Data sent: OAuth authorization codes and refresh tokens for token exchange When used: When you connect or reconnect to Google Search Console, and periodically to refresh access tokens Privacy Policy: https://policies.google.com/privacy Terms of Service: https://policies.google.com/terms Google Search Console API — Used to retrieve your site’s search performance data, URL inspection results, and sitemap information. Endpoints: googleapis.com/webmasters/v3, searchconsole.googleapis.com/v1 Data sent: OAuth access token, your site URL, date ranges, and URLs for inspection When used: When you view Search Console data within the plugin dashboard Privacy Policy: https://policies.google.com/privacy Terms of Service: https://policies.google.com/terms InfyPress OAuth Proxy — When using the “Quick Connect” method to connect Google Search Console, the authorization flow is routed through our proxy server. This proxy securely holds the Google OAuth client secret so it is never shipped in the plugin code. Endpoint: infypress.com/wp-json/ai-products/v1/gsc Data sent: Proxy authorization code, refresh token, and your site URL When used: Only when you use the “Quick Connect” method for Google Search Console (not when using custom credentials) Privacy Policy: https://infypress.com/privacy/ Developer Information Image SEO Optimizer provides 118 hooks (38 actions + 80 filters) for developers to extend its functionality. Below are the most commonly used hooks. For the complete reference, see our documentation: Actions Reference Filters Reference Key Hooks Filters: infyp_allowed_post_types – Filter which public post types are shown in the image list. Default: all public post types registered in WordPress. infyp_image_context – Add custom context to AI prompts (e.g. product data). Parameters: $prompt_addon, $image_id, $context_type. infyp_supported_mime_types – Filter supported image MIME types. Default: ['image/jpeg', 'image/png', 'image/webp', 'image/gif']. infyp_register_pagebuilder_adapters – Register additional page builder adapters. Parameters: $adapters. infyp_image_usage_post_ids – Find additional post IDs where an image is used. Parameters: $post_ids, $image_id, $image_url. infyp_table_columns_after_title – Add custom columns to the image list table. Parameters: $columns. Actions: infyp_after_image_upload – Fires after a new image is uploaded and processed. Parameters: $attachment_id, $metadata. infyp_filename_updated – Fires after filename URL references are updated across content. Parameters: $post_id, $url_map, $results. infyp_before_settings_cards / infyp_after_settings_cards – Add custom cards to the Settings page. Code Example // Customize which post types appear in the image filter add_filter( 'infyp_allowed_post_types', function( $types ) { // Remove a type you don't want unset( $types['custom_type'] ); return $types; } ); // Add custom context to AI prompts add_filter( 'infyp_image_context', function( $context, $image_id, $type ) { $parent_id = wp_get_post_parent_id( $image_id ); if ( $parent_id && get_post_type( $parent_id ) === 'portfolio' ) { $context .= "\nThis image is from a portfolio project."; } return $context; }, 10, 3 ); Requirements WordPress 6.1 or higher PHP 8.0 or higher MySQL 5.7 or higher At least one AI provider API key (OpenAI, Google Gemini, or Anthropic Claude) — or, on WordPress 7.0+, an AI connector configured under Settings → Connectors 128MB PHP memory limit recommended cURL or similar for API requests Support & Links Documentation WordPress Support Forum Feature Requests Report Bugs
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.