Pingverablog ← Blog
Home › Blog › Merchant Center Price Mismatch: Keep Black Friday Sale Prices in Sync With Googl

Merchant Center Price Mismatch: Keep Black Friday Sale Prices in Sync With Google

November 7, 2026 · 11 min read

Merchant Center Price Mismatch: Keep Black Friday Sale Prices in Sync With Google

A Merchant Center price mismatch means Googlebot found one price in your product data and a different price on the landing page or in its structured data. Google's help page says the affected product "may be disapproved", and that mismatches "may lead to an account suspension." During a sale the risk goes up, because prices change on the website and in the feed at different moments.

To prevent it before Black Friday (27 November 2026), send the sale as sale_price plus sale_price_effective_date with an explicit timezone, keep price as the full price, make sure the price is in the page HTML rather than added later by JavaScript, and check your top products on the morning the sale starts and the morning it ends.

At a glance

  • Google compares the price (and sale_price, if sent) in your feed with the price in the landing page HTML and structured data. A price inserted by JavaScript after page load "will trigger an error", per Google.
  • sale_price_effective_date uses the format YYYY-MM-DDThh:mm[±hhmm]/YYYY-MM-DDThh:mm[±hhmm]. Without a timezone, Google assumes UTC.
  • If you send sale_price with no effective date, Google applies the sale price immediately.
  • Merchant Center automations for price are on by default, but Google warns they may not work for prices that change more than once a day, and may disapprove instead of update.
  • After a fix, Googlebot re-crawls disapproved products "over the next few hours or days". A requested website check can take up to 12 hours.

Why it matters now

Black Friday falls on Friday 27 November 2026 and Cyber Monday on 30 November. Most stores change hundreds of prices in that week, often twice: once when the sale opens and again when it closes. Each change opens a window in which the website and Merchant Center disagree.

As of November 2026, Google's help page "How to fix: Mismatched product price" lists five common causes:

  • delays between website updates and feed updates;
  • incorrect structured data markup;
  • a price shown to Googlebot that differs from the price shown to users;
  • wrong dates or timezone in sale_price_effective_date;
  • minimum-order or bulk quantities not submitted as the total price.

The first and fourth are the usual sale-week problems. A store schedules its sale to start at midnight local time, the feed sends dates without a timezone, and Google reads them as UTC. For a store at UTC-5, Google switches to the sale price five hours before the website does. For a store at UTC+2, the website shows the sale price two hours before Google expects it. Either way, Googlebot may crawl during the gap.

Strikethrough prices have their own issue type. Google's page on "Mismatched strikethrough price (page crawl)" says that when the struck-through price on your site does not match your price attribute, "the original price of your product is discarded and will not be shown as a strikethrough price." The product stays live but loses the sale annotation, which is the part shoppers notice in a Black Friday listing.

If you also run Merchant Center promotions, read Merchant Center Promotions for Black Friday. Promotions handle coupon codes, while sale_price handles a lower displayed price. This article covers the second case.

Step-by-step: prepare sale prices this week

  1. Pick the products that matter. Export the top 50 by revenue from last year's peak plus everything in this year's ads.
  2. Decide how the sale reaches Google. Google's documentation describes this pattern: keep price at the full price and add sale_price with sale_price_effective_date. Google's sale_price page requires the sale price to be lower than price and asks you to "clearly display both non-sale and sale prices on your landing pages, and only the sale price at checkout."
  3. Write the effective date with a timezone offset. Use the same offset your store uses for the sale schedule.
  4. Check what your feed tool sends. Open the generated feed file or the product in Merchant Center and confirm that sale_price_effective_date exists and carries an offset. Some feed plugins drop the time or the offset.
  5. Check the page HTML. Load a product URL with JavaScript disabled, or view the raw source, and confirm the price is there. If the price only appears after a script runs (a currency switcher or a pricing app, for example), Google treats that as a mismatch.
  6. Check structured data. Run the product URL through the Rich Results Test and compare the price and priceCurrency in the Offer with your feed. If the page shows a sale price, the structured data should show the same figure.
  7. Check currency and tax display. Google's help page says the price and currency must match the one prominently displayed on the page and suit the country you target.
  8. Review automations. Go to Products > Automations in Merchant Center. Google says automations are on by default. If your pages show more than one strikethrough price (for example "was", "RRP" and "now"), Google advises against enabling automatic price updates.
  9. Plan feed refreshes. If your feed is fetched once a day, add a fetch just after the sale starts and another just after it ends, or push updates through the Merchant API.
  10. Book two checks in the calendar: one on the first morning of the sale and one on the morning after it ends. Open Products > Needs attention and filter by price issues.

