Merchant Listings Report (Google Search Console)

TL;DR — The Merchant listings report in Google Search Console checks the product data (the structured data) on your own pages and tells you whether Google can use it for the free shopping features in Search — things like Popular Products and the shopping box in Google Images. It groups items into valid and invalid, and separately flags smaller non-critical issues on otherwise-valid items. It is not the same as Google Merchant Center’s own reports, and you don’t need a Merchant Center account for it to work. Being eligible isn’t a guarantee your listing is actually shown.

What this report is

Open Google Search Console, look in the Shopping section of the left menu, and you’ll find Merchant listings. It does one job: it reads the product markup Google found on your pages and reports whether that markup is good enough to make your products eligible for the free, enhanced shopping results in Google Search.

Those enhanced results are called merchant listing experiences. They include Popular Products carousels, the Shopping Knowledge Panel, and the shopping overlays you see in Google Images and Google Lens. This report is your scorecard for the code that powers them.

Valid, invalid, and the issues inside each

Google groups the structured-data items this report finds into two states:

• Valid — no critical issue found; the item is eligible. A valid item can still carry smaller, non-critical issues — missing recommended details (like availability or a product identifier) that would make the listing richer without blocking eligibility.
• Invalid — at least one critical issue (something required is broken or missing), so the item isn’t eligible.

You want valid items rising over time and invalid items near zero. Non-critical issues on valid items aren’t urgent, but clearing them usually earns better-looking results. And “eligible” isn’t the same as “shown” — a valid item doesn’t guarantee Google actually displays it, ranks it, or sends it traffic.

The confusing part: this is not Merchant Center

This is the mistake almost everyone makes. Google Merchant Center is a separate product with its own reports about your product feed — the file of products you upload. The Merchant listings report in Search Console is about the structured data on your web pages instead. They’re two different systems, and one can look healthy while the other complains.

Here’s the good news that surprises people: you do not need a Merchant Center account to appear in the Merchant listings report or to be eligible for those free shopping features. Valid product markup on your pages is enough. (That changed back in 2022 — before then, these experiences mostly needed a Merchant Center feed.)

Who qualifies

There’s one big catch on eligibility: the shopper has to be able to buy the product on your site. If you’re an affiliate or comparison site that sends people elsewhere to buy, Google doesn’t count you as a “merchant” here — even if your markup is technically perfect. That single rule stops a lot of publishers from ever showing up in this report.

Want the full version — the exact required fields, how to read the trend chart, how this differs from the Product snippets report, and a step-by-step fix workflow? Switch to the Advanced tab.

TL;DR — The Merchant listings report (Search Console → Shopping) validates your pages’ Product/Offer structured data for free merchant listing experiences — Popular Products, Shopping Knowledge Panels, and shopping surfaces in Google Images and Lens. It’s an item-level enhancement report: items are classified valid or invalid based on whether a critical issue is present, and non-critical issues are broken out separately as enhancement opportunities on otherwise-valid items — a page can hold more than one item, and one item can carry more than one issue, so item/page/issue counts aren’t interchangeable. It validates on-page markup, not your Merchant Center feed, and since September 2022 needs no Merchant Center account. Eligibility requires the shopper to complete a purchase on your site; affiliate/redirect sites are explicitly excluded. It’s distinct from Product snippets (broader; accepts AggregateOffer) and Merchant opportunities (feed-driven; unlocked by association). Required fields are minimal — name, image, offers.price > 0, priceCurrency — but the recommended ones are where non-critical issues and lost surfaces come from. A drop in valid items without a matching rise in invalid items usually means the markup stopped being found at all. None of this — valid markup, a clean report, or a passed validation — guarantees display, ranking, or traffic.

What it is, and where it lives

The Merchant listings report sits under the Shopping section of Google Search Console’s navigation. In Google’s own words, “Merchant listings are an extension of the Product snippet items that enable more full-featured search results and always include a price.” It validates the Product and Offer structured data Google crawled on your pages and reports items as valid or invalid, with issues broken out as critical or non-critical, trended over time.

