wpTruss Plugins

AI AEO for WooCommerce is built specifically for Answer Engine Optimization (AEO).
Traditional SEO plugins optimize for rankings. 
This plugin optimizes your products for AI understanding and retrieval.
AI systems do not rank pages the way Google does. 
They extract structured data, interpret meaning, and recommend products based on confidence.
If your store lacks structured context, multilingual signals, and semantic clarity — your products will not be selected.
This plugin fixes that.
Learn more: 
<a href="https://wptruss.com/plugins/ai-aeo-seo-titles-for-woo-commerce/" rel="nofollow ugc"> 
AI AEO for WooCommerce Plugin Overview 
</a>
<h3>🧠 What problem does this solve?</h3>
Most WooCommerce stores are invisible in AI search because:
<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>
Result: AI systems cannot confidently recommend your product.
<h3>🇪🇺 Why this is especially powerful for European WooCommerce stores</h3>
European eCommerce is inherently multilingual and cross-border.
Customers search in their native languages:
<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>
But most WooCommerce stores only provide English product data.
AI systems rely on language matching + semantic understanding. 
If your product does not exist in the query language (even at a structured level), it is far less likely to be selected.
<h3>🧠 English → Multilingual mapping (how AI understands your product)</h3>
This plugin keeps your original English product title as the base entity, and generates multilingual equivalents that AI systems map back to the same product.
Example:
Original (English base entity): 
Minimalist RFID Leather Wallet for Men
Generated multilingual titles:
<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>
AI systems use this structure to:
<ul>
<li>Recognize all variations as the same product </li>
<li>Match queries across languages </li>
<li>Improve confidence in recommendations </li>
</ul>
Instead of creating multiple translated pages, you create one strong multilingual product entity.
<h3>🚀 What this enables</h3>
A single product can now match:
<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>
Without duplicating content or managing multiple language pages.
<h3>🇪🇺 The hidden problem with multilingual WooCommerce (example)</h3>
A customer in France searches:
<ul>
<li>“portefeuille cuir homme”</li>
</ul>
Your product exists:
<ul>
<li>“Minimalist RFID Leather Wallet for Men” (in English)</li>
</ul>
Even if you have a multilingual plugin installed, most setups:
<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>
Result:
AI systems may NOT confidently match your product to the French query.
Why?
Because AI systems rely on:
<ul>
<li>Structured signals </li>
<li>Entity consistency </li>
<li>Language-level matching </li>
</ul>
Not just visible translated content.
<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 → product </li>
<li>Another store with better language signals gets recommended </li>
</ul>
👉 You lose customers who were already searching for your product.
<h3>❌ Why multilingual plugins alone don’t solve this</h3>
Traditional multilingual setups:
<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>
AI systems still see:
<ul>
<li>Fragmented or weak signals </li>
<li>No strong cross-language mapping </li>
</ul>
So your product remains under-recommended.
<h3>✅ How this plugin solves it</h3>
This plugin keeps:
<ul>
<li>One English base entity</li>
</ul>
And adds:
<ul>
<li>Multilingual titles directly into structured data </li>
<li>Cross-language semantic signals </li>
<li>Strong entity mapping across languages </li>
</ul>
Now AI systems can:
<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>
Learn more about European multilingual strategy:
<a href="https://wptruss.com/europe/scale-your-woocommerce-store-to-43-european-languages-via-ai-schema/" rel="nofollow ugc"> 
Scale your WooCommerce store to 43+ European languages via AI schema 
</a>
<h3>✅ What this plugin actually does</h3>
<h4>1. Makes your products understandable to AI</h4>
Generates AI-optimized product titles and context that help AI systems understand:
<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>
This improves entity matching and retrieval accuracy.
<h4>2. Adds structured data AI systems rely on</h4>
Automatically generates Schema.org markup:
<ul>
<li>Product </li>
<li>Offer (price, currency, availability) </li>
<li>AggregateRating </li>
<li>FAQ schema </li>
</ul>
This enables machine-readable extraction, not just indexing.
<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>
This allows AI systems to match queries across regions without requiring multiple translated pages.
<h4>4. Prepares your store for AI-driven discovery</h4>
Instead of optimizing for:
<ul>
<li>Rankings </li>
</ul>
You optimize for:
<ul>
<li>AI answers </li>
<li>Product recommendations </li>
<li>Cross-language discovery </li>
</ul>
<h3>🔍 Why this is different from SEO plugins</h3>
SEO plugins:
<ul>
<li>Optimize meta titles and keywords </li>
<li>Focus on rankings </li>
</ul>
This plugin:
<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>
This is not SEO. 
This is AEO (Answer Engine Optimization).
<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>
AI systems use structured understanding to match these queries to your products.
<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>
This plugin does NOT guarantee rankings.
It improves your chances of being:
<ul>
<li>Understood </li>
<li>Matched </li>
<li>Recommended </li>
</ul>
…by AI systems like ChatGPT, Perplexity, and Google Gemini and more.
<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>
This plugin connects to the Google Gemini API.
<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>
No customer personal data is sent.

AI AEO for WooCommerce

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

mandat

