Everything you'd want to know before you install.
A detailed look at how llms.txt + AEO Schema WooCommerce — AI SEO & Agent FAQ works, why we built it the way we did, and the thinking behind the features above.
Why llms.txt and AEO Schema on WooCommerce
The llms.txt standard has emerged as the reference way to expose a site to Large Language Models. But on WooCommerce, the missing piece is not just llms.txt — it is also the product schema. WooCommerce generates a minimal Product JSON-LD that omits everything AI agents actually need: exact brand, GTIN, materials, compatibility, precise return policy, shipping conditions. The result: agents make things up. This plugin serves a dynamic llms.txt and enriches the Product schema with exactly the attributes ChatGPT, Claude, Perplexity and Gemini rely on to answer without hallucinating.
A dynamic, multilingual llms.txt with zero maintenance
The file is served at your site root through a native WordPress rewrite rule. Sections (product categories, products, pages, posts, policies) are generated automatically from your data. The transient cache is scoped by language and invalidated automatically on every edit. Polylang and WPML are detected without configuration — each language has its llms.txt served on the corresponding URL. You stay in control of what is exposed: products included or not, pages, posts, editable intro paragraph.
Enriched product schema — what WooCommerce does not do
WooCommerce natively exposes a Product schema with offers and prices, but omits brand, GTIN, materials, compatibility, return policy and shipping details. This plugin hooks into the native woocommerce_structured_data_product filter and adds: brand (per product or global), gtin with gtin8/12/13/14 auto-detection by length, mpn, material (one or several materials comma-separated), color and size from attributes, dimensions and weight with WooCommerce units, isRelatedTo for compatibility (array of Product, one per line). Everything is non-destructive: if an SEO plugin already adds some fields, they are preserved.
Agent-targeted FAQ — separate from the customer FAQ
A customer FAQ answers emotional and marketing-oriented questions. An agent FAQ answers technical and factual questions: exact compatibility, exact dimensions, ingredients, certifications, usage conditions. This plugin adds a separate FAQPage schema on every product page, fed by a dedicated metabox. You write the Q&A once, they feed the FAQPage JSON-LD that agents consume — without interfering with the customer-facing FAQ.
Explicit policies to reduce hallucinations
AI agents hallucinate especially on policies (returns, shipping, warranty) because that information is rarely structured. The plugin adds hasMerchantReturnPolicy with a configurable return window and fee type (free, customer pays, or shipping-only), shippingDetails with deliveryTime, handlingTime and transitTime, and a seller of type Organization injected into every Offer to answer the question: who sells this product? Your policies become machine-readable.
Compatible with Polylang, WPML, HPOS and every major SEO plugin
HPOS-compatible (explicit declaration via FeaturesUtil). Polylang and WPML detected automatically for the llms.txt and product translations. Compatible with Yoast SEO, RankMath and SEO Press: the module never overrides their schema, it enriches alongside. Two developer filters (dfllmstxtaeo_llms_output and dfllmstxtaeo_product_schema) let you customise without touching the plugin code. PSR-4 style code, PHP 8.0+, translated into French, English, Spanish and German.
There are no reviews yet.