The experiences it feeds are the free ones. Per Google’s launch announcement, “Merchant listing experiences offer enhanced experiences including the Shopping Knowledge panel and Popular Products, as well as shopping experiences in Google Images and Google Lens.” This is not about Shopping ads, and it’s not a paid surface — it’s your organic eligibility for those enhanced shopping results. Eligibility is not the same as a guarantee: Google still decides whether, when, and where a given item is actually displayed, and validating a fix does not by itself guarantee display, ranking, or traffic.

How items, pages, and issues are classified — and counted

Like Search Console’s other structured-data (rich result) reports, this one scores the item — the piece of Product/Offer markup — not the page and not your site as a whole. Google simplified the classification scheme in 2022: instead of a three-way errors/warnings/valid split, an item with at least one critical issue is invalid; an item with no critical issue is valid, even if it still has smaller non-critical issues (Google: “pages or items with critical issues are labeled something like invalid; pages or items without critical issues are labeled something like valid” — Search Console item classification update, Search Central Blog, June 2022). Non-critical issues are enhancement opportunities — missing recommended fields — not blockers.

That item-level scoring also means the counts you see aren’t interchangeable: a single page can carry more than one structured-data item (for example, several Product items on one page), and a single item can carry more than one issue at once. Don’t read “N invalid items” as “N broken product pages” — check the affected-examples list before assuming a 1:1 mapping to pages or products.

It validates your markup, not your feed

The single most important distinction: this report checks structured data on your web pages (crawled HTML), not the product feed you submit to Google Merchant Center. Merchant Center has its own product-level diagnostics for the feed; those are a separate system with a separate fix path. A site can show valid markup in Search Console while Merchant Center flags feed problems, or the reverse — which is exactly the confusion that shows up over and over in Google’s own community forums (“invalid in Search Console but valid in Merchant Center”). If you internalize one thing from this article: Search Console = your page markup; Merchant Center = your feed.

A valid result in one system is not evidence the other is valid — check each independently rather than assuming one implies the other.

You don’t need a Merchant Center account

This is the entire point of the September 2022 change that created the report. The old single “Product structured data” report was split into two — Merchant listings and Product snippets — both grouped under the new Shopping section. And eligibility was expanded. Google’s announcement is explicit: “Initially, product snippets in Google search results were primarily powered by schema.org Product structured data, and merchant listing experiences were primarily powered by product details supplied via a Google Merchant Center feed. Now merchants can be eligible for merchant listing experiences by providing product data on web pages without a Google Merchant Center account.”

So no, you don’t need Merchant Center for this report to populate. A Merchant Center association (Settings → Associations) is a separate, optional step that unlocks a different report — Merchant opportunities — which I’ll cover below.

Merchant listings vs. Product snippets vs. Merchant opportunities

Most existing coverage only compares two of these. There are three, and conflating them is the most common error I see:

The technical line between the first two is sharp and documented: “Product snippets accept an Offer or AggregateOffer but merchant listings require an Offer as the merchant has to be the seller of the product in order to be eligible for merchant listing experiences.” That’s the biggest single differentiator — if your product uses AggregateOffer (a price range from multiple sellers), it can qualify for Product snippets but not merchant listings.

Eligibility: who counts as an “online merchant”

Google defines it plainly: “An online merchant is a site that sells physical goods or services directly to consumers (not to other businesses) on that site.” And the exclusion is explicit — “Websites that redirect users to other sites (affiliate sites), or don’t allow purchase completion on the site, are not considered online merchants for Search Console’s reporting purposes.”

The structured-data doc says the same from the page angle: “Only pages where a shopper can purchase a product are eligible for merchant listing experiences, not pages with links to other sites that sell the product.” So affiliate and lead-gen sites are disqualified regardless of how clean their markup is. This trips up a lot of publishers who wonder why perfectly valid Product schema never earns them a merchant listing — the answer is usually that you can’t complete a purchase on the page.

