NeoSEO WooCommerce product schema for rich results and AI search
Most stores are invisible in Google’s product results for a reason nobody tells them about: their markup is missing a field. One absent property does not shrink the rich result — it removes the whole thing, silently, with no warning in the dashboard.
NeoSEO reads what WooCommerce already knows — variations, shipping zones, brands, dimensions, stock — and turns it into the structured data search engines and AI answer engines actually read.
NeoSEO is not released yet.
It is in active development and has no download or price today. This page will carry both the moment it ships.
Why WooCommerce product rich results go missing
Google builds product rich results — price, stock, ratings, shipping and returns under a search result — from the Product structured data on each product page. WooCommerce outputs some of it out of the box, and the gaps are in the same places on almost every store:
- Variable products. WooCommerce describes a variable product as one product with a price range. Google’s variant markup instead expects a
ProductGroupwhose variants each carry their own price, SKU and availability. - Shipping and returns. WooCommerce’s built-in markup includes neither shipping details nor a return policy, though your shipping zones already hold the information.
- Disconnected fragments. The product, the page, the breadcrumbs and the store itself are described separately, with nothing tying them into one picture of your shop.
None of this is visible on the page, which is why it goes unnoticed. It is also what AI answer engines read when they decide which store to name for a product.
What NeoSEO will do for WooCommerce product schema
Planned for the first release. Nothing below ships today.
Variants as separate products
A variable product is not one purchasable thing. NeoSEO emits a proper ProductGroup with every variation nested inside it, each with its own price, SKU, color and availability.
Shipping and returns from your settings
Built from your live shipping zones and declared return terms rather than retyped. Nothing is invented: a cost that depends on a formula is left out rather than guessed at.
One connected graph
Organization, WebSite, WebPage, breadcrumbs, products and FAQs, all linked by @id so a consumer sees one description of your store instead of scattered fragments.
Built for AI search
A cached llms.txt summary at your site root, speakable markup, and product Open Graph tags for social catalogs.
How it is being built
- Steps aside automatically when Yoast, Rank Math, AIOSEO, SEOPress, Slim SEO, The SEO Framework or Squirrly is active.
- No frontend JavaScript, no CSS, and no database tables — not now, not later.
- WooCommerce is optional: without it you still get the full content graph.
WooCommerce product schema: questions
NeoSEO is in active development and has no release date, download or price today. This page will carry both the moment it ships.
No. It steps aside automatically when Yoast, Rank Math, AIOSEO, SEOPress, Slim SEO, The SEO Framework or Squirrly is active, so a store never ends up with two sets of markup.
No. NeoSEO adds no frontend JavaScript, no CSS and no database tables. Its output is structured data in the page head.
No. WooCommerce is optional: without it you still get the full content graph. With it, product markup is added from your products, variations and shipping settings.
A Product node per product page with its offer, which for a variable product is a price range rather than one entry per variation. It does not include shipping details or a return policy.