Google Changed My Product Price in Merchant Center — Why?

 


Google Changed My Product Price in Merchant Center — Why?

You submitted:

$59

But Merchant Center now shows:

$49

You didn't edit the feed.

Your feed app says it still contains $59.

So why did Google change it?

Before assuming Merchant Center is broken, I would check whether automatic product updates changed the offer to match what Google found on your website.

Because sometimes Google isn't creating the inconsistency.

It's exposing one that already existed.

First, Check Automations

Inside Merchant Center, go to:

Products & store → Products → Automations

Look for automatic updates related to:

  • price

  • availability

  • condition

These features can use information Google finds on your product page to correct certain mismatches.

For example:

Feed

$59

Product page

$49

Google may update the value used in your Shopping listing to:

$49

That can prevent a shopper from seeing $59 on Google and then landing on a page that only charges $49.

Useful?

Yes.

But I would not stop there.

Because the bigger question is:

Why did your feed say $59 while your website said $49?

Don't Treat the Automatic Correction as the Fix

This is the mistake I'd avoid.

Merchant Center changes the product from:

$59 → $49

The warning disappears.

You think:

Great. Problem solved.

But your source catalog still says:

$59

Tomorrow your feed syncs again.

Google receives $59 again.

Your product page still says $49.

Now the same mismatch can return.

Automatic updates are designed to help with temporary inconsistencies.

They are not a substitute for keeping your own product data synchronized.

So whenever Google automatically corrects something, I would treat it as a clue.

Not as the end of the investigation.

Find Out Where the $49 Came From

If Google changes your product price, I would check the page in this order.

What does the shopper see?

Open the exact submitted product URL.

Check:

visible price

If it says $49, that's your first clue.

Then check whether:

  • the product is on sale

  • the selected variant affects price

  • the currency changed

  • a subscription option is selected

  • a location-specific price is being displayed

Do not just open the general product family.

Check the exact offer Google receives.

Then Check the Structured Data

This is where things get interesting.

Your page may visibly show:

$59

but its structured data says:

$49

Google can read the machine-readable Product / Offer data underneath the page.

So you might have:

Feed

$59

Visible page

$59

Structured data

$49

From your perspective:

“Everything looks correct.”

From Google's perspective:

“This page contains another price.”

Use Google's Rich Results Test and inspect values such as:

price

priceCurrency

availability

If structured data contains an old value, find out what generates it.

It may come from:

  • your ecommerce platform

  • theme

  • SEO plugin

  • feed app

  • custom script

  • old schema markup

Fixing the feed won't fix stale schema.

What if Google Changed Availability Instead?

The same idea applies.

Your feed says:

in_stock

but Merchant Center shows:

out_of_stock

That may happen because Google found different availability information on the product page.

Again, check the whole chain.

Feed

in_stock

Visible page

In stock

Schema

OutOfStock

Or maybe:

Feed

in_stock

Default variant

Sold out

Google's automatic update is not necessarily the root problem.

The root problem may be:

different parts of your site describe different offers.

Check When Google Found the Difference

Timing matters.

Imagine this:

10:00 AM

Website: $59
Feed: $59

11:00 AM

Sale starts.

Website: $49
Feed: still $59

1:00 PM

Google checks the page.

It sees:

$49

3:00 PM

Your feed finally refreshes.

Now:

Website: $49
Feed: $49

When you investigate later, everything matches.

That doesn't necessarily mean Google's earlier update was wrong.

There may have been a real mismatch during the gap.

This is especially common with:

  • flash sales

  • automated repricing

  • frequent inventory changes

  • large catalogs

  • once-daily feeds

If prices or inventory change often, update timing becomes part of data quality.

One Case I'd Investigate Immediately

Suppose Merchant Center automatically changes:

2 products

out of a catalog of 10,000.

That may be an isolated mapping issue.

But if it changes:

2,000 products

I would stop checking individual SKUs.

That pattern suggests a system-level problem.

Maybe:

  • the feed hasn't refreshed

  • an integration is sending old prices

  • your schema generator changed

  • a currency configuration broke

  • a sale started on the store but not in the feed

Large-scale automatic corrections are a signal to inspect the pipeline.

Should You Turn Automatic Updates Off?

Usually, not as the first troubleshooting step.

If Google is correcting:

feed $59 → website $49

turning automation off does not magically make $59 correct.

It can simply remove the safety net.

I would first answer:

Which value is actually correct?

Then:

Why do my systems disagree?

Once you understand that, you can decide whether the automation setting fits your setup.