One more page-level rule worth knowing: “Product rich results only support pages that focus on a single product (or multiple variants of the same product). For example, ‘shoes in our shop’ is not a specific product.” Category pages don’t qualify; product (and variant) pages do.

Required vs. recommended structured data

The floor to appear at all is low. For Product you need name, image, and an offers object. For that Offer you need price and priceCurrency — and note the price rule: “Unlike product snippets, merchant listing experiences require a price greater than zero.” (The price may sit inside a priceSpecification instead of directly on the Offer.)

The recommended properties are where most of the value — and most of the report’s non-critical issues — live: availability, itemCondition, shippingDetails, hasMerchantReturnPolicy, aggregateRating, review, brand, description, and a product identifier (gtin/sku/mpn). On GTINs, Google’s guidance: “While you can use the generic gtin property for all GTINs, we recommend that you use the most specific GTIN that applies to your product, as this is the most accurate representation of the product.” Missing or malformed values here are the usual source of non-critical issues like a missing gtin or an unrecognized availability.

Variants — a common mistake. To represent size/color/material variations, use hasVariant/variesBy (or inProductGroupWithID), not AggregateOffer. AggregateOffer is for a range of prices from multiple sellers, which is a Product snippets thing — and, as the ProductGroup schema pattern shows, it’s the wrong tool for describing one product’s variants.

2025 update — energy labels. Google now prefers the newer hasCertification property over the older hasEnergyConsumptionDetails for energy-efficiency-type certifications: “While we continue to support the earlier markup pattern, we recommend using the new hasCertification property instead, if possible.” If you sell appliances or electronics in markets with energy labels, migrate to hasCertification (with issuedBy and name on the Certification object).

Reading the report — the trend chart and the “dropped valid items” trap

The report trends valid items and invalid/issue-affected items over time. The healthy pattern is valid items rising while invalid items stay flat. The diagnostic that catches people out is a drop in valid items that isn’t matched by a rise in invalid items. That usually doesn’t mean your markup got worse — it means the structured data stopped being found at all on those pages: it was removed, blocked by a noindex/robots directive, or gated behind JavaScript that Google didn’t render. Different diagnosis, different fix. Confirm with the URL Inspection tool: look at the rendered HTML and check whether the Product markup is actually present.

Whatever the trend shows, treat it as a markup-eligibility signal, not a performance guarantee. A valid item is eligible to be used for a merchant listing experience; it is not a promise that Google will display, rank, or send traffic to it — that depends on factors this report doesn’t measure. If you want to know whether a merchant listing actually appeared and was seen, that’s a Performance-report question (filtered to the relevant search appearance), not a Merchant listings-report question, and even Performance data only reflects appearances Google observed, not feed status, Shopping-tab approval, or revenue.

This connects to a real caveat for JS-heavy stores: dynamically-injected markup gets crawled less frequently and less reliably, which matters most for volatile data like price and stock. If your prices change often and your markup is client-side rendered, expect this report to lag reality.

Fixing common issues — the triage workflow

When you have critical or non-critical issues, work them in this order:

1. URL Inspection on an affected URL → View crawled page / Test live URL to confirm what Google actually rendered. If the Product markup isn’t in the rendered HTML, your problem is rendering/blocking, not the schema itself.
2. Rich Results Test on the live URL to see the exact property-level issues Google reads, independent of the report’s aggregation.
3. Fix at the source — the template/theme, or the app that injects the markup. Missing price > 0, missing image, invalid availability enum, and missing identifiers are the frequent offenders.
4. Validate fix in the report once the cause is actually fixed. Validation rechecks affected examples over time as Google recrawls — it’s not instantaneous, and Google doesn’t publish a fixed turnaround for it. A completed validation confirms the markup issue is resolved; it still doesn’t guarantee the item is displayed. Clicking it before you’ve fixed the root cause just wastes the cycle.

The Merchant Center association (a different report)

