You mark your best seller down 20% on Friday afternoon. The sale price goes live on the website at 4:00. Your product feed, the file that tells Google what you sell and what it costs, refreshes overnight. Somewhere in between, Google visits the product page, finds a price that does not match the one you gave it, and quietly switches the product off.
Come Monday, the sale has had a strong weekend on your site, and your best seller has not appeared in a single Google Shopping result since Friday evening. Nobody called. There was no dramatic warning. There is a small red notice in an account you do not open very often, and a gap in your sales you will not connect to it for a week.
This is one of the most common reasons products disappear from Google, and Google says so itself: its own Merchant Center team calls price mismatches one of the most prominent causes of product disapprovals. The good news is that almost every mismatch comes from a handful of ordinary, fixable things, and none of them require you to become a developer. They do require you to understand how Google checks your prices, because it checks them in two very different ways, and they carry very different consequences.
One Feed Runs More of Your Google Ads Than You Think
Start with why this matters more than a single product going missing. If you sell online, the price, photo and title that appear in Google Shopping come from your product feed, which lives in Google Merchant Center. We have written about why the feed is the campaign for Shopping ads: there are no keywords, so the data you submit decides where you show up.
What most owners miss is how much else runs off that same feed. Performance Max, the campaign type Google pushes hardest for online stores, pulls its product listings from Merchant Center. The free product listings on Google's Shopping tab come from it too. So a disapproved product does not just lose one ad. It drops out of Shopping, out of the shopping placements inside Performance Max, and out of the free listings at the same moment.
Google is strict about price for a reason that is hard to argue with. A shopper who sees $80 in the ad and $96 on the page feels misled, leaves, and you have still paid for the click. Google would rather show nothing than show a price your store will not honor. The rule it enforces is simple to state: the price in your feed, the price on your product page, and the price in the page's code must be the same number, for every shopper, every time Google looks.
Google Checks Your Prices Two Different Ways
Most confusion about price mismatches comes from not knowing there are two separate checks. Google's own Merchant Center guides draw the line clearly: item-level problems come from a crawler, and account-level problems come from a person.
The crawler checks one product at a time. Googlebot, Google's automated visitor, opens your product pages several times a day, on both the desktop and mobile versions of your site, and compares what it finds with what your feed says. If they disagree, Google disapproves that product immediately. Once the page and the feed match again and Google recrawls it, the product comes back on its own. This is the Friday-afternoon problem, and it is annoying but contained.
The reviewer checks your whole account. Separately, Google's policy team runs manual reviews. A real person picks products at random from your feed, reads the price you submitted, clicks through to your product page, and compares the two. If they find mismatches consistently, you get a warning email with examples and a firm deadline. When that deadline arrives, a reviewer checks a fresh set of products. If the problem is still there, Google issues what it calls a preemptive item disapproval: a large share of your feed is switched off, and Google's own explanation is that this includes products that may be fine.
The difference matters because the fixes are different. An item-level disapproval is a symptom you can clear product by product. An account-level warning means Google has decided you have a pattern, and it wants to see the pattern gone, not a handful of products patched.
Six Ordinary Things That Put Two Prices in Front of Google
When a store gets flagged for price mismatches, it is rarely because someone typed the wrong number. It is usually because the website and the feed are two systems updating on different schedules, or because the page shows a price a person reads correctly and a crawler does not. These are the six causes we see most, and every one of them is on Google's own list.
1. The update gap. Google's example is precise. The website price changes at 4:00 p.m. The feed is not updated until 4:30. The crawler visits at 4:20, sees the new price on the page and the old price in the feed, and disapproves the product. The gap is never zero, so Google's advice is to keep it as short as possible and to update the feed after the website, not before. A feed that says $80 while the page still says $100 is advertising a price you do not yet charge, which is the exact thing the rule exists to stop.
2. A sale entered by overwriting the price. Most platforms let you run a sale by simply changing the price. The feed has a better way. Google supports two prices per product: the regular price and a separate sale price, with a sale price effective date that tells Google when the sale starts and ends. Use those, leave the regular price alone, and Google knows exactly which number to expect on the page and for how long. Overwrite the price instead, and every sale you run becomes two manual edits that have to land at the same moment, twice.
3. A page that shows more than one price. A human sees a crossed-out $150, a bold $100, and understands instantly. A crawler sees two numbers. Google's rule is that the lower price must be the most prominent one and must be submitted as the sale price. Pages also carry prices you might not think about: a "you may also like" row under the product, a bundle offer, a financing line that shows a monthly payment. Every extra price on the page is another chance for Google to read the wrong one.
4. Variants. A shirt in five sizes or a table in three finishes is one page with several prices. If the page loads with no option selected, the crawler may find no price at all, or the price of whichever variant the page defaults to. Google asks for each variant in your feed to have its own link that opens the page with that variant already selected. The same problem hides in the page's code: on some store themes, the price tag in the code shows the first variant's price regardless of which one the shopper picked.
5. Prices that change by location. Currency-switcher apps that detect a visitor's country and convert the price, or pricing that changes by cookie, browser or device, are all against Google's rules. Googlebot does not always visit from where you expect, so it can land on a converted price that matches nothing in your feed. If you genuinely charge different prices in different regions, Google has a proper feature for it called regional pricing. If a switcher app is running and you are seeing mismatches, turning the app off for a day or two is the quickest test.
6. A price the crawler never reaches. Some pages load the price a moment after everything else, through a script. Google warns that if the price is calculated and added late, or the page is slow, the crawler can miss the final number. Others block Google outright without meaning to: a security plugin that treats bots as threats, a rule that blocks traffic from certain countries, or a line in the site's settings that tells crawlers to stay out. If Google cannot read the page, it cannot confirm the price.
Notice that none of these is carelessness. They are the normal side effects of running a store: sales, variants, apps, themes, security. That is why they catch careful owners.
How to See the Price Google Saw
You do not have to guess which of those six you have. Merchant Center shows you the evidence, if you know where it lives.
Start in Products, then the Needs attention tab. This is the early-warning screen, and it lists every product with a problem, grouped by issue. Resist the pull of the general notifications area, which is mostly Google suggesting features. The issues that switch products off live in Needs attention.
Open one of the affected products and scroll to the details. Merchant Center shows the value it found on your website beside the value in your feed, and it shows when the crawler last visited. That timestamp is the most useful thing on the screen. If the crawl happened twenty minutes after you changed the website and before the feed refreshed, you have found an update gap. If the website value is a price you have never charged, you have a page that is showing Google something different from what shoppers see.
To see what Google sees, use Google's free Rich Results Test. Paste in the exact product link from your feed, including any variant code on the end, run the test, and choose to view the tested page. You get a screenshot of the page as Googlebot rendered it and the price data it found in the page's code. If that screenshot does not look like the page you see in your own browser, something on your site is showing Google a different version, and Google treats that as a serious problem in its own right.
Finally, check who is actually receiving Google's emails. Account-level warnings are emailed to the account's owners and admins. In a lot of small stores, that list still includes a developer who built the site, an agency you left, or an employee's old address. A warning with a hard deadline that lands in an inbox nobody reads is how a fixable problem turns into a suspended feed. Go to the account's access settings, remove anyone who no longer works with you, and make sure a person who opens email every day is on it.
You Get One Courtesy Review. Don't Spend It Early.
If you receive an account-level warning, the rules are strict and worth knowing before you touch anything.
The warning email includes specific products a reviewer checked and found mismatched. Treat them as a pattern to understand, not a list to fix. If three of the examples are sale items, your sale process is the problem, and every other sale item in the feed has it too. If they are all products with sizes, it is your variants. Google says plainly that there is no complete list of affected products, so fixing only the examples in the email is how stores fail the next review.
Google does not extend the deadline in the email. During the warning period you get one courtesy review, which you can request at any time before the deadline. A reviewer checks a fresh set of products, and if they all match, the warning is lifted. If any do not, you stay warned until the deadline, and you have spent your only early chance. So fix the pattern first, check it yourself across a good sample of products, and only then ask.
If the deadline passes and a large part of your feed is disapproved, you request a new review with the "I fixed the issue" option. Google says a review takes seven business days to complete, and failing it puts the account into a cooldown of seven business days before you can ask again. Rushing a review you are not ready for can therefore cost you roughly two working weeks of Shopping and Performance Max sales. In a normal month that hurts. During the holiday rush it can cost you the season, which is one more reason holiday preparation starts in September.
A site that disagrees with what you have told Google is also exactly what Google's misrepresentation reviews look for, and those can end in a suspension of the whole account. We have covered what that does to a business in Your Ad Account Is Not Yours. You do not want to be arguing with Google about prices and trust at the same time.
Automatic Updates Are a Seatbelt, Not a Sync
There is a setting in Merchant Center that sounds like it solves all of this. Under Automations, automatic updates for price, availability and condition let Google correct your listings using the price it finds on your page. If your feed says $4 and the page says $3, Google shows $3. According to Google's current help pages, these automatic updates are switched on by default.
Leave them on. They are genuinely useful for the occasional mismatch that slips through. But read Google's own description of what they are for, because it is more modest than the name suggests. Google says automatic updates are designed to fix sporadic problems on a small percentage of products and are not a replacement for keeping your feed current. It says they may not work for products whose price changes more than once a day, that those products may be disapproved instead of updated, and that Google may stop the updates altogether if the number of mismatches becomes too large.
In other words, automatic updates protect a store that is mostly right. They do not rescue a store whose feed is regularly out of step with its site. The real fix is upstream:
- Let your store platform feed Google directly. Shopify, WooCommerce and BigCommerce all have Google integrations that push product changes to Merchant Center as they happen. A feed that someone uploads by hand, or a spreadsheet exported once a week, will always drift.
- If you use a separate feed tool, check its schedule. Look at when the feed last updated in Merchant Center. A feed that refreshes once a day is fine for a store whose prices change once a month and a liability for a store running weekend sales.
- If your prices change several times a day, that is a job for Google's API, which is built for frequent updates. That is a conversation for whoever built your site, not a setting you can switch on.
The same discipline applies to stock. Google enforces availability exactly the way it enforces price, which is why we recommend keeping sold-out products in the feed rather than deleting them. And a clean, current feed is increasingly what gets your products recommended when shoppers ask an AI assistant what to buy, so the work pays twice.
A Price Change Is Now a Two-Step Job
Here is the routine we would give any small online store. It takes a few minutes per sale and about ten minutes a week.
Before a sale. Enter the discount in your feed as a sale price with start and end dates, and leave the regular price as it is. If your platform's Google integration handles sale prices automatically, confirm it once by checking one product in Merchant Center after you schedule the sale. Decide who is changing the website and when, so the site and feed move together.
When the sale starts. Change the website first, then make sure the feed follows as quickly as your setup allows. Pick three products, including one with variants, and run them through the Rich Results Test. You are looking for the sale price in the screenshot and in the price data.
When the sale ends. This is the step everyone forgets. The regular price comes back on the website, and a sale price that is still live in the feed is now a mismatch in the other direction. If you used effective dates, the feed handles it. If you did not, repeat the start-of-sale check in reverse.
Every week. Open Needs attention. Look for anything with a price, availability or crawl issue, and check the crawl timestamps on anything new. It is ten minutes, and it is the difference between catching one disapproved product on a Tuesday and finding out from your sales report a month later.
Give it one owner. The most common reason this goes wrong in a small business is not technical. It is that the person who changes prices on the website, the person who manages the feed, and the person who runs the Google Ads account are three different people, or one person wearing three hats on three different days. Whoever owns it needs to know that on your store, a price change is not finished until Google agrees with it.
Your Price Is Part of the Ad
It is easy to think of Merchant Center as a technical back room, separate from the advertising. It is not. For an online store, the feed is where Google reads your product, your price and your promise to the shopper, and it checks that promise against your website constantly. When the two disagree, Google does not split the difference. It turns the product off, and the campaigns built on the feed, including Performance Max, go quiet with it.
The fix is rarely dramatic. Put sales in the sale price field with dates. Make each variant link open with that variant selected. Keep one price prominent on the page. Let your platform sync the feed, update it after the site, and look at Needs attention every week. If a warning arrives, fix the pattern before you spend the review.
If you would rather hand that to someone, keeping Merchant Center healthy is part of how our Google Ads management team runs Shopping and Performance Max for online stores, and we check the feed before we touch a bid. If you are doing it yourself, the ten minutes a week above will catch most of it before Google does.