Google's own guidance is clear that automatic updates are meant to help with occasional mismatches—not replace regular, accurate product-data updates.

One Important Exception: Pages With Lots of Prices

Price pages can get messy.

A single page may contain:

  • regular price

  • sale price

  • MSRP

  • member price

  • subscription price

  • strikethrough price

If your page presents several prices unclearly, Google may have difficulty understanding which one represents the actual submitted offer.

This is where I would check both:

what shoppers see

and:

what Product / Offer structured data says

The cleaner the relationship between:

offer → price → variant → schema

the easier the page is to interpret.

What I'd Do Before Changing Anything

If Google automatically changed one of my products, I'd ask:

1. What value did I submit?

↓

2. What does the exact landing page show?

↓

3. What does Product / Offer structured data say?

↓

4. Which variant opens by default?

↓

5. When did the feed last update?

If those five answers don't agree, I would fix the source that is wrong.

Not the system that happened to expose it.

Check the Public Product Page First

If you're not sure whether your own product page is sending conflicting signals, you can start with a small sample.

Mingche checks three public product URLs from the same store for signals including:

  • price

  • availability

  • variants

  • structured data

Check 3 Product Pages for Free →

https://mingcheip.com

The goal isn't to guarantee Google approval or rankings.

It's to answer a simpler question first:

“Does my product page itself tell one consistent story?”

If the page is clean but your feed still contains different values, the next investigation belongs in your product source or feed pipeline.

Bottom Line

If Merchant Center automatically changes your price or availability, don't immediately ask:

“How do I stop Google from doing this?”

Ask:

“What did Google find on my website that disagreed with my feed?”

Then follow the chain:

source catalog

→ feed

→ landing page

→ variant

→ structured data

→ Merchant Center

Automatic updates can protect the shopper from some temporary mismatches.

But repeated automatic corrections usually mean something upstream still needs attention.

Disclaimer

Mingche is an independent product-data readiness service and is not affiliated with or endorsed by Google.

Product-data auditing or correction does not guarantee approval, visibility, ranking, traffic or sales. Google independently determines Merchant Center eligibility and how products appear across its services.

Comments

Post a Comment

Popular posts from this blog

Before you upload a product feed: check the row, the variant and the page

A product file can look tidy and still describe the wrong offer. The useful question is whether each row points to the product a customer can actually buy, at the price and availability you submitted. Start with a copy of your catalog export. Keep the original and record when it was exported. The following is a short review workflow for English product data and US-dollar offers. It is a starting point, not a complete Merchant Center compliance checklist. First confirm which file you are checking A current-looking spreadsheet can still cover only a selected set of products, or differ from the file Merchant Center last received. Keep the export time and the source version with your notes. Working from Shopify: use the export selection and coverage checklist to distinguish the rows you selected from the full catalogue. A Shopify export is source evidence, not automatically a ready-to-upload Google feed. The file looks right but an issue remains: check the last file Merchant Center ac...
Read more
Image
  Merchant Center Says “Missing Brand” — Should You Use Your Store Name? You open Merchant Center and see: Missing brand The obvious fix seems easy. Your store is called: YourStore So you type: Brand: YourStore Save. Done? Not necessarily. The brand field is supposed to describe the brand of the product , not simply the company selling it. That distinction matters. Before changing hundreds of products, I would first figure out which of these situations you are actually in: You sell another company's product. You manufacture the product yourself. You sell a private-label product. The product genuinely has no recognized brand. Those four situations should not automatically receive the same value. First: Ask Who Actually Branded the Product Imagine your store sells a pair of Adidas shoes. Your business is called: YourStore The correct brand is not: YourStore It is: Adidas because that is the product brand shoppers recognize. Google's current brand specification says the value sho...
Read more

Before importing a repaired product CSV, ask for the change log

A repaired CSV should come with an explanation of what changed. Otherwise, you are being asked to upload a file without knowing whether it fixed a formatting problem or silently guessed a product fact. Keep the original export. Before importing any proposed replacement, review a change log that lets you trace a changed field back to the same product and its evidence. This is an illustrative workflow, not a customer case study or a promise that every field can be repaired. Prepared with AI assistance by Rowmint, the product-data education brand of Mingche Commerce. Three rows, three different decisions Example issue Evidence available Appropriate next step A field contains accidental surrounding spaces The receiving field's rules and the intended value are known Propose a supported formatting correction; show old and new values A product identifier is missing No manufacturer record supplied Request the source identifier or relevant product evidence; do not invent digits The lin...
Read more