Merchant Center price mismatch: why your products aren't showing on Google

A Merchant Center price mismatch means that the price you send to Google doesn't match the price Google finds on your product page. Google responds in one of two ways: it disapproves the product and removes it from Google Shopping, or, if automatic item updates are on, it replaces your price with the value from the page. Both are problems. In one case the product is invisible; in the other it appears at the wrong price. The cause is rarely the individual products; it is usually the way the shop outputs its prices, and that is where it needs fixing.

What does a Merchant Center price mismatch mean?

A price mismatch occurs when the price in your Merchant Center product data and the price on the product page are not the same. Google regularly visits the page of every product in your feed and compares the two values. When it finds a difference, you will see one of two messages in Merchant Center:

Message	What happened	Result
“Mismatched value (page crawl) [price]” (error)	Google found the difference and disapproved the product	The product appears neither in Google Shopping nor in ads
“Automatic updates: Mismatched price” (warning)	Google found the difference and replaced the price with the value from the page	The product stays visible, but at the price Google chose

The first message is hard to miss, because products disappear. The second is quiet, and that makes it more dangerous: in Google's words, your product's price value was automatically updated to match the data on your landing page. If the price on the page is wrong, the product is now live at the wrong price.

Why are my products not showing on Google Shopping?

Not every missing product has a price mismatch. In Merchant Center there are three common reasons, and each needs a different response:

1. The first review is still pending. New or changed products are reviewed by Google first. All you can do is wait.
2. The product has been disapproved. A price mismatch, missing information, an image problem or a policy violation. The reason is shown in the product status.
3. The product data never arrived. The feed wasn't uploaded, the shop plugin's connection dropped, or the product is excluded.

We saw why this distinction matters in one account. Merchant Center reported that the product pages of 150 products could not be checked, which sounds like a fault on the website. We opened the pages one by one with Google's shopping crawlers: every single one loaded without a problem. Meanwhile, Merchant Center listed 155 products as awaiting their first review, noting that the review can take up to three working days. The website was fine; the products were simply in the queue. Within a few days the number fell on its own.

Not every red line is a website fault. Read the reason first, then act.

Where does Google get the price from?

Google knows a product's price from three sources and expects all three to match:

• Product data (the feed): the list you send to Merchant Center, via a plugin, a file or an API.
• The product page: the page and price your customers see.
• Structured data: the product details in the page's code, written for machines. This is the markup Google reads for automatic item updates.

Google's price rule is clear: submit an amount and currency that match the price on your landing page and your checkout pages. Outside North America, the price is submitted including VAT in most countries. Automatic item updates are on by default: Google reads the page's structured data and adjusts price, sale price, availability and condition to match it.

That has an important consequence. Even if your customers see the right price, Google will see a different one if the structured data in the page code says something else. This is exactly the situation behind the many forum threads where shop owners insist the prices in their feed and on their page are identical and the error still won't go away.

Two special cases have their own rules. For bundles and sets, you submit the total price of the whole bundle; if you also sell the parts individually, each part needs its own page with its own price. For variants, each variant needs its own URL, and according to Google's product variants guide, the page must show that variant preselected with the right image, price and availability. A page that opens without a colour or size selected and shows the default variant's price will not match a different variant in your feed.

What are the most common causes?

The cause is rarely a single product; it is usually a setting or the structure of the shop. Google's price troubleshooter and our own measurements point to these causes:

Cause	How to spot it
VAT settings	There is a fixed percentage gap between the feed and the page
Currency	The page opens in a different currency under another country setting
Sale dates	The sale has ended on the page but continues in the feed, or vice versa; the time zone is wrong
Timing	The price changed in the shop, and the feed caught up hours or days later
Variants	A variant's URL shows the price of a different variant
Sets and bundles	The feed sends the part price, the page shows the total price of the set
Two prices in the structured data	The page code contains two conflicting prices for the same offer

The last three are connected and the hardest to find, because customers see nothing wrong on the page. In the case below, all three occurred at once.

What we measured in an online furniture shop

We reviewed the Merchant Center account of an online furniture shop on 15, 18 and 22 September 2026. The shop had around 1,700 offers. Overall, things were improving:

Measurement	15 Sep	18 Sep	22 Sep
Approved	0	1,077	1,508
Not approved	654	577	159
Clicks (last 28 days)	29	47	79

On 22 September two new items appeared. Nine offers had been disapproved for a price mismatch. And there was a warning that didn't show in the default view at all: for 76 products, Google had changed the price itself.

