13 WooCommerce Product Schema Checks for Store Owners

Audit WooCommerce product schema with 13 checks for prices, stock, variants, reviews and policies, plus a reusable repair record for your store.

Editorial policy

WooCommerce product schema is worth checking against the item a customer can actually buy. Start with the live product page, find its Product and Offer data, and compare the price, currency, stock, identifiers and reviews with the visible offer. Then validate Google's requirements. A passing syntax check cannot tell you whether a price is commercially correct.

WooCommerce can already generate product structured data. Your theme, extensions and custom code can alter that output, so another schema plugin is not automatically the solution. These 13 checks help you identify the wrong field and give the person responsible enough evidence to fix its source.

Start with a small sample: one simple product, one sale product, one out-of-stock product and one variable product with different prices or stock levels. Add another market or currency if your store serves it. Save the exact URLs, capture time and relevant WooCommerce, theme and plugin versions before changing anything.

This is a documentation-based audit workflow, not a report of tests performed on your store. Google's and WooCommerce's sources were checked on November 15, 2026. Required fields vary by search feature; missing recommended fields are not automatically disqualifying. Accurate markup can support eligibility, but it does not guarantee stars, shopping placement or rankings. For the underlying terms, see Screpy's structured data guide.

1. Identify every source of Product markup

Open the public product page's source and search for application/ld+json. Inspect every block containing Product, ProductGroup or Offer, including nodes inside @graph. Also look for product microdata if your theme uses it. Save the HTML before editing.

Record which system produces each relevant node: WooCommerce, an SEO extension, the theme, a reviews integration or custom code. Comments and script IDs are clues; a controlled comparison on a staging copy can establish ownership when they are unclear.

The failure to fix is contradictory descriptions of the same offer. One block might say $49 and another $59. Multiple nodes alone are not proof of a defect: a legitimate variant graph contains several products, while separate scripts can reference the same entity through an @id.

The WooCommerce structured-data reference documents its native generator. Check your installed version and integrations before disabling it. An extension may build on core data rather than replace it; removing the foundation can remove useful markup too.

2. Check the right Google result requirements

Read the result type attached to an error. Product snippets and merchant listings use related markup, but their requirements differ.

Target Core requirements to check Important distinction
Product snippet Product name and at least one of offers, review or aggregateRating, including the chosen property's required fields An offer can support eligibility without customer ratings
Merchant listing Product name, product image and an Offer with an active price greater than zero and its currency An AggregateOffer is not a substitute for the required merchant Offer
Product variants The appropriate product requirements plus variant and group identification Grouping does not replace each variant's applicable product and offer data

Google's product snippet requirements and merchant listing requirements are the source of truth. The table is a starting point, not the complete property specification.

For merchant pricing, Google supports the documented priceSpecification structure as well as a direct offer price. Inspect the actual nesting before declaring a price absent.

Fix critical errors first. Evaluate recommended-property warnings against real catalog information. A product with no reviews does not need an invented rating, and a handmade item without an assigned GTIN does not need a fabricated barcode.

3. Match the product name and destination URL

Compare Product.name with the product heading and selected model. A schema name such as “Premium Hiking Boot” should not describe a page selling a replacement lace. Avoid adding promotional keywords that change the item's identity.

Open the product and offer URLs from the markup. They should resolve to the relevant product or purchasable variant, without sending a visitor to a category, login page or unrelated replacement. Confirm that the page is accessible to Google, without an unintended robots.txt block or noindex directive. Check the page's canonical URL too; investigate conflicts between the intended product URL, redirects and the canonical.

Google's product technical guidelines focus on a single product or variants of that product. A collection of unrelated products is not one product simply because a theme prints a Product object there.

Save the URL after redirects in your issue record. “The schema offer opens the category page” is a clear defect; “the URL looks different” needs investigation because legitimate variant parameters may explain the difference.

4. Reconcile the active price and tax display

Read the active price in the offer, then compare it with the amount shown for the same product, shopper market and variant. Use a logged-out session where the offer is intended for the public. Distinguish the product price from delivery charges and other separately described costs.

For example, a product showing $120 including applicable tax needs investigation if its markup presents $100 as that same public offer. Check WooCommerce's tax display settings, the price source used by the schema generator and any pricing integration. Do not assume the stored catalog price is the displayed customer price.