If you do link Merchant Center via an association, you unlock the Merchant opportunities report — not more Merchant listings data. Google describes its two enhancements: “With the first enhancement, merchants will receive notifications when products stop appearing on the Shopping tab due to any issues” and “The second enhancement shows merchants opportunities to increase clicks and improve ranking of products on Google.” Useful, but a separate feature — don’t confuse a Merchant opportunities recommendation with a Merchant listings structured-data issue.

A note on the naming

The “Merchant listings” name is arguably misleading now, and I’m not the only one who thinks so. Independent technical SEO Brodie Clark has made the case that since eligibility no longer depends on a Merchant Center feed, a clearer label would be “free product listings” (see his Merchant listings write-up). The underlying point is sound: the report name still implies a Merchant Center dependency that hasn’t existed since 2022.

Bing’s equivalent (there isn’t a direct one)

Bing Webmaster Tools has no aggregate report named “Merchant listings.” The closest analog is the per-URL Markup Validator in Bing’s structured-data guidance, which validates JSON-LD/Microdata/RDFa on a single URL — not a site-wide valid/invalid dashboard. Microsoft’s shopping feed diagnostics live separately in Microsoft Merchant Center. If you’re keeping the Bing side clean, the practical move is valid Product markup plus fast re-crawl via IndexNow — Bing frames those two together for Shopping.

This report is a sibling of the other Google Search Console report explainers on this site — the Page Indexing (Index Coverage) report, the Video indexing report, and the URL Inspection tool — and it leans on the same structured-data validation you’d use for any product rich result.

AI summary

A condensed take on the Advanced version:

• The report (Google Search Console → Shopping → Merchant listings) validates your pages’ Product/Offer structured data for free merchant listing experiences: Popular Products, Shopping Knowledge Panel, and shopping surfaces in Google Images and Lens. It’s an item-level report: items are classified valid or invalid based on whether a critical issue is present, with non-critical issues broken out separately as enhancement opportunities.
• Counts aren’t 1:1. A page can hold more than one structured-data item, and one item can carry more than one issue — item, page, and issue counts are different numbers.
• It validates on-page markup, not your feed. Google Merchant Center’s own diagnostics cover the feed — a separate system with a separate fix path. A site can be valid in one and flagged in the other; neither result implies the other.
• No Merchant Center account required. Since September 2022, valid Product markup on purchasable pages is enough: “Now merchants can be eligible for merchant listing experiences by providing product data on web pages without a Google Merchant Center account.”
• Three different reports. Merchant listings (requires an Offer, price > 0), Product snippets (broader; accepts AggregateOffer), and Merchant opportunities (feed-driven; needs a Merchant Center association). Don’t conflate them.
• Eligibility requires the shopper to buy on your site — affiliate/redirect sites are explicitly excluded, regardless of markup quality. Category pages don’t qualify; single-product (and variant) pages do.
• Required fields are minimal (name, image, offers.price > 0, priceCurrency); recommended fields (availability, gtin/sku/mpn, itemCondition, hasMerchantReturnPolicy, shippingDetails) unlock richer surfaces and are where most non-critical issues originate. Use hasVariant/variesBy for variants, not AggregateOffer. Prefer hasCertification over hasEnergyConsumptionDetails.
• Reading it: valid rising + invalid flat = healthy. Valid items dropping without a rise in invalid items = markup no longer being found (removed, blocked, or JS-gated) — check URL Inspection.
• None of this guarantees display. Valid, clean, or validated markup makes an item eligible — it doesn’t guarantee Google displays, ranks, or sends traffic to it.
• Fix flow: URL Inspection → Rich Results Test → fix at the source → Validate fix (fix the cause first; Google doesn’t publish a fixed turnaround for validation). Bing has no direct equivalent — per-URL Markup Validator only.

Official documentation

Primary-source documentation from Google and Bing.

Google