Mandat AEO Assistant is a powerful WordPress plugin that leverages Google’s Gemini AI and Vertex AI to automatically generate high-quality, SEO-optimized blog posts. The plugin provides a comprehensive Article Studio interface where you can:
<ul>
<li>Generate long-form articles (>=1600 words) using Google Gemini 2.0/2.5 models</li>
<li>Create AI-generated featured and in-content images using Imagen 4.0</li>
<li>Automatically insert internal links from your existing content</li>
<li>Find and embed relevant YouTube videos</li>
<li>Generate SEO metadata (meta descriptions, focus keywords, tags)</li>
<li>Support for both Vietnamese and English content</li>
<li>Automatic translation with Polylang integration</li>
<li>Real-time cost tracking for all API usage </li>
</ul>
The plugin is designed for content creators, bloggers, and digital marketers who want to streamline their content production workflow while maintaining high quality and SEO best practices.
<h3>External Services</h3>
This plugin connects to external Google Cloud services to provide AI-powered features. Below is detailed information about each service used, what data is transmitted, and when these connections occur.
<h4>Google Cloud Vertex AI – Gemini API</h4>
Purpose: Generates AI-powered article content using Google’s Gemini language models (gemini-2.0-flash-exp, gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite).
When used: 
– When you click “Create Article” in the Article Studio interface 
– When using the automatic translation feature with Polylang
Data sent to Google: 
– Your article topic, keywords, and content generation parameters 
– Source text for translation (when translating existing content) 
– Your Google Cloud Service Account credentials for authentication 
– No personal user data from your website visitors is ever sent
Data received from Google: 
– Generated HTML article content 
– SEO metadata suggestions (titles, descriptions, keywords) 
– Token usage statistics for cost tracking
API Endpoint: https://us-central1-aiplatform.googleapis.com/v1/projects/{project_id}/locations/us-central1/publishers/google/models/
Service Terms: https://cloud.google.com/terms
Privacy Policy: https://policies.google.com/privacy
<h4>Google Cloud Vertex AI – Imagen API</h4>
Purpose: Generates AI images for featured images and in-content illustrations using Google’s Imagen 4.0 model.
When used: 
– When you click “Generate Images” after article creation 
– Images are only generated when you explicitly request them
Data sent to Google: 
– Text prompts describing the desired images 
– Image generation parameters (aspect ratio, style) 
– Your Google Cloud Service Account credentials 
– No personal data or user information is transmitted
Data received from Google: 
– Base64-encoded PNG image data 
– Generation metadata
API Endpoint: https://us-central1-aiplatform.googleapis.com/v1/projects/{project_id}/locations/us-central1/publishers/google/models/imagen-4.0-generate-001:predict
Service Terms: https://cloud.google.com/terms
Privacy Policy: https://policies.google.com/privacy
<h4>Google OAuth2 API</h4>
Purpose: Authenticates your Google Cloud Service Account to securely access Vertex AI services.
When used: Automatically before each API call to Gemini or Imagen (access tokens are cached for 55 minutes to minimize requests).
Data sent to Google: 
– JWT (JSON Web Token) signed with your Service Account private key 
– Service Account email address 
– Timestamp and token expiration data
Data received from Google: 
– Temporary access token (valid for 1 hour) 
– Token expiration timestamp
API Endpoint: https://oauth2.googleapis.com/token
Service Terms: https://developers.google.com/terms
Privacy Policy: https://policies.google.com/privacy
<h4>YouTube Data API v3</h4>
Purpose: Searches for and retrieves YouTube video information to embed relevant videos in articles.
When used: Only when the “Generate YouTube Video” option is enabled during article creation.
Data sent to Google: 
– Search keywords related to your article topic 
– Language and region preferences 
– Your YouTube Data API key
Data received from Google: 
– Video IDs, titles, and descriptions 
– Channel information 
– Video metadata (upload date, thumbnails)
API Endpoint: https://www.googleapis.com/youtube/v3/search
Service Terms: https://developers.google.com/youtube/terms/api-services-terms-of-service
Privacy Policy: https://policies.google.com/privacy
<h4>Google Custom Search API</h4>
Purpose: Searches the web to gather factual information and current sources to enhance article accuracy and relevance.
When used: Automatically during article generation to provide the AI with up-to-date context and credible sources.
Data sent to Google: 
– Search queries based on your article topic and keywords 
– Language and region preferences 
– Your Custom Search Engine ID and API key 
– Number of results requested (typically 3-10)
Data received from Google: 
– Search result titles, URLs, and snippets 
– Page metadata
API Endpoint: https://www.googleapis.com/customsearch/v1
Service Terms: https://developers.google.com/custom-search/v1/overview
Privacy Policy: https://policies.google.com/privacy
<h4>Privacy and Data Protection</h4>
Important notes: 
– No personal data from your website visitors (names, emails, IP addresses) is ever transmitted to external services 
– All API calls are initiated only by authenticated WordPress administrators 
– API keys and credentials are stored securely in your WordPress database (encrypted or hashed where possible) 
– Generated content is saved to your WordPress database only; Google does not retain your content beyond the time needed for API processing 
– Cost tracking data (token usage) is stored locally in your WordPress database 
– This plugin does not use cookies or collect any user data from your site visitors
GDPR Compliance: This plugin does not collect, store, or transmit any personal data from your website visitors. All external API calls are initiated exclusively by authenticated WordPress administrators for content generation purposes.
<h3>Credits</h3>
This plugin integrates with the following Google Cloud services: 
– Google Cloud Vertex AI (Gemini language models and Imagen image generation) 
– Google OAuth2 API for secure authentication 
– YouTube Data API v3 for video content 
– Google Custom Search API for web research
All trademarks and service marks are the property of their respective owners.
<h3>Support</h3>
For support, feature requests, or bug reports, please visit: https://eonsr.com/
<h3>License</h3>
This plugin is licensed under GPL-2.0-or-later. See https://www.gnu.org/licenses/gpl-2.0.html for details.

Mandat AEO Assistant

AI-powered content generation plugin using Google Gemini API to create long-form SEO articles with images, internal linking, and Polylang integration.

AI AEO for WooCommerce vs Mandat AEO Assistant