For variable products, ask a concrete question: do two variations with the same consumer price still have different stored prices because of their tax treatment? Compare the public offer for each variation rather than treating a backend price range as the answer.

Google defines the merchant offer price as the current active price. If both offers.price and offers.priceSpecification encode an active price, its documentation says it uses offers.price. Fix inconsistent values at their generating source rather than hiding one discrepancy with another block.

5. Verify currency and market-specific URLs

Check priceCurrency alongside the amount. It should use the three-letter currency code, such as USD or GBP, rather than a symbol. A correct numeric price in the wrong currency is still the wrong offer.

Repeat the comparison for each market you sampled. Open the market's direct URL in a fresh session and record the currency, price and selected variant before using a currency switcher. A cookie or location rule can make your own browser appear correct while a new visitor receives a different offer.

Google recommends distinct URLs when selling a product in different currencies. Review that currency guidance with your storefront's URL design.

If a US feed link opens a British-pound page, investigate the submitted URL and currency-routing behavior before editing keywords or adding schema properties. Keep each issue tied to its country, language, currency and actual destination so the developer can reproduce it.

6. Check sale prices and expiry dates

Use an on-sale product to confirm that the active offer reflects the price available now. Distinguish it from the crossed-out original price, a future promotion and a members-only price. More elaborate price specifications need to follow Google's merchant pricing examples.

If priceValidUntil is present, verify what its date means and whether it is still accurate. It describes how long the offer price is valid; it is not a field to extend arbitrarily until a warning disappears. Google notes that an expired value can stop a product snippet from displaying.

Ask the person maintaining the store to check a scheduled sale's start and end on a staging copy or during a planned promotion. Compare the visible amount, generated markup and any feed after the change. Record each capture time.

When an old sale price survives, investigate the product data, promotion schedule and relevant caches. A manual change to static JSON-LD is fragile if the next synchronization or page generation restores the old value.

7. Match availability to the purchasable item

Compare the offer's availability with the stock message and the item's actual purchase conditions. Inspect an unavailable product deliberately; an in-stock bestseller will not reveal a template that marks everything InStock.

Use the appropriate supported status for the real offer, such as OutOfStock, BackOrder or PreOrder. These states mean different things. A product available for future ordering is not necessarily in stock, and a product that cannot be ordered is not automatically a backorder.

For variable products, check the selected combination. A parent page can have stock in one size while the requested size is unavailable. The relevant offer must describe the item the URL and product selection identify.

Google lists supported availability values in the merchant offer specification. If stock data disagrees, trace the inventory integration and schema mapping before changing the markup manually. For a permanently retired item, review the page's purpose and offer together; do not keep an active offer merely to preserve a rich-result test.

8. Verify selected variations and product groups

Open a URL that preselects a specific size or color. Confirm that it loads the intended combination and that the visible price, stock, image and identifiers correspond to that variant. Test a second combination with a different price or availability.

A parent price range is not evidence that Google has the exact offer for every variation. Ask your implementer which model the store uses: a complete family graph, variant-specific pages, or another supported arrangement. Check it against Google's product variant documentation.

That documentation uses ProductGroup, hasVariant, variesBy and group identifiers to connect related products. Each variant needs a unique identifier, and its product and offer must meet the applicable result requirements.

Do not require the JSON-LD to change after every dropdown click. Google's single-page example already describes the variants in the graph while the visible selection changes. The important question is whether the graph accurately identifies the offers and their URLs.

Canonical handling also depends on the model: Google specifies one distinct canonical URL for a single-page product group, while its multi-page examples work differently. Avoid a blanket instruction to canonicalize every possible variant to itself or to remove every variant parameter.

9. Confirm brand and product identifiers

Compare brand, sku, gtin and mpn, where present, with reliable catalog or manufacturer records. A store SKU, manufacturer part number and GTIN are different identifiers; do not substitute one for another simply because a field is empty.

For branded goods, use the product's real brand. The retailer is not automatically the manufacturer. Check individual variations too: a barcode for a small blue shirt should not be copied onto every size and color.

Current WooCommerce code supports a native global identifier when valid, but the final mapping depends on the installed version and integrations. Check the actual output before assuming a custom field or plugin value is connected. Likewise, do not assume brand data is always absent from core-based output.

