Google Merchant Center sale price claims: a checklist
A “was £89, now £39” line looks harmless on a product card. It is not decoration. It is a claim that the higher number was a real price, and that the lower one is what a shopper pays.
Terms in this guide, explained: sale_price, Structured data (Product / Offer), Misrepresentation.
On this page
Google Shopping is blunt about this. The price in your product data has to match the landing page, the structured data and checkout. If you also show a struck-through or compare-at price, that number is matched against the price attribute once sale_price is present. When those figures disagree, Google’s strikethrough-price help says the original price is discarded and will not show as a strikethrough. That is a hassle you can avoid.
This page is a checklist. Work through the surfaces in order. For the mismatch diagnosis, the compare-at audit, and what counts as a genuine “was” price, use the live guides linked above. For how to mark the price up, use Product structured data for Merchant Center: GTIN, brand, and price consistency.
Stock, scarcity and preorder wording are a different mess. Use the companion checklist, Google Merchant Center stock and scarcity claims.
What this checklist covers
- The current price on the page, in the product data, in structured data and at checkout.
- The struck-through, compare-at or “was” price, and the
sale_priceattribute. - Sale badges, coupons and prices that only appear after a code.
- Sale claims you cannot verify, including a “was” price you never actually charged.
- Currency and variant prices, where they turn a sale into a mismatch.
It does not replace your shipping policy or returns policy. Delivery rates and restocking fees live there, not inside a product-price badge. Keep the business details on the contact and business details checklist consistent as well. A clean sale price on a page that still hides who you are is not a finished storefront.
How Google treats a sale price
In the product data, price is the required current price when the item is not on sale. When you lower it for a sale, Google’s sale price attribute help says to submit the reduced amount in sale_price and to keep submitting the full, non-sale amount in price. If the item is on sale and you do not submit sale_price, submit the amount the shopper actually pays as price. The sale amount has to be lower than price, and that difference has to appear in the product data.
The same help article says the sale price you submit must match the sale price on the landing page and at checkout. Show both the non-sale and sale prices on the landing page, and only the sale price at checkout. If you advertise a coupon code, it has to be usable by everyone who lands there. Show the non-sale price and the sale price after the code, and keep that sale amount the same through checkout.
Google’s sale-price annotations article adds a display rule for the landing page: the active sale price should be the most prominent price, and the original can be struck through, greyed out, or otherwise shown as not currently active. The sale_price attribute article notes a narrower exception: the sale price does not have to be the most prominent, and the original may still be in a larger font. Do not treat a huge “was” number and a tiny current price as a clever trick. If a reviewer or a crawler can be confused about what the shopper pays, you have a problem.
To time a sale, use sale_price_effective_date as a start and end in the ISO 8601 form Google documents. If you omit it, the sale price attribute help says the sale price is used immediately.
Checkout is its own test. Google’s checkout requirements say the price must not increase at checkout. It can fall after the item is in the cart if a promotion is applied. With the exception of government-mandated fees, adding extra products or services at checkout that raise the total is not allowed. The price attribute help also says not to use “View price in cart,” and not to change the landing-page price based on a user’s location. IP detection, it says, is against the guidelines and may interfere with the crawler.
Strikethrough and compare-at prices are claims
Themes love a compare-at field. A red “was” price next to the current one is easy to paste in. Google does not treat it as a style choice.
The mismatched strikethrough-price article says the other prices on the landing page — regular, suggested retail, and strikethrough — are matched against price when sale_price is also provided. Common reasons it lists for a mismatch:
- The strikethrough on the site does not match
pricewhilesale_priceis present. - The page shows a strikethrough, but
sale_pricewas never submitted. - The strikethrough is added with JavaScript after the page has loaded.
- There is a delay between a website update and the product data in Merchant Center.
If you show a compare-at or “was” price, put the same number in price and the amount the shopper pays in sale_price. If you cannot stand behind the higher number as a price you actually charged, take the strikethrough off the page. Do not invent a reference price “because the theme asked for one.” That is the unverifiable claim this checklist is for.
Google’s sale-price annotations are a separate overlay: a strikethrough and a sale badge on Shopping ads, free listings and the Shopping tab, when the sale and the base price meet published conditions. Those conditions include a sale lower than the base price, a discount greater than 5% and less than 90%, and both prices on the landing page. Some countries and surfaces also require the base price to have been valid or charged for a stated number of days in a stated window. The official groups, from the annotations article fetched on 2026-11-14, are:
- Free listings in Australia, Canada, the United States and Japan: the 5%–90% discount band and both prices on the page. No extra day-count is listed for that group.
- Free listings in Brazil, France, Germany, India, Italy, Korea, the Netherlands, Spain and the United Kingdom: the same discount band, plus a base price valid for 30 days within the past 200 days (not necessarily consecutive).
- Shopping ads in the United States: the same discount band, and the base price charged for either 5 days within the past 30 days or 15 days within the past 200 days, whichever condition is met first (days need not be consecutive).
- Shopping ads in Australia, Brazil, Canada, France, Germany, India, Italy, Japan, Korea, the Netherlands, Spain and the UK: the same discount band, plus a base price valid for 30 days within the past 200 days (not necessarily consecutive).
- Local inventory ads have a stricter store-level day rule in the same article (60 days within the past 200, or 60 consecutive days if the product has been active for less than 200 days).
The annotations article also says that, for a sale to be recognised as a temporary reduction, the base price should ideally be the sole active price at times, and the sale_price duration should not exceed 30 days. That is Google’s wording for the annotation, not a promise that a badge will appear. The same article says sale price annotations still may not show, even when you meet the requirements, because Google wants the best-performing annotations to surface.
Do not treat those day counts as a sales target, and do not invent a figure for a country that is not in the list. For the longer walkthrough of what Google counts as a genuine “was” price, use Discounts and “was” prices: what Google counts as genuine. For how to audit a compare-at field, use Compare-at prices on Google Shopping: how to audit them.
Unverifiable and dishonest sale claims
Google’s Misrepresentation policy does not allow offers that represent you or your products in a way that is not accurate, realistic and truthful. It also does not allow pricing practices that create a false or misleading impression of the cost, including bait-and-switch: advertising an enticing, often unrealistic, low price with no genuine intent to sell that item. “Unavailable offers” in the same policy include promising promotional offers that are not available, and listing items as available when you cannot fulfil the orders. For “unavailable offers,” Google says a warning is issued at least 7 days before any account suspension. That is a warning rule. It is not a result you can count on, and it is not a reason to leave a fake sale up.
If you cannot show, from your own price history, that the “was” or compare-at amount was a real selling price, do not put it on the page and do not put it in price. Suggested retail, a competitor’s list price, or a number the theme generated overnight is not a base price you can stand behind. If a sale has ended, take the badge and the strikethrough down, and stop submitting sale_price. Promoting a deal that is no longer active is the kind of unavailable offer the policy calls out.
Sale price checklist
Work through this on one product, then on a variant that has its own price. Stay signed out. Use the same country and currency you submit in Merchant Center.
Questions merchants ask
Can I show a compare-at price I never charged, if I also submit sale_price?
No. The higher number is a claim. Google matches that strikethrough against price. If you did not charge it, do not show it and do not submit it.
Why did a strikethrough disappear from Shopping even though the page looks right?
A mismatch between the page and price / sale_price is enough for Google to discard the original price. Even when the figures match and the published discount band and day-count rules are met, Google still says sale price annotations may not show.
If I only lower price and skip sale_price, is that cleaner?
If the item is on sale and you do not submit sale_price, Google’s attribute help says to submit the sale amount as price. You then have no official original price in the product data, so a strikethrough on the page has nothing honest to match. Pick one story and tell it on every surface.
Does a consistent sale price mean a misrepresentation review will go in my favour?
No. This checklist helps you publish prices you can stand behind and line them up with Merchant Center. It does not file a review, and it does not claim any outcome.
Sources
Fetched and verified HTTP 200 on 2026-11-14:
- Sale price [sale_price] — submit
sale_pricewithprice; sale amount must be lower; match landing page and checkout; both prices on the page, only the sale price at checkout; coupon codes must be usable; ifsale_priceis omitted during a sale, submit the sale amount asprice. - Sale price effective date [sale_price_effective_date] — start and end in ISO 8601; without it, the sale price is used immediately.
- Price [price] — match landing page and checkout; do not use “View price in cart”; do not change the landing-page price by IP detection.
- About sale price annotations — landing-page prominence; 5%–90% discount band; country-specific base-price day counts for annotations; annotations may still not show.
- How to fix: Mismatched strikethrough price (page crawl) — strikethrough / regular / suggested retail matched against
pricewhensale_priceis present; common mismatch reasons. - About landing page requirements — price, currency and availability on the landing page must match the product data.
- Checkout requirements and best practices — price must not increase at checkout; it can fall with a promotion.
- Misrepresentation — accurate, realistic and truthful offers; dishonest pricing, including bait-and-switch; promotional offers that are not available.
- Product data specification — price must match the landing page, structured data and checkout.
- Merchant listing structured data — Offer price markup on the product page.
Check the live storefront
A sale can look tidy on the product card and still disagree with the feed, the markup, or the cart. That mismatch is the headache. Paste your store URL into the free StoreVerifier scan. You get the published price and sale sentences that actually conflict.
Similar cases
That is one issue. The library documents 140.
The free scan shows the verdict, the counts and up to 3 findings in full. The paid report opens every finding, with the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.