Price diagnostics
How to fix a Google Merchant Center price mismatch
Find feed-side price defects, then align the submitted price, landing page, structured data, currency, and active sale timing.
Reviewed against Google Merchant Center documentation on August 25, 2026. Independent guide; not affiliated with or endorsed by Google.
What the diagnostic means
Google reports a price mismatch when the price in submitted product data is inconsistent with the product landing page. Structured data can also contribute to the mismatch.
Common causes
- The store price changed before the product data source refreshed.
- A sale started or ended, but sale_price and the displayed promotion are out of sync.
- The landing page structured data contains a different price or currency.
- A variant URL opens on a different option than the one represented by the feed row.
- Regional pricing, currency, tax, or checkout behavior differs from the submitted target.
Resolution checklist
Fix it step by step
- Open a sample affected product from Merchant Center and record its submitted price, currency, and URL.
- Check the final landing-page price and the price in Product structured data for the same variant.
- Correct the source of truth, including sale_price and sale_price_effective_date when a promotion is time-bound.
- Refresh or re-upload product data after the storefront and source data agree.
- Recheck the Needs attention area after Google processes the update; do not attempt to hide affected products from a review.
Before you resubmit
- Every price uses a positive amount plus a three-letter currency, such as 29.99 USD.
- sale_price uses the same currency and is lower than price.
- The feed row, selected variant, landing page, structured data, and checkout agree.
- Scheduled uploads are frequent enough for the store’s price-change cadence.
Feed-side formatting correction
Before
price: 29.99 sale_price: 35 USD
After
price: 35.00 USD sale_price: 29.99 USD
Frequently asked questions
Can a file validator prove that a price mismatch is fixed?
No. A local validator can find malformed and internally inconsistent price fields, but only a comparison with the live landing page, structured data, and checkout can establish end-to-end consistency.
Should I delete disapproved products before requesting review?
No. Google specifically warns against removing products to bypass a data-quality review. Correct the mismatches and follow the review process shown in Merchant Center.
How can I reduce repeat mismatches?
Keep the catalog and storefront on the same source of truth, refresh feeds promptly after changes, and use valid product structured data. Google also documents automatic item updates as a supporting safeguard, not a substitute for accurate source data.