• Shopping reports and tools – Search Console Help — the umbrella Help page defining the Shopping section, the “online merchant” eligibility rules, and the affiliate exclusion.
• How To Add Merchant Listing Structured Data – Search Central docs — the technical reference: required vs. recommended Product/Offer properties, the Offer-vs-AggregateOffer rule, the price-greater-than-zero rule, GTIN guidance, and hasCertification.
• New Search Console Merchant Listings report – Search Central Blog (Sept. 2022) — the launch announcement: the report split, the “no Merchant Center account needed” expansion, and the decision guidance on which report to check.
• Simplifying Search Console reports with an updated item classification – Search Central Blog (June 2022) — the source for the current valid/invalid, critical/non-critical item classification this report (and the other structured-data reports) uses today.
• Associate Search Console to Merchant Center – Search Central Blog (Sept. 2023) — the separate association feature and the Merchant opportunities enhancements.
• Associations – Search Console Help — how to associate a Merchant Center account (Settings → Associations).
• Structured Data for Ecommerce Sites – Search Central docs — the broader ecommerce structured-data reference.

Bing / Microsoft

• Marking Up Your Site with Structured Data – Bing Webmaster Tools Help — Bing’s structured-data guidance and the per-URL Markup Validator (Bing’s closest analog; no aggregate report).
• IndexNow — the push protocol for fast re-crawl, which Bing pairs with structured data for Shopping.

Quotes from the source

On-the-record statements from Google. Each link is a deep link that jumps to the quoted passage on the source page.

Google Search Console Help — what merchant listings are and who qualifies

• “Merchant listings are an extension of the Product snippet items that enable more full-featured search results and always include a price.” — Search Console Help. Jump to quote
• “An online merchant is a site that sells physical goods or services directly to consumers (not to other businesses) on that site.” — Search Console Help. Jump to quote
• “Websites that redirect users to other sites (affiliate sites), or don’t allow purchase completion on the site, are not considered online merchants for Search Console’s reporting purposes.” — Search Console Help. Jump to quote

Google Search Central Blog — the September 2022 expansion

• “Now merchants can be eligible for merchant listing experiences by providing product data on web pages without a Google Merchant Center account.” — Search Central Blog, Sept. 2022. Jump to quote
• “Merchant listing experiences for web pages that allow shoppers to buy a product on the site.” — Search Central Blog, Sept. 2022. Jump to quote
• “Check the merchant listings report for your pages selling products.” — Search Central Blog, Sept. 2022. Jump to quote

Google Search Central docs — the structured-data rules

• “Product snippets accept an Offer or AggregateOffer but merchant listings require an Offer as the merchant has to be the seller of the product in order to be eligible for merchant listing experiences.” — How To Add Merchant Listing Structured Data. Jump to quote
• “Unlike product snippets, merchant listing experiences require a price greater than zero.” — How To Add Merchant Listing Structured Data. Jump to quote
• “Only pages where a shopper can purchase a product are eligible for merchant listing experiences, not pages with links to other sites that sell the product.” — How To Add Merchant Listing Structured Data. Jump to quote

Google Search Central Blog — the 2022 item classification change (valid/invalid, critical/non-critical)

• “We are grouping the top-level item (a rich result for the rich result reports, a page or URL for the other reports) into two groups: pages or items with critical issues are labeled something like invalid; pages or items without critical issues are labeled something like valid.” — Simplifying Search Console reports with an updated item classification, Search Central Blog, June 2022. Read the post
• “To reiterate, this is only a reporting change in Search Console; there are no changes in how Google Search crawls, indexes, or serves your pages.” — Same post. Read the post

Google Search Central Blog — the Merchant Center association (a different report)

• “With the first enhancement, merchants will receive notifications when products stop appearing on the Shopping tab due to any issues.” — Search Central Blog, Sept. 2023. Jump to quote
• “The second enhancement shows merchants opportunities to increase clicks and improve ranking of products on Google.” — Search Central Blog, Sept. 2023. Jump to quote

Which report should I be looking at?

Work top-down; stop at the first match.

1. Do you sell products directly on your own site (shopper completes the purchase there)?

