--- title: "FAQ" url: "https://aeoultimate.com/docs/woocommerce/faq/" description: "Get answers about AEO Ultimate for WooCommerce schema, pricing, variable products, HPOS compatibility, Merchant Center sync and AI features explained." published: "2026-08-30T22:21:51+00:00" modified: "2026-08-30T22:33:49+00:00" language: "en-US" site: "AEO Ultimate" --- Source: https://aeoultimate.com/docs/woocommerce/faq/ AEO Ultimate for WooCommerce # Questions people actually ask If something is going wrong, [Troubleshooting](https://aeoultimate.com/docs/woocommerce/troubleshooting/) is the better page. This one is about how the plugin behaves and why it makes the choices it does. ## Do I need the WordPress plugin as well? No. This extension is complete for commerce on its own. If you do run both, the WordPress plugin **stands down from commerce output automatically** so nothing publishes twice — you do not have to configure anything to make that happen. Running both makes sense when you also want the non-commerce features — llms.txt, author E-E-A-T, Local SEO, the Command Center — on the same site. ## Will this duplicate the schema WooCommerce already outputs? WooCommerce’s own Product and breadcrumb markup is suppressed automatically — but **only with your one-click consent**. Until you give it, both may be present, which is why a validator can legitimately show two Product blocks on a fresh install. The consent step exists because silently removing another plugin’s output is the kind of thing that should be your decision. ## Does my schema go stale when prices change? No. Structured data is rebuilt from live WooCommerce data on every page load — it is never frozen into a saved copy. Change a price, sell the last unit, add a variation or edit a shipping zone, and the published schema follows immediately. This is the main reason a mismatch between your storefront and your schema should not happen. If you see one, it is almost always a page cache rather than stale data. ## Which price does it publish — with or without tax? The tax-inclusive figure a shopper actually sees, so your schema matches your storefront and your Merchant Center feed. A schema price that disagrees with the visible price is a feed error and erodes trust with the engine. ## What happens to products with no price? They publish **no offer at all** — not an offer of zero. An empty price field is not a price of nothing, and publishing zero would be a false statement about your catalogue. The same principle runs through the plugin: where a fact cannot be established honestly, nothing is published rather than something invented. ## How are variable products handled? As a `ProductGroup` with every variant, and an `AggregateOffer` carrying a real low and high price rather than a single guessed figure. Products from Bookings, Subscriptions, Bundles and similar extensions publish a “From” price or a range — never a definite price their own page would contradict. ## Is it HPOS compatible? Yes — High-Performance Order Storage and the Cart & Checkout blocks are both declared compatible. The plugin never touches order storage directly, which is what makes that safe rather than merely claimed. ## What does Merchant Center sync actually check? It compares your catalogue against what Google and Bing **actually list**, rather than what you think you submitted — surfacing missing products, rejected items, price mismatches and identifier gaps, with an integrity score. That distinction matters: a feed can upload successfully and still have items silently rejected downstream. ## Am I billed for AI by you? No. There is no credit meter and no surcharge. You connect an API key you already control — Claude, OpenAI, Gemini, Perplexity, xAI or Mistral — and settle with that provider at their raw rate. Nothing is sent anywhere until you configure a feature and trigger it. The plugin is fully functional with no AI configured at all. ## Does the plugin phone home? It collects **no usage telemetry**, no tracking and no analytics. It does check for updates. Because it is not hosted on WordPress.org, updates come from our licence server instead: once you enter a licence key the plugin joins WordPress’s own routine update check, sending your **licence key, site URL and plugin name — nothing else**. Before a key is entered it makes no contact at all, and an expired licence stops updates only. No store-visitor or customer personal data is ever sent anywhere. See the [privacy policy](https://aeoultimate.com/privacy-policy/). ## What happens when my licence expires? Nothing breaks. The plugin keeps publishing your schema exactly as before — it never disables itself. You stop receiving updates and support until you renew. $99 a year, one site, GPL-2.0+, with a full refund within 30 days of purchase. [Full terms](https://aeoultimate.com/terms/). ## What are the requirements? WordPress 6.5 or newer WooCommerce 8.0 to 11.0 PHP 7.4 or newer Memory, for AI features 512MB recommended Barcode/GTIN reporting Needs WooCommerce 9.2+ ## Something is not answered here Ask. Questions that reach me become documentation, so asking one genuinely helps whoever hits the same thing next.