What default WooCommerce schema do AI engines ignore?

Cherry Seed

WooCommerce's default Product schema covers fewer than half of the properties AI shopping engines require (Seresa, 2026). Out of the box, WooCommerce outputs name, description, price, and a basic availability flag — but AI engines need brand, GTIN or MPN identifiers, aggregate ratings with review count, shipping details, and product condition before they'll match or recommend a listing. The default markup also skips the offers wrapper Google and AI engines expect for price data. Without these fields, AI engines can't distinguish your products from millions of competing listings and silently pass them over.

Full Answer

WooCommerce generates a minimal Product JSON-LD block: name, description, price, and an in-stock or out-of-stock availability value. That's technically valid schema, but AI shopping engines treat it as a skeleton — not enough to act on.

The first gap is identity. Without brand, GTIN, MPN, or SKU in the markup, AI engines can't verify which product you're selling or match it against a buyer's query. A search for "Canon EOS R6 II body" needs those identifiers to confirm your listing is the real product, not a generic description.

The second gap is trust signals. AI engines weigh aggregateRating and reviewCount heavily when deciding which merchant to cite. WooCommerce has a review system built in, but the default schema doesn't expose those ratings as structured data — so AI engines see a product with no social proof.

The third gap is commercial detail. Properties like shippingDetails, hasMerchantReturnPolicy, and itemCondition tell AI engines whether your listing is current, deliverable, and returnable. Google's structured data documentation lists these as recommended for merchant listings — AI engines treat the same fields as required (Google Search Central, 2026). For a full breakdown of which fields are missing and how to add them, see Schema Markup for WooCommerce.

Cherry Seed

Quick Answer

Full Answer

Sources