• No — you’re an affiliate/comparison/lead-gen site, or you send buyers elsewhere. → You’re not an “online merchant” for this report. You won’t qualify for merchant listings no matter how clean your markup is. If you publish product reviews or aggregate product info, check the Product snippets report instead.
• Yes → continue.

2. What are you trying to diagnose?

• “My product markup is invalid / has issues on my pages.” → Merchant listings report (Search Console → Shopping). This is on-page Product/Offer structured data. Fix in the page template, then Validate fix.
• “My uploaded product feed is disapproved / has feed errors.” → That’s Google Merchant Center’s own diagnostics — a different product, about your feed, not your page markup.
• “I want growth recommendations (shipping, returns, ratings, payment methods).” → Merchant opportunities report — but you must first associate Merchant Center with your Search Console property (Settings → Associations).

3. Merchant listings shows valid items suddenly dropping — with no rise in invalid items?

• → Don’t assume the markup got worse. The structured data probably stopped being found: removed from the template, blocked by noindex/robots, or gated behind JavaScript Google didn’t render. Check URL Inspection on an affected URL and confirm the Product markup is in the rendered HTML.

4. Your product has size/color/material variations — how do you mark them up?

• → Use hasVariant/variesBy (or inProductGroupWithID). Not AggregateOffer — that’s a multi-seller price range and belongs to Product snippets, not merchant listings.

5. Your item shows valid in merchant listings but you want it richer?

• → Add the recommended properties: availability, itemCondition, a product identifier (gtin/sku/mpn), shippingDetails, hasMerchantReturnPolicy, aggregateRating. Non-critical issues here aren’t blocking, but clearing them unlocks the fuller experiences — though even a fully valid item isn’t a guarantee Google displays it.

Merchant listings — the fast reference

The three reports, at a glance

Required vs. recommended (merchant listings)

Rules that catch people out

• Price must be greater than zero (may be nested in priceSpecification).
• Offer only for merchant listings — AggregateOffer is Product-snippets-only.
• Variants → hasVariant/variesBy or inProductGroupWithID, not AggregateOffer.
• Single-product (and variant) pages only — category pages don’t qualify.
• Affiliate/redirect sites are excluded — purchase must complete on your site.
• Energy labels → prefer hasCertification over hasEnergyConsumptionDetails.
• GTIN in numerical form — Google doesn’t support the URL form.
• A page can hold multiple items, and one item can carry multiple issues — item, page, and issue counts aren’t the same number.
• Valid/eligible ≠ displayed — no report state guarantees display, ranking, or traffic.

Item classification (current, since June 2022)

• Valid = no critical issue. Invalid = at least one critical issue.
• Critical issue = blocks eligibility. Non-critical issue = enhancement opportunity on an otherwise-valid item.

Reading the trend

• Valid ↑, invalid flat = healthy.
• Valid ↓ with no rise in invalid items = markup no longer found (removed / blocked / JS-gated) → check URL Inspection, not the schema.

Fix order: URL Inspection → Rich Results Test → fix at the source → Validate fix (fix the cause first; no published fixed turnaround).

Merchant listings triage checklist

Run this before and after touching your product markup:

• Confirm you’re actually eligible: shoppers can complete a purchase on your site (not an affiliate/redirect site).
• You’re in the right report: Shopping → Merchant listings (page markup), not Merchant Center feed diagnostics.
• Required fields present on every product: name, image, offers with price > 0 and priceCurrency.
• Using an Offer, not AggregateOffer (which would push you to Product snippets instead).
• Variants marked with hasVariant/variesBy or inProductGroupWithID.
• Recommended fields added where you can — availability, itemCondition, gtin/sku/mpn, shippingDetails, hasMerchantReturnPolicy, aggregateRating — to clear non-critical issues and unlock richer surfaces.
• GTINs in numerical form, using the most specific GTIN for the product.
• Energy-label products migrated from hasEnergyConsumptionDetails to hasCertification where applicable.
• Checked whether an “invalid” count reflects fewer pages than it looks like — remembered a page can hold multiple items and one item can carry multiple issues.
• For any drop in valid items, checked URL Inspection to confirm the markup is still present in the rendered HTML (not removed, blocked, or JS-gated).
• Validated a real issue in the Rich Results Test before assuming the report is wrong.
• Fixed the underlying cause before clicking Validate fix.
• Didn’t treat “valid” or “validation passed” as a promise the item is actually displayed, ranked, or driving traffic.

