Google Merchant Center Product Data Mismatch: How to Fix It

Google Merchant Center checks your product feed against your actual website. When it finds that the price in your feed does not match the price on the landing page, that an image shows a different product, or that a title describes something the page does not sell, it flags those items as containing product data mismatches. Enough mismatches lead to item disapprovals. Persistent mismatches across many products lead to account suspension under the "Misrepresentation" policy.

This guide covers the five most common causes of product data mismatches, how to fix each one, and how to use Google's own tools to confirm your data is clean before it causes problems.

What Google means by "product data mismatch"

Google's crawlers visit your landing pages periodically to verify that what your feed says matches what a shopper would see. A mismatch is flagged when:

• The price in the feed is different from the price shown on the product page.
• The product image in the feed shows a different colour, model, or variant than what the URL resolves to.
• The title or description in your feed refers to features that are not visible or purchasable on the landing page.
• The product is listed as in stock in the feed but out of stock on the page.

Google does not always tell you exactly which field is wrong. The Diagnostics tab in Merchant Center shows the category of the issue, and from there you have to investigate which products are affected and why.

Cause 1: Delayed price updates in the feed

You change the price on your website. The product page shows the new price immediately. Your Merchant Center feed still has the old price because it was last fetched yesterday.

This is the most common cause of price mismatches. Google's crawler may visit your landing page and see the new price before your feed has been refreshed. The result is a mismatch.

Cause 2: Currency conversion errors

If you target multiple countries and use automatic currency conversion, the price in the feed may be calculated at a different rate than the price your landing page shows using a third-party currency widget. Google sees two different numbers and flags a mismatch even though both numbers are legitimate.

Cause 3: Dynamic pricing not reflected in the feed

Some stores use dynamic pricing based on user segments, ad traffic, or real-time supply. The price a logged-in repeat customer sees may differ from the price in the feed. The price a mobile visitor sees may differ from what Google's crawler reads on a desktop user-agent.

Cause 4: Mobile vs. desktop price differences

Some stores show different prices or apply different promotions depending on whether the visitor is on mobile or desktop. Google crawls with both mobile and desktop user-agents. If the prices differ across device types and your feed uses one price, one of those crawls will flag a mismatch.

Cause 5: Promotional pricing not updated in the feed

You run a flash sale and drop prices on your site for 48 hours. The feed still shows regular prices. Google crawls during the sale, finds a lower price on the page than in the feed, and flags a mismatch.

This also works in reverse: the sale ends, prices go back up on your site, but the feed still shows the sale price. Now the feed shows a lower price than the page, which Google also treats as a mismatch.

How to use the Diagnostics tab in Google Merchant Center

The Diagnostics tab is your first stop for identifying mismatch issues. Navigate to Products → Diagnostics in Merchant Center. You will see a breakdown of active issues with severity levels: errors (items disapproved), warnings (items at risk), and notifications (informational).

For product data mismatches specifically, look for entries under "Item issues." Click on any issue to see a list of affected products, the attribute in question, the value in your feed, and the value Google found on your landing page. This comparison is the most direct way to understand what changed and why.

Export the affected product list to CSV and prioritise items with high click volume or high revenue, since those mismatches carry the most risk of suspension escalation. Fix those first.

Enabling automatic item updates

Google offers a setting called Automatic Item Updates that lets Merchant Center override your feed's price and availability data based on what it crawls from your landing pages. This acts as a short-term buffer when your feed is slightly out of date.

To enable it: in Merchant Center, go to Settings → Automatic improvements → Automatic item updates. Turn on updates for price and availability separately. Note that this is a corrective tool, not a replacement for keeping your feed accurate. Google's own documentation states that accounts with chronic mismatches may not be eligible for automatic updates.

Testing with the Rich Results tool

Google's Rich Results Test lets you enter any product URL and see what structured data Google extracts. For product pages, it shows the price, availability, and image Google reads from your page. Compare this output against what your feed contains for the same product. If the numbers match, you are clean. If they differ, you have found a mismatch before Google flags it.

Run this test on your top 10 products by revenue every time you change prices, update images, or edit product descriptions. It takes two minutes per page and catches the most common causes before they reach the Diagnostics tab.

When mismatches lead to suspension

Individual mismatches cause item disapprovals. Widespread or recurring mismatches signal to Google that your store systematically misrepresents products, which can trigger a full account suspension under the Misrepresentation policy. You can read more about how Google defines misrepresentation and what the suspension process looks like in our full GMC suspension guide.

If your account is already suspended and you believe product data mismatches were a contributing factor, the correct approach is to audit your entire feed against your live site, fix every mismatch, and then submit a reinstatement request through the Merchant Center dashboard. Submitting a request before fixing the underlying issues almost always results in a rejection.