A Google Shopping price mismatch means the price in your product feed differs from the price Google finds on the product page, in its structured data or at checkout. The fix is almost always the same: make one source of truth and make sure the feed, the page and the markup all read from it on a schedule. We build feeds for a living at Textfinity, and the feed side of that job is where most recurring mismatches are stopped for good.
This guide covers what Google actually compares, how to trace a mismatch to one product and one value, the usual causes, and how to prevent them, including for stores selling in several countries and currencies.
TL;DR
- A mismatch means the [price] in Merchant Center differs from the price on the landing page, in its structured data or at checkout. Google can disapprove the product until it is corrected.
- Trace it by product: take the examples from the warning, then compare feed value, page HTML, structured data and checkout for the same variant, country and currency.
- The usual culprits are stale feeds after a sale starts or ends, wrong sale dates, structured data still showing the old price, variant preselection and prices loaded by JavaScript.
- Automatic item updates are a safety net for rare errors. Frequent or systematic mismatches can switch them off and put the account at risk.
- Prevent repeats by publishing the feed from your catalog on a schedule, so it changes whenever the shop's prices change.
Table of Contents
- What a price mismatch actually is
- How to find the product, the value and the cause
- The most common causes
- Fixing it, step by step
- Selling in several countries and currencies
- Preventing mismatches: make the feed follow the catalog
- How Textfinity fits in
- FAQ
- Sources
What a price mismatch actually is
Google checks that what you promise in the feed is what the shopper gets. According to Google's help page on mismatched product prices, Googlebot crawls the landing page, including the HTML the server returns, compares the values, and may disapprove the product. Once you correct it, the item can be recrawled.
Two details trip up many stores:
- The server HTML counts. Google says data added dynamically with JavaScript after page load can trigger the error. The price in the HTML your server sends needs to match the Merchant Center price exactly.
- Amount and currency both count. Google requires the submitted amount and currency to match the landing and checkout pages, and it prohibits "view price in cart" and location-based price changes.
You may see the problem in two places: an item-level disapproval for a particular product, or a wider warning about inaccurate prices across the account. The causes overlap, and the diagnosis below works for both.
How to find the product, the value and the cause
Do not start by editing whichever number looks wrong. Start by proving you are comparing the same thing.
Step 1: Pull the affected products
Google's guidance for inaccurate price status is to use the examples in the warning email to identify affected products, then look for something they have in common: the same category, the same variant type, products on sale, one country. A pattern points to a rule or a process. A single odd product points to a data error.
Step 2: Fix the identity of what you compare
Note the SKU or variant ID, the target country, the currency and the time you checked. A shirt in size M and the same shirt in size XL can carry different prices, and a Swedish and a German feed carry different currencies. Many "mismatches" turn out to be two different offers compared by mistake. If you compare data across several systems, the principle of standardised product data applies here too: the same product, selected option, country and currency must sit on both sides of the comparison.
Step 3: Compare four layers in order
| Layer | What to look at | Typical finding |
|---|---|---|
| Feed | The [price] and [sale_price] you submitted for that ID | Old value from before the price change |
| Page HTML | The price in the server-returned source, not the rendered view | Price injected later by a script |
| Structured data | The price and availability in the product markup | Markup still shows the old price |
| Checkout | The price on the product line at checkout | Handling fee, minimum quantity or increase |
Google's advice is to check that product data matches the landing page and that structured data aligns with price and availability. It also points to the Rich Results Test for checking structured data. Work from the feed outward: the first layer that disagrees is where the cause lives.
Step 4: Identify where the value changes
If the feed is right and the page is right but Merchant Center shows something else, the processed value is being altered along the way. Look at what Merchant Center has stored for the product, then at what the page shows after plugins, apps or theme code have run. Fix the layer that changes the number, not the symptom.
The most common causes
Google's own list in the inaccurate price documentation is a good map of where to look. These are the ones we see matter most for small and mid-sized stores:
- Stale data after a sale starts or ends. The shop changes price at midnight; the feed still holds yesterday's value. Google names update timing as a common cause and recommends scheduling uploads, or using the Content API to update data after site changes.
- Sale dates and time zones. Google says an active sale price is shown as the current price in Shopping ads and listings, so sale-price dates and time zones must be correct. A sale that ends at 23:59 in one time zone can still be live in another.
- Structured data on the old price. The page looks right to a shopper, but the markup still holds the previous value.
- Multiple prices on a page. Sale and regular prices, price ranges, bundles and minimum quantities confuse the comparison when the feed holds only one of them.
- Variant preselection. The feed carries the price of one variant while the page loads another by default.
- Dynamic or location-based prices. Prices that change by visitor location or load slowly after the page.
- Handling fees and checkout increases. Google requires price consistency through checkout: the price must not increase there, although it may decrease after adding the item if a promotion applies.
Coupons and discount codes
A price that only appears after a coupon code is entered is not the price the page shows, so it should not go into [price]. Submit the price a shopper sees on the page, and handle promotions in ways Google supports.
VAT
For Sweden and the rest of the EU, consumer prices include VAT. Google says VAT must be included in [price] where required, while shipping is submitted separately. A feed exported from an accounting-style source that holds net prices will mismatch on every single product by the VAT amount, which is why that pattern is easy to spot: the gap is the same percentage everywhere.
Fixing it, step by step
- Correct the source, not just Merchant Center. If the catalog is wrong, a manual edit in Merchant Center is overwritten by the next feed fetch. Fix the price in the shop or catalog first.
- Align the markup. Make the structured data price and availability match the visible price. Re-test with the Rich Results Test.
- Move prices into the server HTML. If a script writes the price after load, have the theme or platform output it in the initial HTML.
- Correct sale dates and time zones. Make sure the sale start and end in the feed match what the shop does.
- Resubmit and wait for the recrawl. After correction the product can be recrawled. In Merchant Center you can filter under Products, Needs attention, edit affected products or download a CSV, fix it and upload it again.
- Check availability too. Google's guidance puts price and availability together, so a product that is out of stock on the page but in stock in the feed produces a related inconsistency.
This works the same whether the store runs on Shopify, WooCommerce or Magento. What differs is where the price is output: the platform's own template, an app that injects it, or a separate feed plugin that exports on its own timetable. If your feed comes from a plugin that refreshes once a day while your prices change several times a day, you have found your cause.
Do not lean on automatic item updates
Merchant Center can update product information automatically when it detects an error on your page. Google describes this as designed for sporadic accuracy problems, not as a replacement for frequent product-data updates. Frequent price changes may lead to disapproval, and too many mismatches can stop the updates. Google also sets a minimum match level between product data and schema.org markup for automatic price updates; if it is not met, automatic updates stop and the account may be at risk of suspension. Treat the feature as a net under the wire, not the wire.
For products whose prices change several times a day, or for large offer volumes, Google recommends considering the Inventory API for faster updates.
Selling in several countries and currencies
Multi-market stores multiply the places a mismatch can hide. Each country feed has its own price, currency and sometimes language, and each must agree with its own landing page.
- One currency per market. Without currency conversion enabled, product pages and checkout must consistently show the currency of the country where the products are sold. For a Swedish feed that means prices in kronor on the page and at checkout.
- Regional prices must agree. Google's regional pricing troubleshooting says the regional landing-page price must match the regional product-data price. The Needs attention filter, direct edits and a CSV re-upload are the tools it names.
- Separate feeds, separate IDs. The same SKU in a Swedish and a German feed is two offers. Keep identifiers consistent so you can compare like with like, and compare in the right currency.
- Exchange-rate drift. If you convert prices by an automatic rate on the feed side but the shop uses fixed local prices, the two will drift apart. Pick one method and use it on both sides.
If you sell across the EU, our guides on one Google Shopping feed for multiple countries and the German Merchant Center rules cover the structure of per-market feeds.
Preventing mismatches: make the feed follow the catalog
Most mismatches are timing problems. The shop changes, the feed lags. Prevention is therefore about two things: a single source of truth and a refresh rhythm that matches how often you change prices.
A prevention routine
- Hold prices in one place, the shop or catalog, and generate every channel feed from it.
- Schedule feed rebuilds to match your price changes: before and after sale starts, and at least daily for active catalogs.
- Keep sale dates in the feed, with the correct time zone.
- Check structured data after any theme or app update.
- Watch Needs attention in Merchant Center weekly, and the warning emails when they arrive.
- Audit the feed periodically against a checklist; our product feed audit template has 24 points and a CSV to work from.
Our guide to disapproved products in Merchant Center shows the feed-side fixes beyond price, and the Google Shopping feed rules guide explains how attribute rules keep values consistent across thousands of products.
How Textfinity fits in
Textfinity reads your catalog from Shopify, WooCommerce, Magento, PrestaShop or BigCommerce, from a CSV, TSV or Google Shopping XML export, or from a Google Sheet. It then maps, filters and publishes one feed per channel and market to a stable URL that rebuilds on a schedule. Because every channel and market feed is generated from the same catalog, the Swedish, German and Meta feeds are built from the same price data rather than from separate exports that drift apart.
Plans start with a Free tier at $0 per month, Basic at $4.99 per month ($49.90 per year), Standard at $9.99 per month ($99.90 per year) and Premium at $14.99 per month ($149.90 per year); see the pricing. If you would rather not wire it up yourself, we can set it up for you: send the store and the channels, and the catalog is connected and the feeds are built and registered with you in each channel's console.
Processing runs on German infrastructure, and for stores that care where product data goes, our page on EU-hosted product feed tools explains what to look for. Agencies running several stores can see how we handle per-client set-up.
FAQ
How long does Google take to re-check a product after I fix the price?
Google says the item can be recrawled after you correct it. The timing is not fixed, so correct the source first, confirm the page HTML and markup agree, and then check the status under Products in Merchant Center. Resubmitting the corrected data helps Google see the change sooner.
Why does Merchant Center show a mismatch when my page looks correct?
What you see in the browser is not always what Googlebot reads. A price written by JavaScript after the page loads, markup that still holds the old price, or a different variant preselected by default can all produce a mismatch while the page looks right to a shopper. Compare the server-returned HTML and the structured data with the feed value.
Does a mismatch affect the whole account?
It can. Google notes that too many mismatches can stop automatic item updates, and a failure to meet the minimum markup match level may put the account at risk of suspension. Fixing systematic causes early protects the account, not just the individual products.
Should prices in my Swedish feed include VAT?
Yes, where VAT is required, Google says it must be included in the price attribute, while shipping is submitted separately. The currency should be the one for the target country, so a Swedish feed shows kronor on both the page and at checkout.
Can I use a sale price that needs a coupon code?
No, not as the price. The price in the feed should be the one shoppers see on the landing page. Keep coupon-only prices out of the price attribute and use the sale price attribute only for a price that is visibly live on the page for the dates you set.
Sources
- How to fix: Mismatched product price, Google Merchant Center Help
- How to fix: Inaccurate price status due to inconsistency, Google Merchant Center Help
- How to fix: Insufficient match of microdata price, Google Merchant Center Help
- Allow Merchant Center to update product information, Google Merchant Center Help
- Checkout requirements and best practices, Google Merchant Center Help
- How to fix: Mismatched regional prices, Google Merchant Center Help
- Price [price], Google Merchant Center Help
- Standardised product data: what it is and how to use it