The mental models

1. Page markup vs. feed — two systems, never one. Merchant listings (Search Console) validates the structured data on your pages. Merchant Center validates your feed. They can disagree, and that’s normal. Diagnose the right system before you “fix” anything.

2. Three reports, not two. Merchant listings (buy-on-site, requires Offer), Product snippets (broader, accepts AggregateOffer), Merchant opportunities (feed-driven, needs an association). Know which one owns the thing you’re looking at.

3. Eligibility is about the transaction, not the schema. The gating question isn’t “is my markup valid?” — it’s “can a shopper buy this product on this page?” Affiliate/redirect sites and category pages fail that test regardless of markup quality.

4. Required unlocks appearing; recommended unlocks richer. Minimum fields make you eligible. The recommended fields (availability, identifiers, shipping, returns, ratings) are what earn the fuller experiences — and they’re where most non-critical issues come from.

5. A drop in valid items is a “found?” question, not a “worse?” question. Valid ↓ without invalid items ↑ almost always means the markup stopped being found — removed, blocked, or JS-gated — not that the schema degraded. Reach for URL Inspection, not the schema editor.

6. Item ≠ page ≠ issue, and eligible ≠ displayed. One page can carry several items; one item can carry several issues — don’t read report counts as product counts. And a fully valid item is eligible, not guaranteed to be shown, ranked, or to drive traffic.

Prove a merchant-listing markup fix took effect

Validate the live Product and Offer markup

Test to run — Test an affected product URL in Google’s Rich Results Test after deploying the schema change. Expected result — merchant-listing eligibility is detected, required Product and Offer fields parse, and the fixed critical issue is absent. Failure interpretation — the live template still omits or malforms a required field, or the page is only eligible for a different product result type. Monitoring window — Immediate. Rollback trigger — Revert if the deploy removes previously valid required markup across the product template.

Confirm Google can see the same markup

Test to run — Run URL Inspection’s live test and inspect the rendered page for the same product URL. Expected result — Google can fetch the page and render the Product/Offer markup with an offer price above zero. Failure interpretation — robots rules, rendering, authentication, or client-side timing prevents Google from seeing what the browser-side validator saw. Monitoring window — Immediate for the live test. Rollback trigger — Stop rollout if Google loses access to product pages or their previously visible markup.

Confirm the issue clears in Search Console

Test to run — Start Validate fix for the affected Merchant listings issue and monitor the sampled URLs. Expected result — validation passes as Google recrawls, the invalid cohort declines, and valid items do not fall unexpectedly. Treat a pass as confirmation the markup issue is fixed, not as confirmation the item is being displayed, ranked, or driving traffic — that’s a separate, unmeasured outcome. Failure interpretation — the fix is not present on every template variant or Google has not recrawled enough examples yet. Monitoring window — Multiple crawls and report refreshes over time; Google does not publish a fixed turnaround and the report is not real time. Rollback trigger — Revert or halt the template rollout if invalid items grow or valid coverage drops across unaffected products.

Confirm the markup was not simply removed

Test to run — Compare valid, non-critical-issue, and invalid trends after the change, then spot-check URLs that disappeared from the valid count. Expected result — fixed URLs move toward valid (with or without a non-critical issue) without vanishing from all cohorts. Failure interpretation — a drop in valid items without a matching rise in invalid items can mean Google no longer finds the markup at all. Monitoring window — After the next report refresh. Rollback trigger — Restore the prior template if product markup disappears from a material part of the intended catalog.

Tools for working this report