What was going on? The shop sold bedroom furniture both as complete sets and as individual pieces. A piece such as the bedside table was set up as a variant of the set. The feed sent this piece as a separate offer at around €300. But when the piece's URL was opened, the page showed the price of the whole set, around €5,000. And the structured data on the same page carried two prices within the same offer: the set price and the price of the piece.

Google saw €5,000 on the page and €300 in the feed. For nine products it treated this as a mismatch and disapproved the offer. For 76 products, automatic item updates kicked in and Google replaced the price with the value from the page. In other words, the single piece was live on Google at the price of the whole set.

The root cause was not in the products but in the structure of the shop: the same variant attribute carried both the bed size (160x200, 180x200) and the set piece. The feed treated every variant as a product of its own; the page described the whole set.

The fix was made in a single place: when a variant URL is opened, the page's structured data now carries only that variant's price. Nothing changed on the main product page, and no price that customers see changed. In our check, the structured data price matched the feed price for all nine disapproved offers. For 20 randomly chosen set variants, the variant URL showed the variant's own price in all 20 cases.

Google takes a few days to crawl these pages again. Once we have measured the result, we will update this article.

Why aren't automatic item updates the answer?

Automatic item updates hide the symptom of a price mismatch but don't fix its cause. Google says so itself: they are not a replacement for regular updates to your product data and are meant for occasional problems.

The 76 products in the case show why this matters. They weren't disapproved and stayed visible. On paper, everything was fine. In reality, shoppers on Google were seeing the price of a whole bedroom for a bedside table. Nobody clicks on an offer like that, and anyone who does lands on a page that doesn't match what they expected.

Google also describes price mismatches as critical errors that can lead to account suspension, even once they have been corrected. Switching the updates off isn't the answer either: the same products would simply be disapproved instead. The right approach is to read the warning as a signal and find out where the difference comes from.

How do you fix a price mismatch?

You fix a price mismatch by seeing every affected product, comparing the three price sources and removing the difference at its source. Step by step:

1. See every problem. Merchant Center's issues view shows errors by default, not warnings. In the account we measured, it listed two items, while the product status details listed six. Open the product status details and make sure warnings are included.
2. Download the list of affected products. Do they have something in common? Are they all variants, all on sale, all in one category? In the case above, all nine were set pieces, and that pattern led straight to the cause.
3. Put the three prices side by side. For one product, compare the price in the feed, the price on the page and the price in the structured data. You can see the structured data with Google's Rich Results Test.
4. Fix the difference at its source. Is it VAT, a sale period, a variant URL or the code a plugin writes? Correcting individual products only postpones the problem while the fault remains in the structure.
5. Resubmit the feed and wait. The figures change as Google recrawls. Watch the number of affected products for a week. If you have many products whose prices change often, Google also recommends reviewing the crawl rate setting in Merchant Center for this issue; your pages are then visited more often, and new prices reach Google sooner.

How do you prevent price mismatches?

You prevent price mismatches by making sure the price comes from a single source and that every change there reaches Google straight away. Five habits stop most problems before they start:

• One source of truth for prices. The price is entered once in the shop system; the feed, the page and the structured data all read it from there. Typing prices into the feed separately means the two will drift apart sooner or later.
• Update the feed as soon as prices change. Google recommends sending the feed immediately after price updates. A file uploaded once a day will always lag behind prices that change during the day.
• Set sales with dates and time zones. The start and end of a sale price belong in the feed as well, with the correct time zone, so a sale that has ended in the shop doesn't carry on in the feed.
• Test after every theme or plugin update. Structured data is usually generated by the theme or a shop plugin. An update can quietly change where the price is written. Running a few product pages through the Rich Results Test takes five minutes.
• Open the product status details once a month. Look at the warnings, not just the errors. The problem with the 76 products was only visible there.

When is it worth getting help?

If a setting such as VAT or a sale period is wrong on a handful of products, most shop owners can fix it themselves. In these situations, outside help saves time:

• The number of affected products runs into the hundreds or rises every day.
• The problem is concentrated on variants or on products that are also sold as sets.
• The page shows the right price but Google sees a different one, which means the problem is in the page code.
• Your account has received a suspension warning.

What these cases have in common is that the problem lies in the structure of the shop: the code a plugin generates, the way variants are set up, the source of the structured data. That is why we always look at the Merchant Center account and the shop together; the fix for a price mismatch is usually on the website, not in the account. How paid and organic visibility on Google relate to each other is covered in our article SEO vs PPC.