Merchant Center says your price does not match the page: compare feed, page, checkout and markup

What Google actually compares

When a product is flagged for an inaccurate price, Google has compared the price in your product data with what it found on the landing page, at checkout and in any structured data on the page, and found them different. The question to answer for each flagged product is therefore not what the price should be, but which of those four places disagrees with the others, and why. Google's help pages change; this guide reflects the pages as read on 11 October 2026.

• Feed value, product page, checkout and page markup: write all four down for one product.
• State the country and any variant the feed link opens; both change the answer.

The causes, grouped

Google's help page lists the causes. The most common is a stale feed: a sale starts or ends on the site and the feed has not caught up. Next is markup that disagrees with the feed. Several prices on the page can cause it, because only a price and a sale price are supported, as can prices that vary by visitor location, cookies or device, minimum order quantities where the feed shows a single-unit price, a feed link that opens a different variant, a price range where the feed should carry the lowest, handling fees that belong in shipping, and prices injected late by script that a crawler misses. Membership or discount prices are acceptable only if everyone in the target country can get them and the price is clearly shown.

Tax and format

Two rules produce a large share of mismatches. Tax: for the United States and Canada the price excludes sales tax and similar charges; for many other countries, including the UK and Germany, Google's page says the price must include VAT or GST and match the page. A store that shows prices excluding VAT to business buyers while the feed includes it will mismatch. Format: the price is a number and an ISO 4217 currency code separated by a space, with at most two decimal places, and extra digits are rounded, which can change a cent. Shipping and handling costs go in shipping settings, not the price.

Fixing it, and how review works

The page's fix steps are plain: look at the example products in the warning, find the shared pattern, correct the price attribute, resubmit the data by feed upload or a platform import, then request a review. The same page also lists the Content API for Shopping, but Google's developer pages say that API was sunset on 18 August 2026, with requests failing progressively from 1 September 2026, and describe the Merchant API as its replacement. If you submit data through an API, it needs to be the Merchant API, and moving an old integration over is a separate piece of work that this fixed job does not cover. Site and feed changes should happen together, so update the data straight after changing the site. The page says warned accounts can ask for a courtesy review before the deadline, disapproved items use I fixed the issue, a failed review starts a seven-business-day wait, and a review takes about seven business days and cannot be sped up or extended by contacting support. Plan promotions with that delay in mind.

Automations are not a fix

Google offers automations that correct small differences using your page's data, but its own page says they are not a replacement for regular updates of product data. It adds that automations may not work for products with frequent price or availability changes (for example more than once per day), that a product may be disapproved instead of updated if Google detects a mismatch, and that updates may stop if the number of detected mismatches becomes too large. For merchants who expect prices to change frequently, the page says to use the Merchant API to manage product updates. If your prices move often, the refresh route is the thing to change.

How the paid job is accepted

The job merchant-center-price-availability-mismatch is £345 for one data source and up to 25 named flagged products. For each product the corrected feed value must equal the landing page and the checkout for the agreed country, including tax treatment and currency; after you resubmit and Merchant Center has processed the data, diagnostics for those products must show no mismatch; and the refresh route must be written down and tested: your account holder changes the price of one agreed product, or of a product in a separate test data source, and restores it, and the new value must appear in the feed output within the stated time. Building or migrating an API integration is not part of the fixed job. Account suspensions, appeals and pricing decisions are out of scope. Prices are untested proposals, and payment follows the agreed checks and your sign-off. Nothing is booked or charged by an enquiry. Google's review and recrawl timing and decisions are its own, and approval is never promised.