PMV Agency

<p><strong>AEO Engine</strong> is a complete optimization plugin for WordPress that covers <strong>SEO</strong>, <strong>AEO</strong> (Answer Engine Optimization), and <strong>GEO</strong> (Generative Engine Optimization). It generates structured data, meta tags, and AI-readable files to maximize your visibility across traditional search engines and AI-powered platforms like ChatGPT, Google AI Overviews, Perplexity, and Claude.</p>
<h4>What Makes AEO Engine Different?</h4>
<p>Unlike traditional SEO plugins, AEO Engine is built from the ground up to optimize your content for the AI era. It combines classic structured data with cutting-edge features like LLMs.txt generation and GEO optimizations.</p>
<h4>Key Features</h4>
<ul>
<li><strong>9 Schema Types (JSON-LD)</strong>: Organization, BlogPosting, BreadcrumbList, FAQPage, HowTo, WebSite + SearchAction, LocalBusiness, VideoObject, Product</li>
<li><strong>Auto-Detection</strong>: Automatically detects FAQ pairs, HowTo steps, and YouTube/Vimeo videos in your content</li>
<li><strong>LLMs.txt Generation</strong>: Creates /llms.txt and /llms-full.txt files following the llmstxt.org standard for AI crawlers</li>
<li><strong>Open Graph + Twitter Cards</strong>: Complete social media meta tags with conflict detection</li>
<li><strong>GEO Optimizations</strong>: SpeakableSpecification, quality indicators, and entity optimization</li>
<li><strong>Per-Post Controls</strong>: Meta box to disable/force schemas on individual posts</li>
<li><strong>Conflict Detection</strong>: Automatically detects Yoast, RankMath, AIOSEO, and other SEO plugins</li>
<li><strong>WooCommerce Ready</strong>: Enhanced Product schema with offers, ratings, and brand support</li>
<li><strong>Lightweight</strong>: No external dependencies, no custom database tables, minimal overhead</li>
<li><strong>Developer Friendly</strong>: Hooks and filters for every schema type</li>
</ul>
<h4>Schema Types Included</h4>
<ol>
<li><strong>Organization</strong> – Identifies your company/brand on the homepage</li>
<li><strong>BlogPosting / Article</strong> – Structured metadata for your articles and posts</li>
<li><strong>BreadcrumbList</strong> – Navigation breadcrumbs in search results</li>
<li><strong>FAQPage</strong> – Auto-detected FAQ pairs from heading + paragraph content</li>
<li><strong>HowTo</strong> – Auto-detected step-by-step instructions from ordered lists</li>
<li><strong>WebSite + SearchAction</strong> – Sitelinks search box on your homepage</li>
<li><strong>LocalBusiness</strong> – Complete business listing with address, hours, phone, and GPS coordinates</li>
<li><strong>VideoObject</strong> – Auto-detected YouTube and Vimeo embeds</li>
<li><strong>Product</strong> – WooCommerce products with price, availability, and ratings</li>
</ol>
<h4>LLMs.txt for AI Engines</h4>
<p>AEO Engine generates standard-compliant /llms.txt and /llms-full.txt files that help AI models (ChatGPT, Claude, Perplexity) better understand and cite your content. Features include:</p>
<ul>
<li>Automatic generation based on your published content</li>
<li>Configurable post types, ordering, and item limits</li>
<li>Per-post exclusion from LLMs.txt</li>
<li>1-hour smart caching with automatic invalidation</li>
</ul>
<h4>GEO Optimizations</h4>
<ul>
<li><strong>SpeakableSpecification</strong> – Marks content as suitable for voice assistants and AI</li>
<li><strong>Quality Indicators</strong> – Adds isAccessibleForFree and isPartOf to article schemas</li>
<li><strong>Entity Optimization</strong> – Enhanced Organization schema with @id, foundingDate, and numberOfEmployees</li>
</ul>
<h4>Meta Tags</h4>
<ul>
<li><strong>Open Graph</strong>: og:title, og:description, og:image, og:url, og:type, og:site_name, article:published_time</li>
<li><strong>Twitter Cards</strong>: twitter:card, twitter:title, twitter:description, twitter:image, twitter:site</li>
<li><strong>Smart Conflict Detection</strong>: Automatically skips output if Yoast, RankMath, or similar plugins are active</li>
<li><strong>Force Override</strong>: Option to output meta tags even when other plugins are detected</li>
</ul>
<h4>Why Do You Need AEO Engine?</h4>
<ul>
<li>Better visibility in AI-powered search results and answer engines</li>
<li>Improved content understanding by search engines and AI models</li>
<li>Rich snippets and enhanced search result presentation</li>
<li>Future-proof optimization for the AI era</li>
<li>Quick setup with automatic site data detection</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li><strong>Blogs</strong>: Optimize articles with BlogPosting, FAQ, and HowTo schemas</li>
<li><strong>Local Businesses</strong>: Full LocalBusiness schema with hours, address, and map coordinates</li>
<li><strong>E-commerce</strong>: WooCommerce Product schema with price and availability</li>
<li><strong>Corporate Sites</strong>: Organization schema with entity optimization</li>
<li><strong>Documentation Sites</strong>: LLMs.txt for better AI comprehension</li>
<li><strong>Video Content</strong>: Automatic VideoObject schema for embedded videos</li>
</ul>
<h4>Validation Tools</h4>
<ul>
<li>Google Rich Results Test</li>
<li>Schema.org Validator</li>
<li>Facebook Sharing Debugger</li>
<li>Twitter Card Validator</li>
<li>Direct site preview</li>
</ul>
<h4>Compatibility</h4>
<ul>
<li>Works with any well-coded WordPress theme</li>
<li>Compatible with WPML and Polylang</li>
<li>Works alongside Yoast SEO, RankMath, AIOSEO (with conflict detection)</li>
<li>WooCommerce integration for Product schema</li>
<li>Translation-ready (includes .pot file)</li>
</ul>
<h3>Developer Documentation</h3>
<h4>Available Filters</h4>
<p><strong>Schema Filters:</strong></p>
<pre><code>aeo_engine_organization_schema - Modify the Organization schema
aeo_engine_blogposting_schema - Modify the BlogPosting schema
aeo_engine_breadcrumb_schema - Modify the Breadcrumb schema
aeo_engine_faqpage_schema - Modify the FAQPage schema
aeo_engine_howto_schema - Modify the HowTo schema
aeo_engine_website_schema - Modify the WebSite schema
aeo_engine_localbusiness_schema - Modify the LocalBusiness schema
aeo_engine_videoobject_schema - Modify the VideoObject schema
aeo_engine_product_schema - Modify the Product schema
</code></pre>
<p><strong>Other Filters:</strong></p>
<pre><code>aeo_engine_registered_schemas - Add/remove registered schema classes
aeo_engine_post_schema_type - Change schema type by post type
aeo_engine_get_option - Modify any plugin option
</code></pre>
<h4>Example: Modify a Schema</h4>
<pre><code>add_filter('aeo_engine_blogposting_schema', function($schema, $post) {
    $schema['aggregateRating'] = [
        '@type' => 'AggregateRating',
        'ratingValue' => '4.5',
        'reviewCount' => '100'
    ];
    return $schema;
}, 10, 2);
</code></pre>
<h4>Example: Register a Custom Schema</h4>
<pre><code>add_filter('aeo_engine_registered_schemas', function($schemas) {
    require_once 'class-my-custom-schema.php';
    $schemas[] = new My_Custom_Schema();
    return $schemas;
});
</code></pre>
<h4>Example: Change Schema Type by Post Type</h4>
<pre><code>add_filter('aeo_engine_post_schema_type', function($type, $post_type, $post) {
    if ($post_type === 'recipe') {
        return 'Recipe';
    }
    return $type;
}, 10, 3);
</code></pre>
<h4>Get Plugin Options</h4>
<pre><code>$org_name = AEO_Engine::get_option('aeo_engine_org_name', 'Default Name');
</code></pre>
<h3>Privacy Policy</h3>
<p>AEO Engine does not collect, store, or transmit any personal data from users or site visitors. All configuration is stored locally in your WordPress database. The LLMs.txt files are generated from your already-public content.</p>
<h3>Support</h3>
<p>For support, documentation, and updates:</p>
<ul>
<li><strong>Documentation</strong>: https://wordpress.org/plugins/alquingadev-aeo-schema/</li>
<li><strong>Support</strong>: https://wordpress.org/support/plugin/alquingadev-aeo-schema/</li>
<li><strong>GitHub</strong>: https://github.com/alquingadev/aeo-engine</li>
<li><strong>Report Bugs</strong>: https://github.com/alquingadev/aeo-engine/issues</li>
</ul>
<h3>Credits</h3>
<p>Developed by PMV Agency for the WordPress community.</p>
<p>Built following Schema.org, Google Structured Data, and llmstxt.org best practices.</p>


