Academy › Publish › Get found on Google
The price you change in your store versus the one Google is still showing
Decide how you'll keep the price you give Google up to date, with a sheet that Merchant Center reads on its own or by forcing a refresh, so today's sale price doesn't still show the wrong number on Google tomorrow.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
A listing being approved in Merchant Center doesn't mean it's up to date. On Tuesday you drop the price of a chair from $89 to $69 because a sale starts. Your site updates instantly: anyone who visits now sees $69. On Thursday, in Google's Shopping tab, that same chair is still showing $89.
Nobody messed up here. The price shoppers see in the ad doesn't come from your site the instant they look. It comes from a copy, the feed, and Google reads that copy on a schedule, not continuously. Between the moment you change the price and the moment that copy catches up, there's a gap, and two bad things can happen in that gap at once: someone clicks expecting $69 and lands on a page that already says something else, and Google, if it notices the price you gave doesn't match your page, can reject the product until it's fixed.
How your catalog gets into Merchant Center, with a file you upload yourself or a sheet Merchant Center reads on its own, is one decision. What we're deciding here is another: how you keep the price from falling behind every time you touch it once it's in. Because you will touch it. You launch a sale, adjust for the season, fix a one-dollar mistake: every time, the lag clock starts running again.
Where Google gets the price from, and why it takes time
Google doesn't check your site live every time someone searches for a chair. It reads whatever you gave it, based on how you gave it: if it's a Google Sheet or a file hosted at a web address, Merchant Center reads it again every 24 hours; if it's a file you upload yourself, only when you upload it, which is the same as saying: never, until you decide to.
That schedule is the gap we were talking about. If the last read happened overnight and you change the price at ten in the morning, Google can keep showing the old price until the next one, and anyone comparing your ad to your site is going to see two different numbers. And if your feed is a file you upload yourself, no clock marks that gap anymore: it's marked by whatever day you remember to upload it, which could be that same afternoon or could be next week. If your page carries the price in structured data, Merchant Center tries to update it on its own, but don't count on that: your feed still has to be the one telling the truth.
The feed updates at the next scheduled fetch, not the moment you change the data
A sheet Merchant Center reads on its own, or a file you upload yourself
This is where you decide whether the lag depends on a clock or on your memory. With both, you're changing the price in two places, the store and the feed; the difference is in the step after that: the sheet gets read by Merchant Center on its own, and the file only gets there if you remember to upload it.
- You change the price in the store and in the sheet, and Merchant Center picks it up at the next read without you uploading anything
- The delay is just the time between reads, a day at most, not however long it takes you to remember to upload a file
- It holds up the same whether you change one price a month or twenty a week
- Every time you touch a price you have to touch two places, the store and the file, and then upload it too
- The delay is set by whatever day you remember to upload it, and a forgotten upload doesn't send a warning: the product can sit rejected until you notice
Which one to pick: If you touch prices more than a handful of times a month, sales, seasonal changes, stock adjustments, go with the sheet Merchant Center reads on its own. The manual file only holds up if your catalog is small and prices haven't moved in months.
The day you change a price
- 1Change the price in both places
in your store and, at the same time, in the feed's sheet or file: if you only change it in one, you've already got a lag - 2If your feed is a file, upload it that same day
not next week or whenever you get a spare minute: the lag starts counting from this moment - 3Check when the next read is due
in Merchant Center, under your data sources; if the sale can't wait, the "Update" button on that source forces a manual read - 4Check again the next day
open the product listing in Merchant Center and compare the price to your store's; if they don't match, don't wait for it to fix itself
A wrong price doesn't stay contained to that one product
- You know why the price in the ad and the price on your site don't change the same second: the feed is read on a schedule, not live
- You've decided whether your feed is a sheet Merchant Center reads on its own or a file you upload by hand, and what the difference is between depending on a clock and depending on your memory
- You have the four steps for the day you change a price, including forcing a fetch when the sale can't wait for the schedule
- You know that a lag across many products can end up as a warning about your account, not just about those products
Three cases to decide
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. You drop the price of a chair from $89 to $69 for a sale that starts Friday morning, and your Google Sheet gets read once a day. What do you do to make sure it's already showing $69 on Friday?
On Friday morning, as soon as you change the price in the store and in the sheet, you force the read from Merchant Center with that source's «Update» button, instead of waiting for the day's scheduled read: the sale can't depend on the feed's clock. If you'd rather have it ready by Thursday, Google has a sale price with a start and end date built in for exactly that.
2. You've been uploading a price file yourself every time something changes for months, and last week you forgot to update two products whose prices had gone up; one has been rejected for incorrect pricing for four days. What do you decide?
Move the feed to a Google Sheet that Merchant Center reads on its own every day: you still change the price in the store and in the sheet, but the step of uploading the file disappears, and that's the step you keep forgetting. A manual file only makes sense when the catalog's prices barely change, and that's no longer the case here.
3. This month twelve products got rejected at once for incorrect pricing, after you raised all your seasonal prices the same day. What do you actually risk if it happens again next season, and what do you change?
You're not just risking those twelve products staying down until they're fixed: if the mismatched prices add up, Google can escalate from a per-product notice to a warning about the whole account, and if you don't fix it in time, to suspending it. You change the timing: update prices in the store and force the feed read the same day, instead of waiting for the scheduled one.
You force the feed read the same day you update prices, and that habit saves you plenty of outdated-price warnings. But the feed keeps changing every week, and with it come new listings that Google rejects for reasons you don't fully control. That's where the habit of checking Merchant Center's «Needs attention» tab every week comes in.
NextA rejected product doesn't count until you fix it: how you know