Why Does Product Schema Appear in Two Search Console Reports?

A WooCommerce product URL appearing in both Search Console’s Merchant listings and Product snippets reports does not, by itself, prove that the page has duplicate Product markup. Google documents different experience requirements for the reports and says the Merchant listings report includes checks for Product snippets that use Offer markup. That relationship does not establish that every product URL should appear in both reports—or that an overlap is always harmless. Inspect the report details and the page’s detected data before changing markup.

What the two reports describe

Google describes Merchant listings as applying to pages where shoppers can buy products. Product snippets can apply to other product-related pages, such as reviews and aggregator pages. Google also says Product rich results are intended for pages focused on one product or variants of the same product, rather than product-category or listing pages. Its Product Snippet Structured Data guidance explains that the Merchant listings report includes checks for Product snippets using Offer markup; the Product snippets report is still relevant for non-merchant-listing pages. The Merchant Listing Structured Data guidance describes the page types and requirements for these experiences.

These are reporting distinctions, not a diagnosis of what is currently on a particular URL. Search Console’s rich-result report documentation says reports contain samples, and their counts represent structured-data items, not a count of affected pages. An issue can affect multiple items on one page, and a URL not listed in a report can still be checked with URL Inspection. A report entry alone does not show every structured-data item or necessarily reflect the exact markup Google would find on the page now.

Inspect the URL before changing WooCommerce settings

Compare both reports. In Search Console, open Merchant listings and Product snippets. Compare the affected URLs and the issue details or examples in each report. Note what each report says is invalid or eligible; do not treat the number of report entries as the number of duplicate products or pages.
Test the exact product URL. Run the URL through Google’s Rich Results Test. Review each detected Product and Offer rather than stopping at the overall pass or error summary. Compare the product name, price, currency, and availability in the detected data with the offer shoppers can see on the page.
Check what Google can access. Use Search Console URL Inspection to review the deployed page’s Google-rendered or crawled view and the structured-data items Google detects. Confirm the page is accessible to Google and is not blocked by robots.txt, marked noindex, or behind a login. A report may reflect an earlier crawl, so compare its data with the current page rather than assuming they are identical.
Trace each entity to its source. Record which Product and Offer entities appear, what values they contain, and which WooCommerce plugin, theme, or custom implementation emits each one. The output can vary with the store’s theme, plugins, custom code, product type, and rendering behavior. Inspect the actual page and implementation before changing settings; do not assume a particular component generated the markup.

A practical decision rule

Hypothetical example: A WooCommerce product page visibly offers one in-stock item for $40. Inspection finds two Product entities, and one contains an outdated price. The actionable defect is the conflicting entity or Offer data—not simply that the URL appears under two report names. Trace the stale entity to the component emitting it, correct that source, then test the page again.

If inspection instead finds one coherent Product entity with current Offer data, do not remove markup just to force a report to be empty. Review the issue details in each report and consider whether Search Console is reporting an earlier crawl. If entities conflict or a value is stale, identify the emitting source and correct that implementation before retesting. Schema.org’s Product definition describes the vocabulary, but using a Schema.org Product type alone does not establish eligibility for a Google rich result.

Verify the correction and allow for recrawling

Use Google’s Merchant Listing Structured Data guidance for the recommended Rich Results Test and URL Inspection workflow. After a change, check that the intended product and offer appear in the rendered output, that price, currency, and availability match the visible offer, that the Rich Results Test has no relevant critical errors, and that URL Inspection can access the page. A clean test does not prove Google has recrawled or indexed the updated page, and it does not guarantee that a rich result will appear. Google notes that recrawling and reindexing can take time, so allow for that before judging whether Search Console’s reports have changed.

When markup has more than one possible source, a careful review can help prevent a fix in one plugin from leaving a conflicting entity elsewhere. Splinternet Marketing’s SEO services can help trace WooCommerce Product and Offer output, validate the rendered page, and monitor the relevant Search Console reports so the implementation can be maintained as the store changes.

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.