2026-10-25

WooCommerce: fixing "Mismatched value (page crawl) [price]" in Google Merchant Center

"Item-level disapproval: Mismatched value (page crawl) [price]" means Google visited your product page, read a price there, and it wasn't the price in your product feed. Google's help article for this issue is How to fix: Mismatched product price. It says mismatched products may be disapproved and that the problem "may lead to an account suspension", so it's worth fixing properly instead of waiting for it to go away.

On a WooCommerce store the feed and the page usually come from the same product, so the two prices should agree. When they don't, one of the settings below is often the reason. This guide covers what Google compares, how to find the products, the WooCommerce cause behind each kind of mismatch, and how to get Google to check again.

Not sure which products are affected? Run the free Merchant Center Check.

Run the free Merchant Center Check

What Google compares

Google crawls the landing page in your feed and reads the price from the page's HTML or from its structured data (the Product markup WooCommerce and SEO plugins add). Google's help page says a price passed in with JavaScript after the page has loaded can also trigger the error. Your feed, the visible price and the markup all have to show the same amount in the same currency.

The issue can also appear as "Mismatched regional value (page crawl) [price]" for regional prices, and repeated mismatches can turn into an account-level "Inaccurate prices" warning. Google's price troubleshooter lists all of them.

Find the affected products

In Merchant Center, open Products (Google's help page names the tab Needs attention) and filter by the price mismatch issue.
Open one product. Compare three values: the price in the product's details in Merchant Center, the price on the live product page in a private browser window, and the price in the page's markup. To see the markup, paste the URL into Google's Rich Results Test and open the Product item's offer.
Note which one is different. That points to the cause.

For a long list, download the list of affected products as a CSV, as Google describes, and check a few from each product type. A list like this often traces back to one store setting.

The WooCommerce causes, and the fix for each

1. Prices shown with tax, feed sent without it (or the other way round)

If tax is turned on, WooCommerce → Settings → Tax has two settings that matter: "Prices entered with tax" and "Display prices in the shop". When the shop shows prices including tax but the feed sends prices without it, every taxed product mismatches by the tax amount.

Fix: decide which price shoppers in your target country should see, then make the feed match that. Countries where Merchant Center expects tax-inclusive prices need the tax-inclusive figure. Check how your feed plugin sends tax. In Google for WooCommerce, the product feed settings are under Marketing → Google for WooCommerce.

2. Geolocation shows Googlebot a different price

WooCommerce → Settings → General → Default customer location can be set to "Geolocate". Then tax, and with some plugins the currency, follows the visitor's location. Googlebot doesn't necessarily crawl from your customers' country, so it may get a price your customers never see. Google lists "bot and user prices differ" as a cause.

Fix: set the default customer location to your shop base address, or make sure your geolocation or currency plugin shows crawlers the same price and currency your feed sends for that country.

3. A currency switcher

A multi-currency plugin can show a converted price, or remember the last visitor's currency in a cached page, while the feed sends your store's base currency (WooCommerce → Settings → General → Currency options). Google's article says to submit the price in the correct currency for the target country.

Fix: send one feed per country and currency, built from the prices that country's shoppers actually see, or turn off automatic currency switching for the country you're advertising in.

4. Scheduled sale prices

A sale price with dates (Products → edit product → Product data → General → Sale price → Schedule) changes the page price on the start date and changes it back on the end date. Google's article lists wrong sale start or end dates and time zones as a cause. WooCommerce applies the schedule with WordPress's scheduled tasks and your site's time zone (Settings → General → Timezone), so the page can switch at a different moment from the feed. A site whose WordPress cron only runs when someone visits can switch late.

Fix: set the site time zone to the one you actually trade in, make sure the feed sends the sale price with the same dates, and after a sale starts or ends, check that both the page and Merchant Center show the new price. If scheduled tasks run late on your site, ask your host to run WordPress cron from a real server cron job.

5. A cached page

A caching plugin, your host's cache or a CDN can keep serving yesterday's page after you change a price. Your feed updates, the cached page doesn't, and Google sees the old price.

Fix: clear the page cache and the CDN cache after any price change, and make sure your cache clears a product's page when the product is saved. Then check the page in a private window, not while logged in, because logged-in admins often bypass the cache.

6. Variable products and price ranges

Every variation is its own item in Merchant Center, with its own price. The parent product page shows a range ("$20 – $35") until a shopper picks options, so if the feed sends a variation but its link opens the parent page with nothing selected, Google may read the range or the wrong variation's price.

Fix: make sure each variation's link opens the page with that variation's attributes selected, that every variation has a price, and that the markup on the page lists the variation prices. Check one variation's URL in the Rich Results Test.

7. Prices changed after the last feed sync

Edit a price, and the page changes immediately, but Merchant Center keeps the old price until your feed plugin sends the update. Google's article lists update timing first.

Fix: after a bulk price change, make sure the feed has sent it. For Google for WooCommerce, check that its pending jobs in WooCommerce → Status → Scheduled Actions are moving. If they aren't, our guide to products not syncing has the order to check things in.

8. Markup that disagrees with the page

Google can read the price from structured data. If two plugins output Product markup, for example WooCommerce and an SEO plugin, or a theme adds its own, one block may carry an old, regular or tax-free price. Prices added by JavaScript after the page loads, such as some dynamic or role-based pricing plugins, may not be in the HTML Google reads at all.

Fix: run the Rich Results Test on the product URL. If you see more than one Product item, or the offer price isn't the price on the page, turn off the duplicate markup in the plugin or theme that adds it, and make sure the price is in the page's HTML.

9. Minimum or bulk quantities

If a product can only be bought in packs or with a minimum quantity, Google's article says the feed must carry the total price for that minimum quantity, not the price of one unit.

Automatic item updates

Merchant Center can correct small price differences for you. Google's article Allow Merchant Center to update product information automatically says these automations use the price on your page and are on by default. They aren't a replacement for a correct feed: Google says they may not work for products whose price changes often, and those products may be disapproved instead. Turn them on or off under Products → Automations in Merchant Center. If your pages show more than one strikethrough price, Google advises against turning price automations on.

Ask Google to check again

Fix the cause, then make sure the corrected price is in Merchant Center: let your feed plugin sync, or edit the product or re-upload the file as Google's article describes.
Check the live page and its markup once more in a private window.
In Merchant Center, request the website check the help page describes. Google says the review "may take up to 12 hours" and you can't send another request in that time. Without a request, Google says it re-crawls disapproved products "over the next few hours or days".

Google decides when an item is approved again. If the Status column on the products page already shows the item as approved, the notice you're reading may be older than the fix.

If you also have an account-level suspension, fixing prices is only part of the job. Our Merchant Center misrepresentation guide covers what reviewers check across the whole store.

Check your store

Our free Merchant Center Check reads your store's public pages and lists the Merchant Center issues it can see, so you know where to start. No account, no card.