Rich Results Test passes, but Merchant Center reports a mismatch
A structured-data test can parse a valid Product while the current visible value, selected variant, or submitted feed row still differs. Compare all three layers on the exact affected page.
MMP does not inspect the Merchant Center account or reproduce Google's crawl snapshot. It checks the current page and one optional local row without claiming approval.
Passing schema validation is not a three-layer match.
Keep validation, current page consistency, and Merchant Center account diagnostics as distinct questions.
Use the affected URL
Test the exact product or variant URL reported in Merchant Center, including any variant query parameter required to load the right selection.
Separate validity from consistency
A parseable Product result does not establish that its values match the visible page or the submitted product row.
Capture the visible state
Record the current selected variant, purchasable price, currency, sale state, and availability shown to the user.
Select the matching Offer
Confirm which Product or ProductGroup Offer belongs to the current variant before comparing its supported fields.
Add one feed row
Paste or import the affected product row locally so the page and structured-data values can be compared with the submitted values.
Check timing and rescan
After fixing the stale source, verify the live page again. Merchant Center recrawl timing remains outside the extension's boundary.
The markup can parse while the feed price is stale.
In this bounded example, the page and matching Offer agree but the locally supplied row still exposes the old price.