How WooCommerce Handles Schema Markup by Default
WooCommerce outputs basic Product schema automatically on single product pages, including name, description, SKU, and price. However, the default implementation is incomplete by search engine standards — it routinely omits AggregateRating, Review, Offer availability, and currency fields unless a dedicated schema plugin is active.
Themes compound this problem. Storefront and many third-party WooCommerce themes inject their own microdata or JSON-LD fragments, creating duplicate or conflicting schema that Google's Rich Results Test flags as errors. Before adding any plugin, audit what your active theme already outputs using the URL Inspection tool in Google Search Console or the Rich Results Test directly.
The practical starting point for any WooCommerce store: install a schema-specific plugin, disable any schema output from the theme, and verify a single product URL shows one clean JSON-LD block covering Product, Offer, and AggregateRating (if reviews are enabled).
The WooCommerce Plugin Ecosystem for Structured Data
Rank Math and Yoast SEO are the two dominant schema plugins in the WordPress/WooCommerce ecosystem. Both generate JSON-LD Product schema and pull WooCommerce product data — price, stock status, currency, brand — into the output automatically. Rank Math's schema module allows custom schema types and field mapping without code; Yoast's WooCommerce SEO add-on (a paid extension) layers richer product-level controls on top of the free plugin.
Schema Pro and WP Schema Pro are alternatives that focus exclusively on structured data rather than broader SEO. They give field-level control and support for additional types like FAQPage and HowTo on product description tabs, which is useful if product pages carry instructional content alongside commerce data.
For stores with hundreds of SKUs and product variations, the critical requirement is dynamic field mapping — the plugin must pull WooCommerce custom fields (ACF fields, product attributes, variation prices) automatically rather than requiring manual entry per product. Confirm this before committing to any tool by testing with a variable product, not a simple one.
Variable Products, Variations, and Offer Schema
Variable products are the most common source of schema errors in WooCommerce. Each variation has its own price range, SKU, and stock status, but most plugins default to outputting the parent product's price range as a single Offer or PriceSpecification block. Google accepts priceValidUntil and lowPrice/highPrice within AggregateOffer, but the markup must be accurate — if a variation is out of stock, the availability field at the variation level should reflect that.
The correct approach for variable products is to output an AggregateOffer with offerCount equal to the number of in-stock variations, plus lowPrice and highPrice reflecting the actual variation price range. Rank Math and Yoast both approximate this, but stores with complex pricing (tiered discounts, user-role pricing via plugins like WooCommerce Memberships) need to verify output manually because those dynamic prices do not feed into schema automatically.
A common oversight: sale prices. When a WooCommerce sale is running, the schema Offer should reflect the current sale price, not the regular price. Most schema plugins pull _price (the active price) rather than _regular_price from the WooCommerce database, so this is usually handled correctly — but confirm it during a live sale event before relying on price-rich results to drive traffic.
WooCommerce-Specific Schema Gaps to Work Around
Three structured data gaps appear repeatedly in WooCommerce audits. First, Brand schema: WooCommerce does not have a native brand field on products. Most stores store brand as a custom taxonomy or ACF field. Schema plugins need to be manually mapped to that field; otherwise the brand property is absent, which limits eligibility for certain Google Shopping-adjacent rich results.
Second, Review schema: WooCommerce's native review system outputs reviews in HTML, but the JSON-LD AggregateRating block only appears if the schema plugin reads WooCommerce's wp_comments table and aggregates correctly. Stores using third-party review platforms (Judge.me, Stamped.io, Yotpo) must confirm that the review plugin and the schema plugin communicate — some review tools inject their own schema, creating duplicates alongside the existing plugin output.
Third, product images. WooCommerce supports gallery images, but schema image arrays should include all gallery images, not just the featured image. Most plugins default to the featured image only. For apparel or multi-image product categories where image carousels in search results matter, custom code or a plugin filter is required to pass the full image gallery into the schema block.
Category Pages, Site-Wide Schema, and Breadcrumb Markup
WooCommerce category pages (shop archives) are eligible for BreadcrumbList and ItemList schema, but neither appears by default. BreadcrumbList is handled well by Rank Math and Yoast at the site level — they read WooCommerce's category hierarchy and output correct breadcrumb paths automatically once breadcrumbs are enabled in plugin settings.
ItemList schema for category pages lists the products within that archive as ListItem elements. This is valuable for category-level rich results but requires either plugin support or custom code. As of current plugin versions, this is not automatic in most WooCommerce schema setups and is a gap worth addressing for large stores where category pages drive significant organic traffic.
The homepage and cart/checkout pages do not benefit from Product schema. Applying WebSite schema with a Sitelinks Searchbox on the homepage and Organization schema with logo and contact details are the meaningful additions at the site level. Both are standard outputs in Rank Math and Yoast with minimal configuration.
Validation Workflow for WooCommerce Schema
Run every schema change through Google's Rich Results Test before pushing to production. Test a simple product, a variable product, a product with active sale price, and a product with reviews — these four cases cover the majority of failure modes specific to WooCommerce. A clean result on a simple product does not guarantee correct output on a variable product.
After deployment, submit updated product URLs via the URL Inspection tool in Google Search Console and monitor the Enhancements section for Product and Review snippet reports. WooCommerce stores that update pricing frequently should also check that no cached schema (from full-page caching plugins like WP Rocket or LiteSpeed Cache) is serving stale price or stock data to Googlebot. Configure cache exclusions for product pages or set short TTLs to prevent price mismatch errors in structured data reports.
The actionable priority sequence: (1) install a schema plugin and disable theme schema output, (2) map brand to a WooCommerce product attribute or taxonomy, (3) verify variable product Offer output during an active sale, (4) confirm AggregateRating pulls from the correct review source, (5) validate via Rich Results Test on all four product types, then monitor Search Console Enhancements weekly for the first month after launch.