Black Friday Website Readiness Checklist: 8 Weeks to Launch Day

Sales peaks do not create new problems so much as expose old ones. The expired certificate nobody renewed, the checkout plugin that is slow under load, the alert that goes to a mailbox nobody reads: they all wait for the busiest day of the year. This checklist is organized by time before the event so that you can work through it in order. It applies whether you run Shopify, WooCommerce or a custom stack, and where a step is platform-specific it says so.

8 to 6 weeks before: baseline and inventory

• Measure normal. Record last year's peak: orders per hour, sessions per hour, the slowest hour and any errors. If there is no history, use a normal week and apply a multiplier you can defend, such as the traffic your campaigns are expected to drive. Do not invent a figure; ask your ad team or look at the last sale.
• Estimate the cost of downtime for a peak hour with the method in ecommerce downtime cost. This number justifies every other decision on the list.
• List every dependency: hosting, CDN, DNS provider, payment gateways, tax and shipping rate APIs, email provider, search or recommendation apps, fraud tools, ERP or inventory sync. Any of them can be the outage. Note who to contact at each and where their status page is.
• Check expiries. Domain registration, SSL certificates, API keys, app subscriptions and payment-provider account reviews. Use a domain expiry watch and the SSL Checker. Renew early, and if you can automate it, do; renew SSL and automate it explains how.
• Review plan limits: API call caps, hosting resource limits, email sending limits, app order quotas. Hitting a plan ceiling at peak is a common surprise.

6 to 4 weeks before: performance and capacity

• Fix page weight and speed on the home, collection, product, cart and checkout pages. Shopify store speed optimization और WordPress slow site checklist cover the main platforms. Test with the वेबसाइट स्पीड टेस्ट.
• Put a CDN and page caching in place for static assets and cacheable pages. Know exactly which pages must never be cached (cart, checkout, account) and test that rule. CDN explained और Cloudflare cache rules and purge cover this.
• Load test a staging copy with a tool of your choice, simulating the browse-to-checkout path rather than hammering the home page. Raise load in steps until response time degrades, then note the level and what broke first: database connections, PHP workers, a third-party API. Do not load test production without telling your host, and never load test a payment provider's live endpoints.
• Scale deliberately. If you self-host, decide on extra capacity or a larger plan now, not at 9 am on the day. Managed platforms may handle scaling for you, but confirm the limits of your plan and of your apps.
• Database and queue health: check slow queries, table sizes and background job backlogs. Clear old sessions and carts. Make sure scheduled jobs actually run; use a heartbeat monitor for each critical one.
• Reduce third-party scripts that you do not need during the sale. Every extra widget is another thing that can slow or break a page.

4 to 2 weeks before: reliability, DNS and security

• DNS: confirm your provider's reliability, keep a note of all records, and lower TTLs a few days before any planned change so rollback is fast. Do not change nameservers close to the event. See TTL explained and check records with the DNS चेकर.
• HTTPS: no mixed content, valid chain, redirects from HTTP and from the non-primary hostname are single-hop. See mixed content: how to fix.
• Security review: update the platform, themes and plugins early enough to test them; remove unused admin accounts; require two-factor authentication for staff. E-commerce site security checklist lists the details. Sales draw attention from fraudsters and bots as well as shoppers.
• Bot and abuse controls: rate limiting on login, search and checkout, and a plan for card-testing attacks and scraping. Decide in advance who may enable stricter rules during an incident.
• Backups: confirm that backups run, then actually restore one to a test environment and time it. An untested backup is not a backup.
• ईमेल: confirm that order confirmations and shipping emails arrive in inboxes at your expected volume. E-commerce order email deliverability covers authentication and sending limits. Schedule marketing sends so they do not all hit the site in the same minute.

2 weeks before: monitoring and communication

• Monitor what earns money. Beyond the home page, add checks on a product page, the cart and the checkout page, with keyword checks for text that must be present (for example the "Pay" button label or the product title). See payment gateway downtime monitoring.
• Tune intervals and alerts. Check often enough that you learn about a failure within minutes; see how often should you monitor a website. Send alerts to more than one channel (email plus a chat webhook or phone), and route them to a named person who is actually working that weekend. Our free plan includes a limited number of monitors, so choose your most important URLs first.
• Test the alert path. Trigger a test alert and confirm it reaches the on-call person. Check that false alarms are controlled by following reduce false alerts.
• Publish a status page with a clear address you can share, so support and social media can point to one source during an incident. See website status page guide and the status page tool. Pre-write the messages with status page communication templates.
• Agree a runbook. For each likely failure (site down, checkout failing, slow pages, payment provider issue, email delay) write the first three actions, the person responsible and the escalation contact. Keep it where people can find it from a phone.
• Brief support and marketing on what to do if checkout fails: pause paid campaigns, hold email sends, post status updates.

1 week before: freeze and rehearse

• Change freeze. Stop deploying features, theme changes and plugin updates several days before the event. Allow only fixes agreed by the owner of the checklist. Most peak-day outages follow a change, not a traffic spike. Define the freeze start and end dates and write them down.
• Staging parity. Make sure the final build was tested end to end: add to cart, discount codes, shipping calculation, tax, each payment method, order email, inventory update.
• Run a rehearsal. Place a real test order with each payment method, then refund it. Check the order appears in the admin, the warehouse or fulfilment system and the email inbox.
• Rollback plan. Know how to revert the theme, the plugin or the code release in minutes, and who is allowed to do it. Keep the previous version available.
• Inventory and limits. Confirm stock levels sync correctly and that overselling rules are set the way you want. Check the payment provider's transaction and payout limits so a large day is not stopped by a cap.
• Shipping and carriers. Verify carrier rate APIs and cutoff dates. Their outages look like checkout errors.

Launch day

• Watch the monitors and dashboards in a shared channel, with at least two people on watch.
• Keep a log of changes, even tiny ones, with time stamps.
• Check order volume against the expected curve every hour. A flat line is as much an alarm as an error message.
• Test the checkout yourself every few hours, using a real device on mobile data as well as office Wi-Fi.
• Update the status page quickly if anything degrades, even when you do not know the cause.

After the event

• Keep the freeze until the main rush is over; then plan updates in calm periods.
• Review monitoring history, response times and any incidents. Write short postmortems while memory is fresh, and compare the real downtime cost with the estimate from before.
• Update the checklist for next year with what you learned.

अगले कदम

• Set up monitors for key pages with the uptime monitor.
• Check certificates and expiries with the SSL Checker and the domain expiry watch.
• Prepare a public status page.
• Estimate your peak-hour exposure: ecommerce downtime cost.
• Monitor scheduled jobs with cron monitoring.

सामान्य प्रश्न

When should I start preparing for Black Friday?

About eight weeks ahead is a comfortable window, because performance work, load testing and security updates need time to test. If you have less time, prioritize monitoring, a change freeze, expiry checks and a tested checkout.

Do I need a load test?

If you control your hosting, yes: it tells you where your store breaks first. On a managed platform you may not be able to test the platform itself, but you can still test your own apps and integrations on staging and review plan limits.

What should I monitor on launch day?

Home page, a product page, the cart and checkout page with keyword checks, payment webhooks and any critical scheduled job. Alerts should go to a person who is awake and able to act.

Should I freeze deployments?

Yes. Most outages follow a change, so a freeze starting several days before the event removes the biggest source of risk. Allow only reviewed fixes with a rollback plan.

How do I handle an outage during the sale?

Follow the runbook: confirm the issue, pause paid campaigns if checkout is affected, update the status page, fix or roll back, and write a short postmortem afterward.

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.