Two business professionals reviewing graphs and data on a tablet and paper report indoors.

Product Rich Results Missing? Check Merchant Listings and Schema

Product rich results disappear. Impressions in Search Console go up. CTR flattens. Revenue conversations get tense.

Before you blame AI summaries or a ranking drop, separate two issues: eligibility for rich results and actual ranking and click performance. In 2026, most WooCommerce problems I see are eligibility and data-alignment failures—not penalties.

Merchant Listings vs Product Snippets: What the Reports Actually Measure

Google documents Product structured data requirements in Google Search Central’s Product structured data guide. Required and recommended properties determine whether a page is eligible for product rich results—not whether it will rank or earn clicks.

The Product results report in Search Console (documented in Search Console Help) classifies items as Valid, Valid with warnings, or Invalid based on structured data detection. It diagnoses markup issues. It does not measure performance, impressions, or traffic impact.

Separately, Google documents Merchant listings structured data for enhanced shopping experiences. The corresponding Merchant listings report in Search Console tracks issues specific to merchant listing eligibility. This is distinct from the Product results report.

Key distinctions:

  • Product results report: Is your on-page Product/Offer markup valid and eligible?
  • Merchant listings report: Are you eligible for merchant listing experiences, and are there listing-specific issues?
  • Ranking/CTR: Driven by query intent, competition, layout shifts, ads, and AI features—not guaranteed by valid schema.

Google’s documentation is explicit: adding structured data makes pages eligible for enhancements. It does not guarantee rich results or improved ranking.

Also separate on-page structured data from Merchant Center feeds. They are related systems but not the same. Merchant listings documentation makes clear that structured data helps Google understand product details, while feeds in Merchant Center are another data source. When price, availability, currency, or identifiers conflict between feed and page, eligibility and trust signals can degrade.

Common WooCommerce Failures That Kill Eligibility

WooCommerce outputs Product schema by default, as documented in WooCommerce’s structured data guide. Problems usually come from customization, plugins, or theme overrides.

Here are the repeat offenders:

  • Duplicate Product schema: SEO plugins, theme builders, or custom JSON-LD inject a second Product object. Conflicting price or availability fields cause Invalid items.
  • Missing required Offer properties: Google’s Product documentation requires properties like price and availability within an Offer for many product experiences. Missing or malformed values trigger errors.
  • Price/availability mismatch: Structured data must reflect what users see. If the visible price differs from the JSON-LD priceCurrency/price, eligibility can be affected.
  • Variant confusion: Variable products often output parent-level schema while prices live at the variant level. Inconsistent Offer modeling leads to warnings or ineligibility.
  • Canonical misconfiguration: If variants canonicalize incorrectly, Google may index a URL that lacks complete Offer data.
  • noindex or robots blocks: If the canonical product URL is blocked, structured data cannot be processed for rich results eligibility.

Reference Schema.org’s Product and Offer vocabulary to confirm property names and expected structure. Typos in availability values or currency codes are more common than most teams think.

One more reality check: rising impressions with flat or declining CTR can occur even when eligibility is intact. Search layout shifts, merchant experiences, ads, and AI-generated summaries can redistribute clicks without any structured data error.

What to do next

  1. Open Search Console → Product results report. Review Invalid items first. Click into a sample URL and inspect which property is missing or malformed.
  2. Check Merchant listings report separately. Do not assume Product report errors and Merchant listings errors are identical.
  3. Inspect one affected product URL live. Use URL Inspection to confirm it is indexed, canonicalized correctly, and not blocked.
  4. View page source. Confirm only one primary Product object exists. Remove duplicate schema from themes or plugins.
  5. Validate required Offer fields. Confirm price, priceCurrency, and availability match visible content exactly.
  6. Compare feed vs page data. If you use Merchant Center, confirm price, availability, and identifiers align with on-page structured data.
  7. Re-test after fixes. Use Search Console’s validation workflow to track resolution status.

Treat structured data as infrastructure. It reduces friction in organic visibility and shopping experiences, but it is not a one-time SEO toggle. For WooCommerce operators, periodic schema audits belong on the same checklist as backups, plugin updates, and feed diagnostics.

If your rich results disappeared, start with eligibility. Prove or disprove a markup issue before you attribute the change to ranking volatility or AI surfaces.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.