GEO & AI search visibility
How-to

Running a Black Friday sale? How to get your deal prices right in ChatGPT and Google's AI shopping

Short answer

Put the sale price in the page's HTML, mark it up as the active price with the regular price as a StrikethroughPrice, give it a start and end date, and update any product feeds at the same moment. Run the sale from one permanent deal page, such as /sale/black-friday, publish it early, and switch everything back as soon as the sale ends. AI shopping tools can only quote the price they can read, and they may lag behind your changes.

Cover: Make the deal readable. Business and e-commerce how-to on getting Black Friday sale prices right in ChatGPT, Google AI Mode and other AI shopping tools.
On this page

    Key facts

    • Price is one of the ways ChatGPT ranks stores: OpenAI says merchants "are ranked based on factors like availability, price, quality, and whether they are the maker or primary seller", and the cheapest option it knows about may get a "Best price" label.
    • ChatGPT can lag behind your changes: OpenAI says that "when merchants update their pricing or shipping terms, there may be some delay before it is reflected".
    • Google's Shopping Graph moves fast: Google says the Shopping Graph behind AI Mode shopping has more than 50 billion product listings, 2 billion of which are updated every hour.
    • Google has markup for sales: the active price goes in price, the regular price goes in a price specification marked https://schema.org/StrikethroughPrice, and the sale period goes in validFrom and validThrough or priceValidUntil.
    • One URL, every year: Google recommends a recurring URL for Black Friday pages, for example /sale/black-friday, not /sale/2020/black-friday.
    • The EU 30-day rule: in the EU, any announced price reduction must show the "prior price", the lowest price you charged in at least the 30 days before the reduction.
    • The dates: Black Friday 2026 is Friday 27 November, and Cyber Monday is 30 November.

    Why sale prices trip up AI shopping

    People ask AI assistants things like "best winter boots under €100" or "is there a Black Friday deal on this coffee grinder?". Price is part of the question, so it's part of how the answer gets built.

    OpenAI's help page on shopping in ChatGPT says product results use "structured metadata from first-party and third-party providers (e.g., price, product description)". When a shopper gives a budget, "ChatGPT will focus more on price". When several stores sell the same product, price is one of the factors used to rank them.

    That creates two ways to lose a sale:

    1. The assistant has your old price. Your deal is real, but the answer still quotes the full price, or leaves you out of an "under €100" list.
    2. The assistant has your sale price after the sale ended. The shopper clicks through, sees a higher price and leaves, and you look like the store that got it wrong.

    Both happen when your page, your markup and your feeds say different things, or when the price only appears in a way some systems can't read. Google's guidance for AI Overviews and AI Mode includes making sure your structured data matches the visible text on the page and that your Merchant Center information is up to date.

    Where your sale price needs to appear

    Place What to set Who reads it
    Product page (visible text) Sale price and regular price, both shown clearly in the HTML Shoppers, search crawlers, AI crawlers
    Product structured data price = sale price, regular price as StrikethroughPrice, plus start and end dates Google Search, including AI features
    Google Merchant Center feed price = regular price, sale_price = sale price, sale_price_effective_date with time zone Google Shopping and AI Mode
    ChatGPT product feed (if you have one) price = regular price, sale_price = sale price, updated when the sale starts and ends Shopping in ChatGPT
    Checkout The same sale price, with no surprises Shoppers, and Google's checks
    Deal landing page Event name, dates, what's on sale, terms, links to the products Shoppers, crawlers, AI answers about your sale

    Notice the switch between rows two and three. In structured data, price is the price people pay today. In both feeds, price stays the regular price and the discount goes in sale_price. Mixing these up is an easy way to send conflicting signals.

    Step 1: Set up one permanent deal page now

    Google published best practices for Black Friday and Cyber Monday pages that still hold up:

    • Create the page early, well before the sale, so it has time to be found and indexed. Make sure it isn't blocked from crawling.
    • Link to it from your home page, so shoppers and crawlers find it quickly.
    • Use a recurring URL, one that reflects the event and is reused each year: /sale/black-friday, not /sale/2026/black-friday.
    • Ask Google to recrawl it once the content is updated.

    A year later, Google added more advice for deal pages: put the event in the page title (such as "Black Friday 2026 Deals"), describe the event in the page text, and if you only reveal the deals on the day, publish general information in advance and ask for a recrawl once the details go live. Any text in a banner image should also appear in the page text and the alt text.

    For AI answers, that page text does the heavy lifting. An assistant asked "does this store have a Black Friday sale?" can only answer from what it can read. Write down, in plain text:

    • the start and end dates and times, with the time zone
    • which categories or products are included
    • the discount range, for example "up to 30% off selected jackets"
    • the terms: coupon codes, minimum order, who qualifies, shipping during the sale

    After the sale, don't delete the page or redirect it to your home page. Replace the offers with a short note that the sale has ended, link to your current offers, and reuse the same URL next year.

    Step 2: Mark up the sale price the way Google reads it

    Google's merchant listing structured data documentation explains how to show a sale. The current price becomes a sale price "when you provide a second price with the original, strikethrough price" marked with priceType https://schema.org/StrikethroughPrice. You don't mark the active price with a priceType.

    Here's a product on sale for Black Friday, with the sale dates on the Offer:

    {
      "@context": "https://schema.org/",
      "@type": "Product",
      "name": "Merino wool scarf",
      "offers": {
        "@type": "Offer",
        "url": "https://www.example.com/merino-wool-scarf",
        "price": 39.00,
        "priceCurrency": "EUR",
        "validFrom": "2026-11-27T00:00:00+00:00",
        "priceValidUntil": "2026-11-30T23:59:59+00:00",
        "availability": "https://schema.org/InStock",
        "priceSpecification": {
          "@type": "UnitPriceSpecification",
          "priceType": "https://schema.org/StrikethroughPrice",
          "price": 49.00,
          "priceCurrency": "EUR"
        }
      }
    }
    

    A few rules from the same page:

    • Give both a start and an end, in ISO 8601 format, and include the time and time zone.
    • Watch the end date. Google says your listing "may not display if the priceValidUntil property indicates a past date". When the sale ends, update or remove it along with the price.
    • Put the markup in the initial HTML. Google warns that markup generated with JavaScript "can make Shopping crawls less frequent and less reliable", which matters for "fast-changing content like product availability and price".

    The JavaScript point goes beyond Google. Vercel's study of AI crawler traffic found that none of the major AI crawlers it analysed, including OpenAI's and Anthropic's, render JavaScript. If your theme loads the sale price with a script after the page opens, those crawlers may only see the old price, or no price at all.

    Step 3: Update your feeds on the same schedule

    If you send product feeds, they need the same prices at the same time. Google and OpenAI handle sale dates differently, and the difference matters on the night the sale starts.

    Google Merchant Center ChatGPT product feed
    Regular price price price
    Sale price sale_price sale_price, which must be lower than price and in the same currency
    Sale dates sale_price_effective_date, a start and end with time zone Dates don't schedule anything
    What you have to do Set the dates and Google applies the sale price for that window Update the feed when the sale starts and again when it ends

    Google's sale price help page asks you to show both the regular and sale prices clearly on the landing page, show only the sale price at checkout, and submit a sale price that matches both. If a deal needs a coupon code, Google says the code must be accessible to all users. Its sale price effective date page adds that if you leave out the time zone, Google defaults to UTC, and if you leave out the time, the sale runs from midnight on the start date to 11:59 PM on the end date.

    OpenAI's products feed reference is stricter about timing. It says to "update the feed when a sale starts or ends", and that sale-window dates "do not schedule price or availability changes". In other words, a ChatGPT feed shows whatever price you last sent. Shopping in ChatGPT is currently live for users in the US, and merchants can apply to share a feed on OpenAI's merchants page.

    Step 4: Check the EU 30-day rule before you write "-40%"

    If you sell in the EU, the price you show crossed out isn't just a marketing choice. Article 6a of the EU's Price Indication Directive says any announcement of a price reduction must show the "prior price", which is the lowest price you charged in a period of at least 30 days before the reduction. The European Commission's page on the directive links to its official guidance.

    So if you raised a product's price in early November, that higher price can't be your Black Friday reference price. Work out a reference price you can defend, then use that same number in the page, the StrikethroughPrice markup and the feeds. Rules can differ in detail between countries, so check with your national consumer authority or a lawyer if you're unsure.

    Step 5: The day after, switch everything back

    Most sale-price errors in AI answers happen after the sale, not during it. Plan the end before you start:

    1. Revert the price everywhere at the same time: page, markup and feeds. Google Merchant Center handles this for you if you set sale_price_effective_date. A ChatGPT feed doesn't, so schedule that update.
    2. Remove or update priceValidUntil so it never points to a past date.
    3. Update the deal page text to say the sale has ended.
    4. Tell search engines the pages changed. Update lastmod in your sitemap and use IndexNow if your platform supports it. Our guide to sitemap lastmod and IndexNow covers both. In Google Search Console you can ask Google to recrawl your key URLs, but there's a quota, so save it for the deal page and best sellers.
    5. Expect some lag. OpenAI says its price updates may take time to show, so check what ChatGPT says about your products a few days later, and use its feedback option if something is wrong.

    Common mistakes

    Mistake What happens Fix
    Sale price only appears after JavaScript runs Crawlers that don't render JavaScript see the old price or none Put the price and the markup in the initial HTML
    A new URL every year (/black-friday-2026) The page starts from zero and may not be indexed in time Reuse one URL, such as /sale/black-friday
    Sale price in the feed but not on the page Google can disapprove the product, and AI tools see conflicting prices Show the same price on the page, in the markup and at checkout
    The deal only works with a code sent to subscribers Google requires advertised coupon codes to be accessible to all users Publish the code on the page, or leave the deal out of your feeds
    priceValidUntil left in the past Google says the listing may not display Update it when the price changes
    A "was" price you didn't charge in the last 30 days Breaks the EU prior-price rule Use the lowest price from at least the previous 30 days
    Tighter bot protection for the traffic peak Search and AI crawlers get blocked when you need them most Check that crawlers you want can still reach your pages (how to check)

    Sale prices sit alongside the rest of your product data. Clear product descriptions, the right stock status and visible shipping and return policies matter just as much during a sale.

    What this won't do

    None of this guarantees that ChatGPT or Google will feature your deal. Neither company promises that. What it does is make sure that when an assistant does mention your store, it quotes the price you're actually charging, before, during and after the sale.

    Check your site

    Want to know whether AI tools can read your product pages before the rush? The free Web2Agents AI check scores your homepage out of 30, tests 12 AI bots against your robots.txt and checks your robots.txt, sitemap.xml and llms.txt, with results on screen. The €19 AI-Ready Kit runs all 36 checks on up to 25 pages, including product pages and their structured data, and ranks the fixes by impact.

    {"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Do I need a new Black Friday page every year?", "acceptedAnswer": {"@type": "Answer", "text": "No. Google recommends one recurring URL that reflects the event, such as /sale/black-friday, reused each year. Update the content, publish it early and link to it from your home page."}}, {"@type": "Question", "name": "Will ChatGPT show my Black Friday price?", "acceptedAnswer": {"@type": "Answer", "text": "Only if the price reaches it. OpenAI says ChatGPT gets product prices from third-party providers or directly from merchants, and that price changes may take some time to show. A clear price in your page's HTML and an up-to-date feed, if you have one, give it the best chance."}}, {"@type": "Question", "name": "Should the sale price go in price or sale_price?", "acceptedAnswer": {"@type": "Answer", "text": "It depends on where. In Product structured data, price is the price people pay now, and the regular price is added as a StrikethroughPrice. In Google Merchant Center and ChatGPT product feeds, price stays the regular price and the discount goes in sale_price."}}, {"@type": "Question", "name": "What time zone should I use for sale dates?", "acceptedAnswer": {"@type": "Answer", "text": "Always include one. Google recommends adding the time and time zone in ISO 8601 format, and Merchant Center defaults to UTC if you leave the time zone out, which can start or end your sale at the wrong local time."}}, {"@type": "Question", "name": "Can I show a \"was\" price if I raised the price last month?", "acceptedAnswer": {"@type": "Answer", "text": "Not as the reference for a reduction in the EU, if you charged less at any point in the 30 days before the sale. Article 6a of the Price Indication Directive says the prior price shown with a reduction must be the lowest price you charged in at least the 30 days before it."}}]}

    FAQ

    Do I need a new Black Friday page every year?

    No. Google recommends one recurring URL that reflects the event, such as /sale/black-friday, reused each year. Update the content, publish it early and link to it from your home page.

    Will ChatGPT show my Black Friday price?

    Only if the price reaches it. OpenAI says ChatGPT gets product prices from third-party providers or directly from merchants, and that price changes may take some time to show. A clear price in your page's HTML and an up-to-date feed, if you have one, give it the best chance.

    Should the sale price go in price or sale_price?

    It depends on where. In Product structured data, price is the price people pay now, and the regular price is added as a StrikethroughPrice. In Google Merchant Center and ChatGPT product feeds, price stays the regular price and the discount goes in sale_price.

    What time zone should I use for sale dates?

    Always include one. Google recommends adding the time and time zone in ISO 8601 format, and Merchant Center defaults to UTC if you leave the time zone out, which can start or end your sale at the wrong local time.

    Can I show a "was" price if I raised the price last month?

    Not as the reference for a reduction in the EU, if you charged less at any point in the 30 days before the sale. Article 6a of the Price Indication Directive says the prior price shown with a reduction must be the lowest price you charged in at least the 30 days before it.

    Sources

    Newsletter

    New guides on AI visibility, in your inbox.

    Practical, sourced articles on AI crawlers, llms.txt, structured data and AI search. A new one every day.

    Unsubscribe anytime. See our Privacy Policy.