How to validate your product structured data for GMC

Validate product structured data in three places: the Rich Results Test for one URL, Search Console’s Merchant listings report, and the page itself. The tools catch broken code. Only a person comparing markup with the page catches markup that is valid and wrong, and that is the kind that ends in a price mismatch.

Major5 min read

By Edvinas Ivanauskas How the guides are reviewed

Why this matters

Google's “General structured data guidelines” split the job in two. The technical half is testable: “You can test compliance with technical guidelines using the Rich Results Test and the URL Inspection tool, which catch most technical errors.” The other half is not: “These quality guidelines are not easily testable using an automated tool.” Those quality rules are the ones that matter for a shop: “Provide up-to-date information.” “Don't mark up content that is not visible to readers of the page.” “Your structured data must be a true representation of the page content.”

Merchant Center points you at the same tools. Its “Set up structured data for Merchant Center” page says: “Test your schema.org implementation with Search Console or the Rich Results Tool.” It also warns that “The code that generates your structured data needs to be kept in sync with any changes to the user-facing elements on your site.” The “Rich Results Test” help page adds a small trap worth knowing: the test ignores comments inside JSON-LD, but real use may not, so “Be sure to remove any comments from JSON-LD before publishing your final page.”

For the whole site, Google's “Merchant listing structured data” documentation sends you to Search Console. After a first deployment, check the Merchant listings report; after a release, “When you make significant changes to your website, monitor for increases in structured data invalid items.” Its diagnosis is blunt: “If you see an increase in invalid items, perhaps you rolled out a new template that doesn't work, or your site interacts with the existing template in a new and bad way.” On warnings it is relaxed: fixing non-critical issues “can help improve the quality of your structured data (however, this isn't necessary to be eligible for rich results).”

The free scan does the page-by-page part for you. It flags product pages with no supported markup or with markup missing a price, currency or availability, and flags review markup whose reviews appear nowhere in the page text. What the markup itself should say is in what your Product structured data needs. Every structured-data check it runs is listed on the misrepresentation checker.

Typical evidence

Test the schema your product pages publish

The Rich Results Test can surface missing required schema fields in the page you publish. Test the live output after template changes; one template bug can affect every product that uses it.

Rich Results Test2 errors

Product — invalid

Missing field 'price' (required)

Product — invalid

Missing field 'availability'

1 template → ~150 items affected in GSC

Rich Results Testvalid

Product — 1 valid item

price, priceCurrency, availability all present

Eligible for rich results

No errors, no warnings

GSC → Enhancements → Products: 0 errors

Use GSC's Products report as a standing monitor and re-check after theme changes. It can surface structured-data issues, but it does not predict Merchant Center decisions.

The public signals this check looks for:

A theme or app update changed the markup template and nobody re-tested, so invalid items c…
A theme or app update changed the markup template and nobody re-tested, so invalid items climb in Search Console for weeks.
Two apps each print a Product block, and the test shows two products per page with differe…
Two apps each print a Product block, and the test shows two products per page with different prices.
The Rich Results Test passes, but the markup carries a price or stock status the page no l…
The Rich Results Test passes, but the markup carries a price or stock status the page no longer shows: valid, and wrong.
JSON-LD copied from a tutorial still contains comments or a trailing comma
JSON-LD copied from a tutorial still contains comments or a trailing comma.
Review or rating markup describes reviews that appear nowhere on the page
Review or rating markup describes reviews that appear nowhere on the page.
Search Console messages about structured data go to an inbox nobody reads
Search Console messages about structured data go to an inbox nobody reads.

What it looks like once it is right

The store turns off the app’s markup, keeps the theme’s block, re-tests its five template URLs, confirms the price and stock match each page, and watches invalid items fall in the Merchant listings report after validation.

Common mistakes

Common mistake

A store installs a reviews app that adds its own Product block. The Rich Results Test shows two Product items on every page, the theme’s at £45.00 and the app’s at £39.00 from last month’s sale. Both are valid. One is wrong, and nobody opened the details to see it.

Fix checklist

Pick one URL for each kind of product page you have: a simple product, a product with variants, one on sale, one sold out, and a bundle if you sell them. Validating one page only proves that page.
Run each URL, not pasted code, through the Rich Results Test, so you test what the server actually sends. Fix every error under Merchant listings first.
Open the detected Product item and compare name, price, priceCurrency and availability with what the page shows. The test checks the format; you check the truth.
Remove comments, duplicate Product blocks and leftover example values such as a demo SKU or a price of 0.00.
In Search Console, open the Merchant listings report. After a fix, inspect a live URL to confirm it, then use the report's validation button so Google rechecks the affected pages.
Decide warnings one by one. Google's documentation says fixing non-critical issues is not needed for eligibility, but recommended fields such as availability or shipping details are worth adding whenever you have accurate data for them.
Make the five-URL test part of every release: theme update, app install or removal, platform migration, or bulk price edit.
Send Search Console messages to whoever maintains the site, as Google's troubleshooting advice suggests, so an alert does not sit unread.

Make validation part of every release

GSC's Products report is the standing monitor — it watches structured-data health across the whole site and flags new errors the instant a template starts emitting them. Drive the count to zero and keep it there.

150

theme updateafter fixes

Catching a theme regression on release is better than leaving it on a shopper-facing page. Re-test templates after every theme or app change.

Questions merchants ask

What is the best tool to validate product structured data for Google?

Use the Rich Results Test for a single URL, the URL Inspection tool's live test to see the current version of a page, and Search Console's Merchant listings report for the whole site. Google's general structured data guidelines say the first two catch most technical errors.

Do I have to fix every Rich Results Test warning?

Fix every error. Google's merchant listing documentation says fixing non-critical issues can improve the quality of your structured data, but is not necessary to be eligible for rich results. Add recommended fields when you have accurate data for them; never fill them with guesses.

My markup passes the test. Why is there still a price mismatch?

Because the test checks format, not truth. Google's guidelines say their quality rules, such as up-to-date information and marking up only what is visible, are not easily testable with an automated tool. A well-formed price that differs from the page is still a mismatch; compare the values yourself.

Remediation

Risk signal

Valid is not the same as true, and a green tick from a test tool says nothing about whether the price in the markup is today’s price. Test every template after every release, compare the values with the page, and run the free scan to find the pages that slipped.

PriorityAddress and document this finding as part of the store’s remediation work.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

Last reviewed 29 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.