• Google Search Console — Merchant listings report — Shopping → Merchant listings; the report this article is about (valid/invalid items, critical/ non-critical issues, trended).
• URL Inspection tool (GSC) — confirm whether the Product markup is actually in the rendered HTML for a single URL; the first stop when valid items drop.
• Rich Results Test — validate a live URL’s structured data property-by-property and see the exact issues Google reads.
• Schema Markup Validator (schema.org) — general schema validity check, independent of Google’s eligibility rules.
• Google Merchant Center — separate system for your product feed; check here when the problem is feed disapprovals, not page markup.
• Bing Markup Validator (Bing Webmaster Tools) — Bing’s per-URL structured-data check; there’s no aggregate merchant-listings-style report on Bing.
• Crawlers / site audits — Ahrefs Site Audit and Screaming Frog SEO Spider surface which URLs carry (or lost) Product markup across the whole site.

Test yourself: Merchant Listings Report

Six quick questions on the Merchant listings report. Pick an answer for each, then check.

Resources worth your time

My related writing (Ahrefs)

• Schema Markup: What It Is & How to Implement It — the Ahrefs guide to structured data, the foundation the Merchant listings report validates.
• The Beginner’s Guide to Technical SEO — where structured data and Search Console reporting fit in the bigger technical picture.
• What is Structured Data? — the Ahrefs glossary definition of the markup this report checks.

From around the industry

• Shopping reports and tools – Search Console Help — Google’s own umbrella doc; keep it open while reading your report.
• How To Add Merchant Listing Structured Data – Search Central docs — the property-level technical reference (required/recommended fields, the Offer rule, GTIN and certification guidance).
• New Search Console Merchant Listings report – Search Central Blog (Sept. 2022) — the launch announcement and the “no Merchant Center account needed” expansion.
• Merchant Listings in Google Search Console – Brodie Clark Consulting — the strongest independent walkthrough: Popular Products, Knowledge Panels, Google Images filters, the variant/AggregateOffer pitfall, and the “free product listings” renaming argument.
• Google expands enhanced product experiences to more e-commerce sites – Search Engine Land (Sept. 2022) — industry coverage of the launch and the report split.
• Google Search Console Gets New Merchant Opportunities Report – Search Engine Journal (Apr. 2025) — the separate Merchant opportunities report refresh (payment methods, store ratings) — useful for not confusing it with merchant listings.
• Google Search Console Breaks Out Merchant Listings and Product Snippets Reporting – Search Engine Roundtable — the report-split coverage with practitioner context.

Merchant Listings Report

The Merchant listings report is a Google Search Console report (under Shopping) that validates the Product/Offer structured data on your own pages for free merchant listing experiences — Popular Products, Shopping Knowledge Panels, and shopping surfaces in Google Images and Lens. It classifies items as valid or invalid based on critical issues, with non-critical issues flagged as enhancement opportunities, and is distinct from both the Product snippets report and Google Merchant Center's feed diagnostics.

Related: Google Merchant Center, Product Schema, Rich Results

Merchant Listings Report

The Merchant listings report lives in the Shopping section of Google Search Console. It checks the Product/Offer structured data Google crawled on your web pages and classifies each item as valid (no critical issue) or invalid (at least one critical issue), with non-critical issues broken out separately as enhancement opportunities on otherwise-valid items — this is for merchant listing experiences, the free, enhanced Shopping surfaces in Search (Popular Products carousels, Shopping Knowledge Panels, and shopping results in Google Images and Google Lens). A page can hold more than one structured-data item, and an item can carry more than one issue, so item, page, and issue counts aren’t interchangeable.

Two clarifications matter. First, it validates on-page structured data, not your product feed — so it is not the same thing as Google Merchant Center’s own product diagnostics, which track the feed you submit. Second, since September 2022 you don’t need a Merchant Center account for this report to populate: valid Product markup on pages where a shopper can complete a purchase is enough to be eligible. It’s also distinct from the Product snippets report (broader, covers review/aggregator pages, accepts AggregateOffer) and the separate Merchant opportunities report that a Merchant Center association unlocks.

Related: Google Merchant Center, Product Schema, Rich Results

Changelog