Google's merchant product properties explain supported identifiers and brand information. Use an assigned GTIN when one exists, and check it at its source. If a product genuinely has no assigned identifier, record that fact. Inventing a plausible number to remove a warning creates inaccurate product data.

10. Open the actual product image URLs

Copy the URLs from Product.image and open them without an authenticated store session. Check that each returns a usable image of the relevant product, rather than an error page, store logo or placeholder. For variant-specific images, confirm the pictured color or configuration.

Google's merchant listing documentation requires a product image and says its URL must be crawlable and indexable. Inspect access rules as well as the image itself. A photo that works for an administrator may still be inaccessible to Google because of authentication or blocking.

Check clarity and resolution. Google recommends multiple high-resolution images in its documented aspect ratios; that recommendation does not justify cropping away information the customer needs. Preserve a truthful view of the item.

If a valid photo fails to load, fix the image URL or delivery rule instead of removing the image property to hide the error. Screpy's WooCommerce image optimization tasks cover the related work of choosing, sizing and delivering product images. Schema validation and image performance remain separate checks.

11. Reconcile product reviews and rating counts

Compare the marked-up average, rating scale and counts with the product's visible review information. Check ratingCount and reviewCount according to what they describe; a star-only rating and a written review are not necessarily the same record.

Confirm that the reviews concern this product. A store-wide customer satisfaction score or Google Business Profile rating is not a product rating that can be copied onto every item.

Google's review snippet guidelines require review information about a specific item, prohibit aggregating reviews or ratings from other websites, and disallow fake or undisclosed incentivized reviews. The supporting rating information should be readily available to readers.

If an extension supplies ratings, document the source, moderation status and mapping to the product or variant family. After a legitimate review update, check that the displayed count and structured data agree.

Leave ratings absent when there are none. As check 2 explains, an appropriate offer can satisfy the alternative property requirement for a product snippet; an invented five-star rating is never the fix.

12. Compare shipping and return policies

Find the authoritative source of your shipping and return information before adding markup. It may be configured in Merchant Center or Search Console, described in organization-level structured data, or supplied as a product-specific exception.

Compare the destination countries, costs, delivery conditions, return window and fees with the published policy and the real offer. “Free shipping” for domestic orders over a threshold should not become unconditional worldwide free shipping in a copied schema block.

Google documents organization-level shipping policies and return policies. Product-level information is useful when a particular offer has different terms, such as an oversized delivery charge or a return exception.

Check precedence when several sources exist. Google's return policy documentation places Merchant Center or Search Console settings ahead of product-level markup, with organization-level markup below that. A correct page block may therefore not be the source Google uses.

Treat a missing recommended policy property as a reason to inspect your configuration, not permission to invent universal terms. Record which source needs the correction and verify the affected market and product exception afterward.

13. Retest changed pages and record the evidence

After a correction, capture the same sample URLs again. Include their variant parameters and market context. If the source was stale data, confirm that the visible page and generated markup now reflect the update; do not stop at an edited field in the product administration screen.

Use Google's Rich Results Test to inspect supported result types and critical issues. Use the Schema Markup Validator for the broader vocabulary and relationships. Compare the values yourself: neither validator establishes that a product can actually be bought at the stated price.

When Merchant Center is in use, compare its current product data with the same offer. Google's ecommerce product-data guidance explains that structured data and feeds can complement each other. A correct page does not automatically prove the latest feed has arrived.

Copy this repair record

Paste this CSV into a spreadsheet. The example is fictional; replace it with your actual evidence. Use one row per mismatch.

CSV
captured_at_utc,product_url,variant,market,field,expected,actual,source_to_check,owner,retest_at_utc,result
2026-11-15T12:00:00Z,https://shop.example/product/boot/?attribute_pa_size=8,size-8,US-USD,availability,OutOfStock,InStock,inventory-to-schema mapping,store developer,,open

Add links or filenames for the saved HTML, relevant product screenshot and validator result. Keep the original capture so the retest demonstrates what changed.

Close the issue when the generated values match the real offer, the relevant critical validation errors are resolved, and any remaining warnings have an honest documented explanation. Later, review the Product snippets and Merchant listings reports that are available in Search Console, including their crawl dates. Recheck the sample after changes to WooCommerce, the theme, schema extensions, prices or inventory integrations. Report the corrected data and observed validation state; Google's eventual display remains a separate outcome.

Related posts

Keep reading practical SEO guides from the Screpy blog.

View all posts