| 开发者 | bytloop |
|---|---|
| 更新时间 | 2026年8月22日 19:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Product, Offer, ProductGroup, BreadcrumbList, CollectionPage, and more — designed specifically for how AI search engines like ChatGPT Search, Perplexity Shopping, Claude, and Google AI Overviews decide which products to cite.
Why Uttor?
Most AEO (Answer Engine Optimization) tooling targets blogs and content sites — headings, FAQ schema, article markup. WooCommerce stores need something different: product schema, variable product structure, category page markup, and store-level entity data.
Uttor focuses specifically on WooCommerce products — complete Product, Offer, and ProductGroup schema, AI crawler controls, and llms.txt generation built around how a store catalog actually works. It cooperates with your existing SEO plugin — Yoast, Rank Math, All in One SEO, or SEOPress — filling the gaps they leave, without duplicating what they already do.
Features (free)
ProductGroup with hasVariant linking every variationwp uttor-aeo audit, wp uttor-aeo regenerate, wp uttor-aeo validate.pot file and RTL supportllms.txt sections are overridable in your theme. Full REST API for programmatic access to schema. See the developer docs.
Answer Engine Optimization. It's like SEO, but for AI search engines — ChatGPT Search, Perplexity, Claude, Google AI Overviews, Bing Copilot. When a shopper asks an AI which product to buy, AEO is what determines whether YOUR products get cited in the answer.
Yes. Content SEO plugins do a good job on blog posts and pages. They do a partial job on products — often missing ProductGroup for variable products, Offer variations, and correct shipping/return policy schema, and typically don't generate llms.txt or manage AI crawlers granularly. Uttor detects your SEO plugin and fills the gaps without duplicating what it already does.
No. Uttor's conflict detector explicitly checks what your SEO plugin emits and hands off ownership of overlapping schema types. Zero duplicate JSON-LD. You can see exactly who owns what on the Uttor health check page.
An emerging convention (llmstxt.org) for helping AI systems understand your site. Similar to how robots.txt guides search crawlers, llms.txt provides a curated, LLM-friendly summary of your site's key content. Uttor generates one automatically for your WooCommerce store.
Yes. Uttor has granular per-bot toggles in robots.txt for every major AI crawler. Allow the ones you want to be cited by (ChatGPT, Claude, Perplexity), block the ones you don't. Uttor writes via the robots_txt filter and never overwrites your physical robots.txt file if you have one.
Yes. Uttor emits schema and meta tags via WordPress hooks — no theme dependencies. Works with Storefront, Astra, Kadence, Blocksy, GeneratePress, and all modern block themes.
Yes. Uttor is fully compatible with WooCommerce High-Performance Order Storage.
Schema generation runs on wp_head with caching per product. Overhead is negligible — target is under 10ms per page. llms.txt is pre-generated on cron and served statically.
Only for Pro features that use AI (product summaries, category copy, citation tracking, image alt text). Free features don't require any API keys.
Uttor doesn't create any custom data — settings live in wp_options, and generated meta values live in standard WooCommerce meta. On uninstall, you're asked whether to delete Uttor's settings and generated meta. Original WooCommerce data is untouched.
Support is available in the plugin's support forum on wordpress.org. Pro customers get email support with a 24-hour response SLA.
The hooks reference lives at uttor.bytloop.com and in /docs/hooks.md in the plugin.