What to Do When Your Website Goes Down: A Small Business Playbook

The site is down and you found out from a customer. That is the version of this that stings the most, and it is the one I hear about most often. There is a specific kind of panic that comes with it. You are not sure what broke, you are not sure how long it has been broken, and you are staring at your phone trying to remember who set the thing up in the first place. A plan does not make the outage shorter on its own, but it stops you from wasting the first fifteen minutes on the wrong things. Here is the order I work in.

Step one: confirm it is actually down

Before you do anything else, find out whether the site is really down or whether it is just down for you. This sounds obvious and people skip it constantly. Your own connection could be the problem, your browser could be serving a stale cached page, or your office wifi could be having a moment. Pull up the site on your phone with wifi turned off, so you are on cell data instead. If you have a tool like downforeveryoneorjustme or a quick check from a second network, use it. If it loads fine everywhere except your laptop, you just saved yourself a frantic hour. If it is down from every direction, now you know it is real and you move on.

Step two: figure out what kind of down it is

Not every outage is the same, and the type tells you who can fix it. A blank page or a connection timeout usually points at the hosting or the server. A message like 500 or 503 means the site is there but the software behind it is failing. A certificate warning that says the connection is not private is almost always an expired SSL certificate, which is its own small category with a deadline you could have seen coming, something I covered in the one outage you can predict. And sometimes the page loads but the important part, the booking widget or the checkout, is the thing that is broken. Knowing which of these you are looking at means you call the right person instead of guessing.

Step three: tell your customers before they tell each other

This is the step most small businesses skip, and it is the one that protects your reputation. While the site is down, put a short, honest note where people will see it. A pinned post on your Google Business Profile, a quick line on Facebook or Instagram, or an update to your voicemail if you take a lot of calls. You do not need details. Something like "our website is temporarily down and we are working on it, please call or email in the meantime" does the whole job. A customer who sees you are aware and reachable stays a customer. A customer who hits a dead page with no explanation assumes you closed. The cost of an outage is rarely the downtime itself, it is the lost trust and the sales that quietly walk, which is the real math I walked through in what an hour of downtime actually costs.

Step four: get the right person on it

Now you fix it, or you get the person who can. If you host with a big provider, check their status page first, because if their whole platform is having an outage there is nothing for you to do but wait and keep customers posted. If it is just your site, this is where having your logins and your host's support number written down somewhere calm pays off. The middle of an outage is a bad time to be hunting for a password. If you work with someone who built or maintains the site, this is the call to make, and a good arrangement means they are already looking because their monitoring told them before you did. That is the whole point of monitoring, and it is worth understanding what monitoring actually does before you need it rather than after.

Step five: write down what happened

Once the site is back, spend ten minutes on the boring part while it is fresh. What went down, what caused it, how you found out, and how long it took. This is not paperwork for its own sake. The same failure tends to come back, and the note you write today is what stops the second outage from being as slow and confusing as the first. If you found out from a customer this time, the fix is not just the technical one, it is making sure a monitor finds out first next time. A basic check that only pings your homepage will miss a broken checkout entirely, which is exactly the gap that synthetic monitoring closes over a plain uptime check.

The real goal: never be the last to know

Every step here gets easier when you are not starting from a customer's angry email. If a monitor pings you the moment the site goes down, step one is already done, you have a head start on step three, and the whole thing shrinks from a two-hour scramble into a twelve-minute event nobody outside your business even noticed. When I set a business up, I map the real path a customer takes, put checks on the parts that actually matter, and make sure the alert reaches a human who can act on it. You can see how I scope that in how I work. Whether you are in Medford, Cherry Hill, Mount Holly, or anywhere across Burlington and Camden County, the goal is the same: you find out first, every time.

Outages happen to careful people. The difference between a bad day and a quiet one is not whether your site ever goes down, it is whether you have a plan for the half hour after it does, and whether you had to hear about it from a customer at all.