Which Product Report Should Your WooCommerce Store Check?

If a shopper can complete a purchase on your WooCommerce product page, start with Search Console’s Merchant listings workflow. If the page does not let shoppers purchase the product directly, consider Product snippets, subject to Google’s requirements. The two experiences overlap, so the right report to investigate is a starting point—not a promise about how the page will appear in Search.

Choose the report based on what shoppers can do

Google describes Product snippets as suited to product pages where people cannot directly purchase the product, and Merchant listings as suited to pages where they can. Its Introduction to Product structured data also explains that the experiences overlap: meeting Merchant listing product-information requirements can make a page eligible for Product snippets too. Eligibility for either experience does not guarantee a particular Search appearance.

In Search Console, look in the Shopping section for separate Product snippets and Merchant listings rich result reports, if Google has found the relevant structured data for your property. The report to inspect should fit the page’s purchase path, but Google’s findings determine which reports are available. Schema.org’s Product and Offer types describe the vocabulary used to mark up products and offers; using those terms by itself does not establish eligibility for a Google Search feature.

Trace a mismatch from the page to Google’s report

Check the live product page as a shopper. Note the product name, price, currency, and availability shown on the page. Confirm whether the shopper can actually complete a purchase there.
Inspect the rendered structured data. Check the deployed page’s rendered HTML or DOM for its Product and Offer details. Compare the marked-up name, price, currency, and availability with what the page shows. WooCommerce output can vary with the active theme, extensions, and configuration, so inspect the page rather than assuming a particular plugin generates its markup.
Run Google’s Rich Results Test. Test the deployed URL, or the markup when appropriate, and check whether Google identifies the intended supported product feature. Review any errors or warnings and correct the markup or the system generating it. A clean test supports markup validity; it does not show that Google has crawled or indexed the latest version.
Open the matching Search Console Shopping report. Check the Product snippets or Merchant listings report that fits the page’s purchase path. Review detected item details and listed issues; use them to identify whether Google’s reported structured data agrees with the page and test output.
Use URL Inspection for the individual page. If the URL is missing from a report or the report seems inconsistent with your test, inspect that specific URL. Google’s Merchant listing structured data guidance includes validating with the Rich Results Test, checking a deployed page with URL Inspection, and allowing time for recrawling and reindexing after changes.

Hypothetical example: a desk lamp listed at USD 49.00

Suppose a WooCommerce product page visibly offers a desk lamp for USD 49.00 and says it is in stock. First confirm the product name, price, currency, and availability displayed to shoppers. Then compare those details with the rendered Product and Offer markup and the Rich Results Test output. If the page says “in stock” but the rendered Offer says something different, find which part of the site generates the conflicting value and correct it at its source. Retest the deployed page before using Search Console to check what Google reports.

This is a hypothetical troubleshooting example, not a claim about a particular store or WooCommerce extension. A theme, extension, or configuration may affect the output, so verify the actual page rather than relying on an assumed markup setup.

Read Search Console reports as evidence, not a full URL inventory

Search Console’s Shopping reports and tools documentation explains that the Shopping section may contain separate product reports depending on the structured data Google found. A report may be absent because Google has not found the relevant structured data or because its report sample lacks entity data. Absence alone does not prove that every product URL lacks markup or that the property is restricted.

The Rich result report overview also notes that reports show a sample of detected items and count items rather than pages. A URL missing from a report may still need an individual check in URL Inspection. Use report totals and issue details to monitor what Google has detected, but do not treat them as a complete count of product URLs or attribute a change in report totals to a markup edit without evidence that rules out other causes.

Verification checklist

The purchase path on the page points you to the relevant workflow: direct purchase suggests Merchant listings; no direct purchase points toward Product snippets, subject to Google’s requirements.
The rendered product name, price, currency, and availability agree with the information shoppers see.
The Rich Results Test identifies the intended supported product feature without critical errors.
The relevant Search Console report shows a detected item, or URL Inspection provides page-specific evidence about what Google sees.
After a correction, you check the deployed page and allow time for Google to recrawl and reindex it; a valid test alone does not establish that this has happened or guarantee a Search display.

When theme, extension, and product-data output need to work together, Splinternet Marketing’s SEO services can help implement and validate structured data, check page-level output, and monitor Search Console evidence so improvements can be maintained over time.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.