Stopping Google From Silently Overriding Your Feed's Price and Availability Data

Google Merchant Center can rewrite four fields in the feed you submit without asking you first: price, sale price, availability and condition. It pulls the replacement values straight from the structured data markup on your product pages, and it does this by default on every new Merchant Center account (support.google.com/merchants/answer/15623993). If your product page is slow to update, cached by a CDN, or simply wrong, Google will still trust it over your feed. This guide is for anyone running paid Shopping campaigns or free listings who has noticed a price, stock status or condition in Google that does not match what they submitted, and walks through how to find out which of your listings this is happening to, and how to lock the fields that matter.

What "automatic item updates" actually changes

Google calls this feature automatic item updates, and as of September 2025 it lives in Merchant Center under Products & store > Products > Automations, where every automation gets its own on/off toggle and a plain-language impact estimate (support.google.com/merchants/answer/15623993). Three sub-automations are switched on by default for every account: price updates, availability updates and condition updates. Two more are optional and must be turned on deliberately: shipping updates and image improvements (support.google.com/merchants/answer/3246284).

Google's own explanation of the mechanism is direct: "We automatically read the structured data markup on your online shop using our advanced data extractors and directly pull product data from your HTML into Merchant Center." The worked example Google gives in its help center is worth repeating exactly, because it shows how small a gap triggers a rewrite: if your most recent feed upload prices an item at 4 GBP, but the live product page lists it at 3 GBP, Google updates the live ad or free listing to 3 GBP, not your submitted 4 GBP.

Availability uses looser matching than price does. Google's documentation states that "in_stock, preorder and backorder are all considered compatible with in_stock" for the purposes of this automation, so a page that briefly shows "backorder" will not necessarily trigger a correction, but a page that shows "out of stock" against a feed that says "in stock" will.

Why this exists, and why it is not automatically bad

The stated purpose is to prevent disapprovals caused by stale feed data: "If the extractors are unable to determine price, availability or condition information, your products will be subject to product-level disapprovals" (support.google.com/merchants/answer/3246284). In other words, Google built this as a safety net for merchants whose feeds lag behind their storefronts. For a store with reliable schema.org Product markup and an infrequently updated feed, it genuinely reduces disapprovals.

The problem is the assumption baked in: that the live page is always more current and correct than the feed. That breaks in a few situations we see often in feed audits:

• The storefront uses a CDN or full-page cache that lags 15 to 60 minutes behind a price change, so Google's crawl catches the old price.
• The site's structured data was set up once, years ago, and never updated when a new pricing engine or promotion module shipped, so it reports last month's sale price.
• A regional or currency-specific storefront serves different structured data than the one Google is crawling for that market.
• The feed is deliberately more conservative than the site, for example holding an item as "in stock" for a defined buffer window while a warehouse count is reconciled.

In every one of these cases, automatic item updates makes Google show the wrong number in the ad, and it does so silently. There is no email. The only trace is a line item in the Merchant Center diagnostics feed, under an issue labeled exactly "Automatic updates: Mismatched price", "Automatic updates: Mismatched availability" or "Automatic updates: Mismatched condition". It is a different failure mode from the account-level suspensions we covered in our misrepresentation-suspension recovery guide: nothing here gets your account suspended, but it does mean the ad your customer clicks may not reflect the deal you meant to run.

A concrete example

Submitted feed: price: 1299.00 TRY, availability: in stock
Live product page (behind a 40-minute CDN cache after a flash-sale price cut): structured data shows 1199.00 TRY
Google's crawler reads the cached page, flags "Automatic updates: Mismatched price", and republishes the listing at 1199.00 TRY — a price the merchant never submitted and the sale terms never authorized for that channel.

The feed was correct. Google's correction was the error, and it looked identical in the diagnostics tab to a case where the feed genuinely was stale.

Diagnostic checklist: is this happening to you

1. Open Products & store > Products > Diagnostics and filter for issues containing "Automatic updates." Each one lists the affected item count and a sample of affected offer IDs.
2. Open Products & store > Products > Automations and check whether price, availability and condition updates are toggled on (they are, by default, unless someone has already turned them off).
3. Pick three flagged offer IDs and compare three values side by side: your submitted feed value, the value currently live in the Shopping ad or free listing, and the value in your storefront's own schema.org/Product or Product structured data (view page source, or use Google's Rich Results Test) at the time of the check.
4. If the live ad matches the structured data but not your feed, and the structured data is wrong, the root cause is on your website, not your feed. Fixing the structured data (or its caching delay) fixes the ad without touching any Merchant Center setting.
5. If you migrated from Content API for Shopping to Merchant API this year, re-check every automatic-improvement toggle. Content API for Shopping reached its sunset on August 18, 2026, with progressive request errors starting September 1, 2026 for anyone still calling it (developers.google.com/merchant/api/latest-updates, page current as of September 24, 2026). Automatic item updates now live under a dedicated automaticImprovements resource in Merchant API, and a rushed migration is a common way for these toggles to silently reset to their defaults.

Turning it off, entirely or field by field

In the Merchant Center UI, go to Products & store > Products > Automations, open the automation you want to change, click View details, and use the toggle to turn that specific update on or off. This works for price, availability, condition and shipping updates. Image improvements and shipping improvements can only be managed this way in the UI as well, but two of the controls are API-only.