Where mismatches come from: owner and check

Risk Typical owner Check Frequency in sale week
Sale starts at a different time on site and in Google Ecommerce manager Compare the sale schedule with sale_price_effective_date, including the offset Once when the sale is set up, again the day before
Price added by JavaScript after load Developer or agency View raw HTML source for five top products Once, after any theme or app change
Structured data shows the old price Developer or agency Rich Results Test on sale products First morning of the sale
Feed fetched once a day Feed owner Confirm fetch schedule in Merchant Center or feed tool Before the sale; add fetches on start and end days
Multi-currency or tax-inclusive display differs from feed Ecommerce manager Load page from the target country settings and compare Once per target country
Strikethrough price differs from price Merchandiser Compare "was" price on page with feed price Once when the sale is loaded
Sale ends on site but sale_price persists Feed owner Check Merchant Center the morning after the end date Once

Copyable artefact: sale price test plan

Copy this into your ticket system and fill in the blanks.

SALE PRICE TEST PLAN: Black Friday / Cyber Monday 2026 (illustrative values)

Store timezone offset:        ______ (e.g. -0500)
Sale start on website:        2026-11-27 00:00 local
Sale end on website:          2026-11-30 23:59 local
Feed value to send:           2026-11-27T00:00-0500/2026-11-30T23:59-0500

Before the sale (by 20 Nov)
[ ] Feed sends price = full price, sale_price = sale price, both with currency
[ ] Feed sends sale_price_effective_date with timezone offset
[ ] Raw HTML of 5 top products contains the price without JavaScript
[ ] Rich Results Test: Offer price and priceCurrency match the feed
[ ] Strikethrough ("was") price on page equals feed price
[ ] Merchant Center > Products > Automations: price setting reviewed
[ ] Extra feed fetches booked for start day and day after end

Sale start (27 Nov, morning)
[ ] 10 top products: page price = Merchant Center sale price
[ ] Needs attention: no new price issues (note count: ____)

Sale end (1 Dec, morning)
[ ] Page shows full price again
[ ] Merchant Center no longer shows sale price
[ ] Needs attention: no new price issues (note count: ____)

If issues appear
[ ] Fix the source (feed or page), not Merchant Center alone
[ ] Re-fetch feed, then request a website check (up to 12 h review)
[ ] Record the cause in the incident log

Worked scenario (illustrative)

A store in a UTC-5 timezone sells winter boots through WooCommerce and Google Shopping. The merchandiser schedules a 25% sale on 120 products from 27 November at 00:00 local time. The feed plugin sends sale_price_effective_date as 2026-11-27/2026-11-30, with no time and no offset.

Google reads that as midnight UTC on 27 November, which is 19:00 on 26 November in the store's timezone. For five hours, Merchant Center expects the sale price while the product pages still show the full price. Googlebot crawls a dozen product pages in that window and flags them. On the morning of Black Friday, the team finds those products disapproved in Needs attention while the pages look correct.

The team changes the plugin setting to include time and offset, re-fetches the feed and requests a website check. The products return later that day, after most of the busiest morning of the year. Checking one product's feed entry before the sale would have shown the missing offset.

