Site down on Black Friday: your emergency plan, minute by minute

What to prepare beforehand, what to do in the first 30 minutes, what to tell customers, what to do with your ads and what to check once the site is back.

Vasile Dingă2026-11-16T11:50:08.268682+00:00
Site down on Black Friday: your emergency plan, minute by minute

Black Friday falls on Friday, 27 November 2026 this year. For many stores it's the day with the most traffic of the year and, for the same reason, the day when a slow or crashed site costs the most. You can't guarantee it won't happen, but you can decide in advance what you'll do in the first 30 minutes, whom you'll call and what you'll tell customers. When the problem hits, there's no time to think about the order of things: you just follow it. Below I show what I prepare beforehand, what the first half hour looks like, how to communicate, what to do with your ads and what to check afterwards. At the end there's a generator that builds your minute by minute plan and ready-to-copy messages.

1. Preparation: find the limits before your customers do

Many peak-day outages have ordinary causes: the hosting plan has a resource limit you never notice on normal days, a plugin installed the day before slows down the cart, or an email sent to the whole list brings thousands of people in the same minute.

  • Know your plan's limits. On shared hosting, ask how many resources you have (CPU, memory, concurrent processes) and what happens when you exceed them. On a hosted platform such as Shopify the servers are the platform's job, but the theme, apps and scripts you add are still yours.
  • Run a load test with your host's agreement, on a copy of the site or at a quiet hour. A test started without warning can look like an attack.
  • Turn on caching for pages and images and remove scripts you no longer use. I explained what slows a store down in the article on site speed and conversions.
  • Freeze changes. A week before, I stop installing new plugins, changing the theme or running major updates until after Cyber Monday.
  • Take a full backup before the peak and make sure you know how to restore it.

2. Monitoring, contacts and who decides

You don't want to find out from a customer's comment that your site is down. An uptime monitoring service checks the site every few minutes and alerts you by text or phone call. Have it check the cart as well, not just the homepage. Then prepare an emergency list, kept outside the site and the server:

What you need Hosting or platform support, with their opening hours Why First call when the server doesn't respond What you need Your developer or agency, with a phone number Why Rolling back to the last working version What you need Your payment provider's contact Why Declined payments or payments without an order What you need Access to your domain and DNS Why When the problem is the domain, not the server What you need Ads and email apps on your phone, with access checked Why Pausing campaigns when you're away from your desk

Decide in advance who makes the calls. In a small team, one person handles the technical side, another handles communication and ads, and a third, if you have one, handles support. If you're on your own, ask someone you trust to answer messages that day.

3. A plan B for payments

Sometimes the site works but payment doesn't. A bank transfer option or a second payment provider, set up and tested in advance, is the usual backup; in some markets cash on delivery plays that role. The backup method must already be configured and ready to switch on from a setting, not installed in the middle of the crisis. Also prepare the text for customers who paid and didn't get a confirmation: don't pay again, you'll contact them.

4. The first 30 minutes

Order matters more than speed:

  • Minute 0 to 5: confirm the problem from another phone on mobile data and write down the time and the error. Check the platform's or host's status page.
  • Minute 5 to 15: call or message support; if you changed something today, undo it. Pause your ads and any scheduled email and SMS sends.
  • Minute 15 to 30: publish the first message for customers and, if the site is completely down, a maintenance page.

The maintenance page should return HTTP status 503, not 200 and not a redirect to the homepage. In its Search documentation, Google recommends a 503 for temporary unavailability, with a Retry-After header for the estimated return time and a simple, static error page. The same page says a full site shutdown should last only a very short time, at most two or three days, and that robots.txt must not return a 503, because that blocks all crawling. If only payment is broken, it's better to keep the site visible and disable the cart: Google says this doesn't affect your presence in Search.

5. What to tell customers

  • Fast and short: what isn't working, what you're doing and when you'll post an update. Don't promise a recovery time you don't know.
  • Say clearly that orders already placed are safe, if that's true.
  • Update the message every 30 minutes, even if nothing has changed. Silence brings more support messages than the problem itself.
  • The same text everywhere: banner, social media and support replies.

If you decide to extend the offer, extend it for real in your discount settings and say exactly until when. I wrote about organising support on these days in the article on customer support in peak season.

6. Ads and scheduled sends

Ads keep spending even when the site doesn't respond. Pause campaigns at campaign level in Google Ads and Meta, from the phone apps if you're not at your computer. Just as important are the emails and texts scheduled for Black Friday: if a send goes out during the outage, you push thousands of people to an error page and waste the best message of your year.

In Google Ads, if the site returns errors when Google checks it, ads can be disapproved for a destination not working. Under Google's policy, once you've fixed the site you need to file an appeal to have the ads reviewed again. In Merchant Center, products with an unavailable page are disabled until Google can access the page again; you can request a website review, which can take up to 12 hours. That's why, after recovery, the first thing I check in the accounts is the status of ads and products.

7. Once the site is back

  • Test the whole purchase path on mobile and desktop: product, cart, payment, confirmation email.
  • Restart the same campaigns, don't build new ones in a hurry, and watch load times for the first hour.
  • Look for problem orders: payments taken without an order in the store, duplicate orders, stock out of sync.
  • Send a short recovery email saying what happened and, if you extended the offer, until when it runs. I explained how to reach the inbox in the article on Black Friday emails that don't land in spam.
  • Annotate the outage window in your reports and ad account history, so you don't compare the day with last year without context.

The next day, write one page on what happened, how long it lasted, what it cost and what you'll change. Often the answer is a bigger hosting plan just for November and December, or a plugin removed from the site.

How I work

Before Black Friday, my clients and I put together a one-page emergency list: contacts, account access, who decides and the prepared texts. I check in advance which pages the campaigns point to and whether they can be paused from a phone. On peak day, I handle the ads and the messages, while the developer or host handles the technical side.

Generate your emergency plan

Choose your platform, the problem, your team and channels; you get the steps by minute and messages ready to copy.

Frequently asked questions

Conclusion

A site that goes down on Black Friday isn't just a technical problem, it's also a communication problem and money spent on ads. Know your limits in advance, keep the emergency list at hand, pause ads and scheduled sends within the first 15 minutes, tell customers what's going on and check everything once you're back. If you want a fast store that's ready for peak traffic, see the frontend development page or write to me via contact.