Anyone connecting through Merchant API controls the same behavior with explicit boolean fields on the account's automaticImprovements resource (developers.google.com/merchant/api/guides/automatic-improvements/overview):

The Merchant API documentation is explicit that updating this resource is a full replacement of the whole component, not a partial patch: send all six fields with every update, not just the one you meant to change, or you risk resetting the others to their defaults (developers.google.com/merchant/api/guides/automatic-improvements/overview).

Deciding what to actually turn off

Turning everything off is not automatically the right call. It removes the safety net for the disapprovals the feature was built to prevent. The more useful framing is per-attribute:

• Keep price and availability updates on if your structured data is reliably accurate and your feed refresh cadence is genuinely slower than your website's price changes.
• Turn price updates off if you run time-boxed promotions where the feed price is intentional and different from a cached or pre-release version of the page.
• Leave strict availability updates off (its default) if your operations team holds items available during a reconciliation window a literal page read would contradict.
• Leave condition updates on in most cases; condition mismatches are rarer and the failure mode (a used item marked new, or vice versa) is usually a genuine data problem worth catching.

What this doesn't cover

This is specific to Google Merchant Center. Meta Commerce Manager and TikTok Shop have their own catalog reconciliation behavior, and none of it is documented in the same place or governed by the same toggles; treat each channel as its own audit. This also does not cover Google's separate "autofeeds" mechanism, where Google builds a feed entirely from crawling your site with no submission at all — that is a different feature for a different problem (no feed at all, rather than a feed being partially overridden) and deserves its own audit.

If the root cause is broken or missing structured data on your site rather than an aggressive Google setting, no Merchant Center toggle fixes that; you have to fix the markup itself, and Google's Rich Results Test is the fastest way to see what its crawler is actually reading. Feed monitoring tools like Channable and DataFeedWatch surface a similar mismatch-diagnostics view channel by channel; the real difference is whether the fix loop, from spotting the mismatch to correcting and republishing the feed, happens in the same place you manage the feed itself, which is a workflow preference more than a technical limitation of any one tool. GTIN and identifier errors are a related but separate class of disapproval, covered in our GTIN error guide.

Where Feedance fits

Feedance treats your enriched feed as the single source of truth pushed out to each of its 200+ connected channels through the Google Merchant Center integration, so a Google-side override shows up as a visible mismatch against that source of truth rather than disappearing into a Merchant Center tab nobody checks daily. Feed monitoring is what catches the drift in the first place; the toggle decisions above are still yours to make in Google's own interface. Feed refresh cadence depends on plan (Essentials syncs daily; Business syncs hourly), which matters here because a feed that only refreshes once a day gives automatic item updates a full day of gap to fill with page-crawled data before your next submission corrects it.

Frequently asked questions

What is Google Merchant Center automatic item updates?

It is a Google feature, on by default, that reads structured data from your product pages and uses it to overwrite the price, availability, condition and (optionally) shipping and image data you submitted in your feed, whenever Google's crawler finds a mismatch.

Which attributes can Google change without my feed submitting a new value?

Price, sale price, availability and condition by default. Shipping speed estimates and image improvements are separate sub-automations that are off by default and must be enabled deliberately.

Will turning this on fix all my Merchant Center disapprovals?

No. It only resolves disapprovals caused by a mismatch between your feed and your live page for the four covered attributes. GTIN errors, policy violations, and misrepresentation issues are unrelated and need their own fixes.

Can I turn off automatic item updates completely?

Yes, per attribute, either in Merchant Center under Products & store > Products > Automations, or via the four update-related boolean fields on the Merchant API automaticImprovements resource if you manage your account through the API.

Does this affect my Meta or TikTok Shop catalog too?

No. This specific mechanism is Google-only. Meta Commerce Manager and TikTok Shop have their own, separately documented catalog reconciliation behavior that this article does not cover.

I migrated from Content API for Shopping to Merchant API this year. Should I recheck anything?

Yes. Automatic item updates now live under a dedicated automaticImprovements resource in Merchant API, and because updates to that resource replace the whole set of fields at once, a rushed migration script that patched only one field can silently reset the others to their defaults.

How do I know if Google has already changed my listing?

Check Products & store > Products > Diagnostics for issues labeled "Automatic updates: Mismatched price," "Mismatched availability," or "Mismatched condition." Each entry lists a sample of affected offer IDs so you can compare feed value against live value directly.

Should every merchant leave this switched off?

No. For stores with accurate structured data and a feed that refreshes slower than the storefront, it reduces disapprovals with no real downside. The risk is specific to stores where the live page can be stale, cached, or intentionally different from the feed.

Does Feedance manage this setting for me?

Feedance manages your enriched feed as the source of truth pushed to Google and 200+ other channels; the automatic item updates toggle itself is a Google Merchant Center account setting that you control directly in Google's own interface or API, not something a feed platform can switch on your behalf.

What's the difference between automatic item updates and autofeeds?

Automatic item updates corrects specific attributes in a feed you already submit. Autofeeds is a separate Google mechanism that builds a feed from scratch by crawling your site when no feed has been submitted at all. They solve different problems and are controlled separately.

Run a free product feed audit to see where your submitted values and your live channel data have already drifted apart.