Getting agent-ready before the holiday rush

Peak season is when a broken journey costs the most, and it's also when the riskiest changes go live: tighter bot rules, sale prices, promo pop-ups, then a code freeze that makes anything you missed hard to fix. Here's what to check before the freeze, so AI agents shopping for your customers can still find you, read your prices and buy.

Why peak season is different

Every change made for peak is reasonable on its own. Security tightens bot protection to stop scalpers and card testing. Marketing adds a countdown banner and an email pop-up. Merchandising loads sale prices through a promotions app. Operations shortens cache times, or lengthens them to cope with load. Then engineering freezes the code.

Each of those changes is made by a different team, often in a hurry, and none of them is tested with an AI agent in mind. An assistant asked to "find a gift under $50 that arrives before the 24th" needs to get past your bot rules, read the sale price, see that the item is in stock, close the pop-up and reach the cart. Any one of those can fail quietly, and you won't see it in your analytics.

A timeline for the weeks before the freeze

When	What to do	Who
Six or more weeks out	Run AgentScore on your home page and fix anything critical. Agree which journeys matter most at peak.	E-commerce lead, developers
Four weeks out	Review planned bot protection changes with your CDN or security team. Check sale price and stock data on a test promotion.	Security, merchandising
Two weeks out	Put promo pop-ups and banners live on staging or behind a flag, and check an agent can still reach the cart.	Marketing, developers
Before the freeze	Rescan, set up scheduled journey tests with alerts, and agree what counts as an exception to the freeze.	E-commerce lead

1. Bot protection tightened for peak

This is the change most likely to turn agents away. Common peak settings include stricter challenge thresholds, "under attack" modes that challenge every visitor, blocks on cloud and data center networks, and country blocks. Browser agents and assistants that fetch pages for people often run from cloud networks, so they get caught by rules written for scrapers.

• Ask for a list of every bot rule planned for peak, and who can change them during the freeze. CDN rules often sit outside the code freeze and change mid-season.
• Make sure the AI assistants you want are allowed by verified identity, not just by user agent. See how to tell if an AI crawler is real.
• Check cart and checkout separately from the home page. Many stores add extra protection there for peak.
• Prefer rate limits on the expensive actions, like payment attempts, over blanket challenges. See rate limits for AI agents and geo-blocking and AI agents.

AgentScore checks whether your bot protection treats AI assistants differently from a browser, and whether the cart and checkout show them a block or a CAPTCHA. Rescan after every bot rule change, not just once in October. For the settings themselves, see bot protection and CAPTCHAs and setting up your CDN for AI agents.

2. Sale prices that agents can read

Promotion tools often change the price in the browser with JavaScript after the page loads. A shopper sees the sale price. An agent that reads the HTML sees the full price, or no price at all, and may quote the wrong figure to its user or skip you.

Before peak, run a test promotion and check three places: the visible price in the page source (use View Source, not the inspector), the price in your product structured data, and the price in the cart. They should all agree. If a sale ends on a known date, say so:

"offers": {
  "@type": "Offer",
  "price": "39.00",
  "priceCurrency": "USD",
  "priceValidUntil": "2026-12-01",
  "availability": "https://schema.org/InStock"
}

Show the original and the sale price in text, such as "Was $59, now $39", rather than relying on a strikethrough alone. See prices AI agents can read.

3. Stock that stays accurate

At peak, stock changes by the hour. If your structured data says InStock after an item sells out, an assistant will send people to a product they can't buy. If it says OutOfStock for an item you restocked this morning, you lose the recommendation.

• Make sure availability in your product data comes from the same source as the "Add to cart" button, not a nightly export.
• Use PreOrder or BackOrder where they apply, and state delivery estimates in text.
• If you lengthen CDN cache times for load, check how stale product pages can get, and purge on stock changes for best sellers.

4. Promo pop-ups and banners

Email capture, spin-to-win wheels, countdown banners and free-shipping bars all multiply in November. An agent can only get past one if it has a real, labelled close button and doesn't cover the content behind it. A pop-up that sits over the "Add to cart" button means the agent's click lands on the pop-up instead.

AgentScore checks that pop-ups and banners can be dismissed, and whether the add-to-cart button on a product page is covered by something else. Check again once peak promotions are live, because they're usually added after the last scan. See cookie banners and pop-ups.

5. Promo codes, carts and checkout

Gift shopping by agent depends on the last few steps working. Make sure the promo code field is labelled, that a rejected code produces a clear error in text, and that the cart total updates in the page. See carts AI agents can manage and error messages AI agents can understand.

Resist adding a CAPTCHA to checkout for peak. It stops agents at the very last step, after they've done all the work. Card testing is better handled by your payment provider's fraud tools and by rate limits on payment attempts. Keep guest checkout on. See checkout for AI shopping agents and guest checkout.

6. Holiday policies in plain text

Assistants are often asked about delivery cut-off dates and extended returns. Put them on your shipping and returns pages as text in the HTML, with dates, not only in a banner image or a pop-up. See policy pages AI assistants can read.

Planning for the freeze itself

A code freeze protects you from risky changes, but it also means a problem found in December may wait until January. Three things help:

1. Agree that blocking AI agents counts as an incident. If an assistant can't reach your product pages or checkout, that should qualify for a freeze exception, the same as a broken payment form.
2. Test the money journeys on a schedule. Ghost Agents run real journeys, such as search, choose a size and add to cart, stop at the payment form, and alert you when a journey that used to pass starts failing, with a step-by-step replay.
3. Watch your logs, not just analytics. Most agents don't run your analytics tag. A rise in blocked or failed agent requests shows up in server and CDN logs first. See finding the errors AI agents hit.

Start with a fresh AgentScore scan, then work through the list. If you have more time, our 90-day agent readiness plan covers the rest.