The same store would have the mirror problem at the end of the sale. Because Google defaults the end to 23:59 UTC on 30 November, the feed would drop the sale price five hours before the site did.

Common mistakes

  • Overwriting price with the sale price and removing it after. Google then has no full price to compare, the strikethrough annotation cannot show, and you change the core price twice in one week.
  • Fixing the price in Merchant Center by hand while the feed still sends the old value. The next fetch puts the error back. Fix the source.
  • Trusting automations to cover a sale. Google states automations "aren't a replacement for regular updates of your product data", and they may stop if the number of mismatches gets too large.
  • Testing only while logged in. Logged-in prices, member prices and cart rules can differ from what Googlebot sees. Member-only prices belong in loyalty_program, which has its own mismatch issue.
  • Showing a price range or "from" price on variable products while the feed sends one variant price. Make sure each feed item links to a URL that preselects that variant.

Limitations

This plan reduces the chance of a mismatch. It cannot remove it, because Google decides when to crawl and when to re-review. Google does not publish a crawl schedule, and the help pages give only "a few hours or days" for re-crawls. Platform behaviour also varies: your feed app, theme and caching layer each affect what Googlebot receives, so test the actual pages rather than relying on settings screens. This article does not cover regional pricing, local inventory feeds or bulk pricing, which have their own Google help pages.

FAQ

How long does it take Google to clear a price mismatch?

Google says Googlebot re-crawls disapproved products "over the next few hours or days". You can request a website check after fixing the source, and Google says that review can take up to 12 hours, during which you cannot send another request.

Should I turn off automatic item updates for Black Friday?

Usually you can leave them on, since they can correct some prices. Google does advise against automatic price updates when your pages show more than one strikethrough price, and warns they may not work for prices that change more than once a day. Review the setting against how your sale pages look.

Can I send a sale price without an end date?

You can, but Google applies a sale price with no effective date immediately and keeps it until you remove it. For a fixed sale, send both start and end with a timezone offset so the feed changes back on its own.

Sources

  • Google Merchant Center Help, How to fix: Mismatched product price: https://support.google.com/merchants/answer/12159029
  • Google Merchant Center Help, Sale price effective date [sale_price_effective_date]: https://support.google.com/merchants/answer/6324460
  • Google Merchant Center Help, Sale price [sale_price]: https://support.google.com/merchants/answer/6324471
  • Google Merchant Center Help, Allow Merchant Center to update product information automatically: https://support.google.com/merchants/answer/12157888
  • Google Merchant Center Help, How to fix: Automatic updates: Mismatched price: https://support.google.com/merchants/answer/14916353
  • Google Merchant Center Help, How to fix: Mismatched strikethrough price (page crawl): https://support.google.com/merchants/answer/15621352

Last reviewed: 2026-11-07

For related checks, see Merchant Center Availability Mismatch, Product Feed Monitoring and Promotion and Discount Validation.

A price mismatch shows up in Merchant Center, but a broken sale can also show up first as a change in orders. Pingvera's WooCommerce connector compares order flow with an hourly baseline and alerts you when the site is up but orders drop, and its unified timeline puts that drop next to the deploy or change that preceded it. That covers the order side of step 10. The Merchant Center check stays with you.

Know about problems before your customers do

Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.

Start free

Read next: Merchant Center Availability Mismatch: Black Friday Fix · Merchant Center Promotions: Black Friday Setup and Checks · Merchant Center Misrepresentation: Fix It Before Peak · How to Update WooCommerce Safely Before Black Friday · Run a free site check.

Read next: Merchant Center Availability Mismatch: Black Friday Fix · Merchant Center Promotions: Black Friday Setup and Checks · Merchant Center Misrepresentation: Fix It Before Peak · WooCommerce 11.3: What to Test Before Black Friday · Run a free site check.

← All articles · Privacy policy · pingvera.com