Mismatched price in Merchant Center: product data vs page

Work out which side is stale, the product data or the page, and fix it where it starts. Rarely fraud. Usually a sync that fell behind. Google’s “How to fix: Mismatched product price” page says a product whose landing page price differs from the [price] in your data source may be disapproved, that prices in the HTML need to match the uploaded prices exactly, and that product data prices that differ from your website can end in an account suspension. In Merchant Center, download the affected items from the Needs attention tab. For a sample, open each product link in a private window and note three prices: on first load, in the structured data and in the cart. Google’s fix page names the causes: site changes that reach Merchant Center late, wrong structured data, a sale price with the wrong [sale_price_effective_date] or time zone, and pack items sent with a single-unit price. Put the real price in the HTML when the page loads, not one a script swaps in later.

Google's “How to fix: Mismatched product price” page is blunt about the stakes. When the landing page price and the [price] in your data source differ, “the product with the mismatch may be disapproved”, and the same page warns that product data prices that differ from your website can end in an account suspension, not just a paused item. It is specific about what the page has to carry, too: “Prices reflected in the HTML need to match exactly the prices uploaded in Merchant Center.” A price that only appears after a script runs is one of the causes it names.

The “Price [price]” page sets the rule for both sides: “Submit an amount and currency that match the price on your landing page and the checkout pages”, and “Keep your prices up to date.” Google's landing page requirements add a timing rule that plenty of themes trip over: “Make sure your pricing and availability information is consistent through the process of page load.” A page that loads one figure and then swaps in another has two prices, and only one of them can match.

The fix page lists the usual causes, and none is exotic: site changes that reach Merchant Center late, incorrect structured data markup, a sale price whose [sale_price_effective_date] or time zone is wrong, and pack or minimum-quantity items sent with a single-unit price. Google's “Issues in Merchant Center” page describes a stricter mode as well: “Preemptive item disapproval (PID) occurs if the price or availability of your products don't match between your product data and website landing pages.” Automatic item updates help at the edges, but Google's automations page is clear that “Automations aren't a replacement for regular updates of your product data.”

Manual check first: StoreVerifier does not see your product data, so the side-by-side against Merchant Center is yours. The free scan covers the page half. It reports a cart price higher than the product page as a failure, and flags structured data whose price disagrees with the price on the page. The full list of price checks is on the misrepresentation checker. For sale prices, see discounts and “was” prices; for currencies, currency in Merchant Center.