In short. A Google Merchant Center price mismatch can cause disapproval or automatic correction, and the merchant must align submitted prices with the website.
Definition: A product feed price mismatch occurs when the price submitted to Google Merchant Center differs from the product's landing page price. As of 17 October 2026, Google documents possible product disapproval or an automatic price correction, with correction of the submitted data still required.
Key facts
- Google's mismatched product price documentation says Googlebot compares submitted prices with landing pages or their structured data, meaning machine-readable product markup.
- Google's automatic price updates guidance says corrected mismatches remain critical errors that can lead to account suspension.
- Google's price attribute specification requires the submitted amount and currency to match both the landing page and checkout.
- Google's inaccurate price status guidance describes account warnings or preemptive product disapprovals after reviewers find mismatches.
Which price must match?
Google's price specification requires the target country's currency to appear prominently on the landing page and checkout. A price hidden behind “View price in cart” fails that requirement. Its text feed format example is:
15.00 USD
The same specification requires any user in the target country to be able to buy at the submitted price. It prohibits changing the landing page price through IP location detection and directs merchants with regional prices to the regional pricing program where available.
Google's account-level mismatch guidance also requires a variant-specific URL to load the corresponding variant already selected. Its example pairs a premium flower bouquet's feed price with the premium bouquet selected on the page.
How is the mismatch corrected?
Google's automatic update instructions require the product's submitted price to agree with the website and its structured data. For a sale, the fields to check are:
price
sale_price
sale_price_effective_date
The same instructions require the sale period and time zone to be correct. They recommend scheduling feed uploads or Merchant API updates immediately after website changes. For local products, the local inventory feed may also need correction.
In Merchant Center, the documented route for an individual correction is:
Products > Needs attention > [product title] > Edit product > Save
For bulk corrections, the instructions describe downloading the affected products as a CSV, comparing their values with the website and structured data, and uploading corrected product data. Automatic updates can be managed in the Products area's Automations tab.
What happens after correction?
Google's mismatch documentation says disapproved products are crawled again over the following hours or days. Matching prices allow reapproval after that crawl. A website check can be requested after correction; automatic review also occurs later without a request.
The same documentation says review can take up to 12 hours, during which another request cannot be submitted. The notification timestamp records the earlier mismatch; the current approval status appears in the Status column on All products.
Related terms
FAQ
Where should I start with an account warning?
Google's account-level guidance directs you to the warning email's affected product examples. Use them to identify a common issue across similar products and correct those prices.
Can JavaScript pricing cause this error?
Google's price mismatch guidance says prices in the server-returned HTML must match Merchant Center. It identifies prices passed dynamically through JavaScript after page load as an error trigger.
Sources
- Google Merchant Center Help, "How to fix: Mismatched product price", accessed 17 October 2026
- Google Merchant Center Help, "How to fix: Automatic updates: Mismatched price", accessed 17 October 2026
- Google Merchant Center Help, "Price [price]", accessed 17 October 2026
- Google Merchant Center Help, "How to fix: Inaccurate price status due to inconsistency between feed and landing page", accessed 17 October 2026
Check how a page reads to answer engines. Open the GEO score analyzer