Merchant Center issue
Fix a mismatched product price in Merchant Center
Google checks the price you submit against the price on your product page. When the two differ, Merchant Center flags "Mismatched product price", also shown as "Mismatched value (page crawl) [price]". It is a disapproval, and repeated mismatches put the whole account at risk. This page explains what Google compares and how to bring both sides back in line.
Diego Nijboer · WISEPIMLast updated:
Short answer
Update the price in Merchant Center so it matches your website in the currency of the target country, either per product or in bulk with a CSV of the affected products. Make sure the price is in the HTML your server returns, not added later by JavaScript. Then wait for Google to crawl again or request a website check, which can take up to 12 hours.
What this issue means
Googlebot visits your landing page and compares the price in your product data with the price on the page or in its structured data. If they do not match, the product is disapproved. Prices that JavaScript loads after the page renders can trigger the issue too, because Google expects the price in the HTML your server returns.
A related issue, "Automatic updates: Mismatched price", means Google has already corrected the price from your site because automatic item updates are switched on. The offer keeps running, but the notice tells you your feed is behind your website. Google's advice there is the same: send feed or Merchant API updates right after your site changes, and check your sale price dates.
| Detail | Value |
|---|---|
| Issue in Merchant Center | Mismatched product price |
| Also shown as | Mismatched value (page crawl) [price] |
| Attribute | price [price] |
| Effect | The product is disapproved until the price matches your landing page, and Google warns this may lead to an account suspension. |
| Checked | Against Google Merchant Center Help on 11 October 2026 |
Common causes
- Your website price changes more often than your Merchant Center data is updated.
- The structured data on the page shows a different or outdated price.
- Bots get a different price or currency than people do, for example through geo or currency redirects.
- The sale price dates or their time zone are wrong, so the sale starts or ends at a different moment than on the site.
- The notice is old and the price has already been fixed since Google's last check.
- A product sold with a minimum order quantity or in bulk shows a unit price instead of the total price for the minimum quantity.
How to fix it, step by step
- In Merchant Center, open Products and the Needs attention tab, and filter on this issue to see every affected product.
- Open a few affected products next to their landing pages and note which price differs and why: timing, structured data, currency or a sale.
- For a handful of products: open the product, choose Edit product, set the price to match your website in the target country's currency and save. If the site shows several currencies, match the most prominent one.
- For many products: download the affected products as a CSV file, compare them with your product data, correct the prices and upload them with your usual method.
- Check that the price is in the HTML your server returns and that your structured data shows the same price. Google's rich results test helps here.
- Check sale price dates and time zones, and use the total price for the minimum quantity on minimum order or bulk products.
- Wait for Googlebot to crawl again, which can take hours or days, or use Request website check. That check can take up to 12 hours and you cannot send a new request meanwhile.
- If you think the flag is wrong, choose I disagree with the issue and Request review. Review request limits may apply.
Free tool
Check a product against Google Shopping rules
Enter one product's title, description, price, GTIN and image link. The checker lists the errors and warnings Merchant Center's core requirements would raise, before you upload.
How to prevent it
- If your prices change often, schedule regular uploads or send updates through the Merchant API right after the site changes.
- Render the price in the server HTML and keep structured data in sync with the visible price.
- Test your structured data with Google's rich results test after theme or plugin changes.
- Set sale price dates with the right time zone, so the feed and the site switch at the same moment.
How WISEPIM helps
WISEPIM does not crawl your landing pages or check structured data, so it cannot see what Googlebot sees on your site. What it does is keep the price you send to Google coming from one source. The Merchant Center connection sends price and sale price, and a daily check (for projects that exported in the last 14 days, up to 500 products) compares title, price and availability in Merchant Center with what WISEPIM would send, and stores the item issues Google reports, so drift shows up in WISEPIM.
If you publish through Feed Hub instead, a feed can regenerate on a schedule or whenever a product changes, which shortens the gap between a price change and the next feed Google reads.
Sources
Vendor documentation we read for this guide, as of October 2026. Features and names change, so check the current documentation before you decide.
Frequently asked questions
Still have questions?
Can't find the answer you're looking for? Please get in touch with our team.
Contact SupportCatch feed problems before Google does
WISEPIM checks every product against the Google Shopping rules in Quality Guard and sends clean data to Merchant Center or a Feed Hub feed. Free for up to 100 products.
Keep reading
Google Merchant Center guide
Setup, feed or API, the product data essentials and every issue page.
Read moreGoogle Shopping feed checker
Test one product's title, price, GTIN and image against Google's limits.
Read moreGoogle Shopping feed spec
Every feed field with its format and limits.
Read more
Keep exploring
Hand-picked next steps to go deeper.