AEO Engine

Complete SEO + AEO + GEO optimization engine. Generates Schema.org JSON-LD (9 types), Open Graph, Twitter Cards, and LLMs.

wpTruss Plugins

<p><strong>AI AEO for WooCommerce</strong> is built specifically for <strong>Answer Engine Optimization (AEO)</strong>.</p>
<p>Traditional SEO plugins optimize for rankings.<br />
This plugin optimizes your products for <strong>AI understanding and retrieval</strong>.</p>
<p>AI systems do not rank pages the way Google does.<br />
They extract structured data, interpret meaning, and recommend products based on confidence.</p>
<p>If your store lacks structured context, multilingual signals, and semantic clarity — your products will not be selected.</p>
<p>This plugin fixes that.</p>
<p>Learn more:<br />
<a href="https://wptruss.com/plugins/ai-aeo-seo-titles-for-woo-commerce/" rel="nofollow ugc"><br />
AI AEO for WooCommerce Plugin Overview<br />
</a></p>
<h3>🧠 What problem does this solve?</h3>
<p>Most WooCommerce stores are invisible in AI search because:</p>
<ul>
<li>Missing or incomplete structured data  </li>
<li>Weak product semantics (keyword-based, not meaning-based)  </li>
<li>No multilingual signals  </li>
<li>No clear product entity definition  </li>
<li>No FAQ or use-case context  </li>
<li>Missing trust signals (shipping, returns, policies)  </li>
</ul>
<p>Result: AI systems cannot confidently recommend your product.</p>
<h3>🇪🇺 Why this is especially powerful for European WooCommerce stores</h3>
<p>European eCommerce is inherently <strong>multilingual and cross-border</strong>.</p>
<p>Customers search in their native languages:</p>
<ul>
<li>English (base entity): “minimalist leather wallet for men”  </li>
<li>German: “leder geldbörse herren”  </li>
<li>French: “portefeuille cuir homme”  </li>
<li>Spanish: “cartera minimalista hombre”  </li>
</ul>
<p>But most WooCommerce stores only provide English product data.</p>
<p>AI systems rely on <strong>language matching + semantic understanding</strong>.<br />
If your product does not exist in the query language (even at a structured level), it is far less likely to be selected.</p>
<h3>🧠 English <span aria-hidden="true" class="wp-exclude-emoji">→</span> Multilingual mapping (how AI understands your product)</h3>
<p>This plugin keeps your <strong>original English product title as the base entity</strong>, and generates multilingual equivalents that AI systems map back to the same product.</p>
<p>Example:</p>
<p><strong>Original (English base entity):</strong><br />
Minimalist RFID Leather Wallet for Men</p>
<p><strong>Generated multilingual titles:</strong></p>
<ul>
<li>German: Leder Geldbörse Herren Minimalistisch RFID  </li>
<li>French: Portefeuille Cuir Homme Minimaliste RFID  </li>
<li>Spanish: Cartera Minimalista Hombre RFID  </li>
<li>Italian: Portafoglio Uomo Minimalista RFID  </li>
</ul>
<p>AI systems use this structure to:</p>
<ul>
<li>Recognize all variations as the same product  </li>
<li>Match queries across languages  </li>
<li>Improve confidence in recommendations  </li>
</ul>
<p>Instead of creating multiple translated pages, you create <strong>one strong multilingual product entity</strong>.</p>
<h3>🚀 What this enables</h3>
<p>A single product can now match:</p>
<ul>
<li>English: “best minimalist wallet for travel”  </li>
<li>German: “leder geldbörse herren”  </li>
<li>French: “portefeuille cuir homme”  </li>
<li>Spanish: “cartera minimalista hombre”  </li>
</ul>
<p>Without duplicating content or managing multiple language pages.</p>
<h3>🇪🇺 The hidden problem with multilingual WooCommerce (example)</h3>
<p>A customer in France searches:</p>
<ul>
<li>“portefeuille cuir homme”</li>
</ul>
<p>Your product exists:</p>
<ul>
<li>“Minimalist RFID Leather Wallet for Men” (in English)</li>
</ul>
<p>Even if you have a multilingual plugin installed, most setups:</p>
<ul>
<li>Keep English as the default product entity  </li>
<li>Translate content at the page level  </li>
<li>Do not inject multilingual meaning into structured data  </li>
</ul>
<p>Result:</p>
<p>AI systems may NOT confidently match your product to the French query.</p>
<p>Why?</p>
<p>Because AI systems rely on:</p>
<ul>
<li>Structured signals  </li>
<li>Entity consistency  </li>
<li>Language-level matching  </li>
</ul>
<p>Not just visible translated content.</p>
<h3>⚠️ What actually happens</h3>
<ul>
<li>Your product is in English  </li>
<li>The user searches in French  </li>
<li>AI cannot strongly map the query <span aria-hidden="true" class="wp-exclude-emoji">→</span> product  </li>
<li>Another store with better language signals gets recommended  </li>
</ul>
<p>👉 You lose customers who were already searching for your product.</p>
<h3>❌ Why multilingual plugins alone don’t solve this</h3>
<p>Traditional multilingual setups:</p>
<ul>
<li>Create separate translated pages  </li>
<li>Rely on default language indexing  </li>
<li>Do not connect all languages to a single product entity  </li>
</ul>
<p>AI systems still see:</p>
<ul>
<li>Fragmented or weak signals  </li>
<li>No strong cross-language mapping  </li>
</ul>
<p>So your product remains under-recommended.</p>
<h3>✅ How this plugin solves it</h3>
<p>This plugin keeps:</p>
<ul>
<li>One <strong>English base entity</strong></li>
</ul>
<p>And adds:</p>
<ul>
<li>Multilingual titles directly into structured data  </li>
<li>Cross-language semantic signals  </li>
<li>Strong entity mapping across languages  </li>
</ul>
<p>Now AI systems can:</p>
<ul>
<li>Understand all language variations as the same product  </li>
<li>Match queries across regions  </li>
<li>Recommend your product with higher confidence  </li>
</ul>
<p>Learn more about European multilingual strategy:</p>
<p><a href="https://wptruss.com/europe/scale-your-woocommerce-store-to-43-european-languages-via-ai-schema/" rel="nofollow ugc"><br />
Scale your WooCommerce store to 43+ European languages via AI schema<br />
</a></p>
<h3>✅ What this plugin actually does</h3>
<h4>1. Makes your products understandable to AI</h4>
<p>Generates AI-optimized product titles and context that help AI systems understand:</p>
<ul>
<li>What the product is  </li>
<li>Who it is for  </li>
<li>When and why it should be used  </li>
<li>How it compares to alternatives  </li>
</ul>
<p>This improves <strong>entity matching and retrieval accuracy</strong>.</p>
<h4>2. Adds structured data AI systems rely on</h4>
<p>Automatically generates Schema.org markup:</p>
<ul>
<li>Product  </li>
<li>Offer (price, currency, availability)  </li>
<li>AggregateRating  </li>
<li>FAQ schema  </li>
</ul>
<p>This enables <strong>machine-readable extraction</strong>, not just indexing.</p>
<h4>3. Adds multilingual product intelligence</h4>
<ul>
<li>Generates product titles in 90+ languages  </li>
<li>Injects multilingual signals into structured data  </li>
</ul>
<p>This allows AI systems to match queries across regions without requiring multiple translated pages.</p>
<h4>4. Prepares your store for AI-driven discovery</h4>
<p>Instead of optimizing for:</p>
<ul>
<li>Rankings  </li>
</ul>
<p>You optimize for:</p>
<ul>
<li>AI answers  </li>
<li>Product recommendations  </li>
<li>Cross-language discovery  </li>
</ul>
<h3>🔍 Why this is different from SEO plugins</h3>
<p>SEO plugins:</p>
<ul>
<li>Optimize meta titles and keywords  </li>
<li>Focus on rankings  </li>
</ul>
<p>This plugin:</p>
<ul>
<li>Optimizes for AI systems (ChatGPT, Perplexity, Gemini)  </li>
<li>Structures product data for machine understanding  </li>
<li>Improves likelihood of being selected in AI-generated answers  </li>
</ul>
<p>This is not SEO.<br />
This is <strong>AEO (Answer Engine Optimization)</strong>.</p>
<h3>📈 Example queries your products can match</h3>
<ul>
<li>English: best minimalist wallet for travel  </li>
<li>German: leder geldbörse herren  </li>
<li>French: portefeuille cuir homme  </li>
<li>Spanish: cartera minimalista hombre  </li>
<li>English: bluetooth headphones for flights  </li>
<li>English: privacy messaging app without phone number  </li>
</ul>
<p>AI systems use structured understanding to match these queries to your products.</p>
<h3>⚙️ Features</h3>
<ul>
<li>AI-powered product title generation using Google Gemini  </li>
<li>Multilingual support (90+ languages)  </li>
<li>Schema.org structured data (Product, Offer, Rating, FAQ)  </li>
<li>Batch processing for large catalogs  </li>
<li>Product collections with shortcode support  </li>
<li>XML sitemap integration  </li>
</ul>
<h3>🧩 How it works</h3>
<ol>
<li>Select your WooCommerce products  </li>
<li>Generate AI titles and structured data  </li>
<li>Review and publish  </li>
<li>Your store becomes AI-readable and machine-friendly  </li>
</ol>
<h3>📌 Who should use this plugin?</h3>
<ul>
<li>WooCommerce stores targeting European or global markets  </li>
<li>Stores selling across multiple languages  </li>
<li>Large product catalogs  </li>
<li>Founders exploring AI search visibility  </li>
<li>Anyone preparing for post-SEO discovery  </li>
</ul>
<h3>⚠️ Important</h3>
<p>This plugin does NOT guarantee rankings.</p>
<p>It improves your chances of being:</p>
<ul>
<li>Understood  </li>
<li>Matched  </li>
<li>Recommended  </li>
</ul>
<p>…by AI systems like ChatGPT, Perplexity, and Google Gemini and more.</p>
<h3>Requirements</h3>
<ul>
<li>WooCommerce 7.0 or higher  </li>
<li>A Google Gemini API key (https://aistudio.google.com/app/apikey)  </li>
</ul>
<h3>External Services</h3>
<p>This plugin connects to the Google Gemini API.</p>
<ul>
<li>Service: https://ai.google.dev/  </li>
<li>Data sent: product title, description, categories, attributes  </li>
<li>When: only on manual generation or batch processing  </li>
<li>API key: provided by you, requests go directly to Google  </li>
<li>Terms: https://ai.google.dev/terms  </li>
<li>Privacy: https://policies.google.com/privacy  </li>
</ul>
<p>No customer personal data is sent.</p>


AI AEO for WooCommerce

Make your WooCommerce products understandable, matchable, and recommendable by AI systems like ChatGPT, Perplexity, and Google Gemini.

AEO Engine vs AI AEO for WooCommerce