The CW Corner – Your Website Is Down: A Calm First-Hour Checklist
If your website is down, take a breath before changing anything. A calm first-hour checklist helps you gather useful facts and avoid turning one problem into several.
A site can appear down in different ways. You might see a blank white page, a server error, or a page that never finishes loading. Your browser might warn about the connection. Or the site may load for you but fail for a customer.
Those symptoms do not all point to the same cause. Your first job is not to guess the fix. It is to find out what is happening.
First, confirm the site is really down
Check the site using another device on a different network. For example, turn off your phone’s Wi-Fi and try mobile data. If possible, ask someone outside your office to check, too.
Try a second browser on your own device. Your internet connection, router, browser, or a local network filter can make a working site look unreachable. If the site loads elsewhere, that is an important clue.
Also check what the customer actually sees. Ask them for the page address and the exact message, rather than relying on “it’s broken.” A homepage may load while a form, booking page, or other important feature fails.
For now, confirm the problem from another connection before touching the website.
Read the message before clicking
Read the browser or server message carefully. Write down its exact wording, or take a screenshot that includes the address bar. Don’t click through a warning or dismiss an error before recording it.
A “500” style server error usually means the server received the request but failed while trying to handle it. The message alone may not tell you exactly why.
A “can’t be reached” or timeout message often points to a networking issue, the Domain Name System (DNS), or the server itself. DNS directs a domain name to the server that hosts the site.
A certificate warning is a different problem. An expired or incorrectly configured Secure Sockets Layer (SSL) certificate can trigger a browser warning, even when the server is responding. Don’t tell visitors to bypass that warning.
The wording helps your host or developer choose where to look first. It is much more useful than “my site is broken.”
Note when it started and what changed
Write down when you first noticed the problem. If you know when the site last worked, note that, too. Then ask yourself what changed shortly beforehand.
Possible clues include:
- A plugin or theme update.
- A new form or website feature.
- A hosting change or server move.
- A domain or DNS edit.
- A renewal that may have lapsed.
A recent change is often the first lead worth checking. This one note can save time, especially if someone else needs to investigate. Don’t try to undo every recent change at once.
Rule out simple administrative causes
Check the basics before assuming the website itself needs repair. These issues are often quick to confirm and easy to overlook during a stressful moment.
- Domain registration: Is the domain still registered and renewed? See our guide to what happens when your domain expires.
- SSL certificate: Is the certificate active and covering the address your customers use? Our article explains SSL certificates and the little padlock.
- Hosting account: Is there an unpaid invoice or account notice from your hosting provider?
- Host status: Has your provider posted a maintenance notice or reported a service interruption?
Check these items through the provider’s official website or account. Avoid following unexpected payment links in emails. A few basic checks can rule out straightforward causes before anyone changes website files.
If WordPress opens, look without changing anything
If you can reach your WordPress dashboard, take note of what you see. Does the dashboard load normally? Are there visible error notices? Does the problem affect the whole site or only certain pages?
If you have a staging copy, a developer may be able to check whether the site works with a default theme there. A staging copy is a separate version used for testing, away from the live business site.
Do not start deactivating plugins, reinstalling WordPress, or pasting code from a search result into a live site during an outage. Those steps can affect features, remove useful clues, or introduce new problems.
The WordPress guide to common errors explains several symptoms, including blank pages and server errors. WordPress also advises caution before making changes. Its debugging guide recommends using a staging environment or an appropriate backup before modifying a site.
If you are comfortable checking the dashboard, stick to observation. Leave changes to someone who understands the site and can protect its current state.
Know when to call your host or developer
Contact your host or developer when customers cannot use the site, the error persists across devices, or you see a certificate warning. Reach out sooner if your website handles appointments, inquiries, or other essential business tasks.
You do not need to diagnose the problem before asking for help. Send a short, useful report with:
- The exact error text or a screenshot.
- When the problem started, and when the site last worked.
- What changed shortly before the problem appeared.
- Whether the WordPress dashboard loads.
- Whether your business email still works.
- The best way to reach you.
That information gives the person investigating a useful starting point. “My site is broken” leaves them asking basic questions before they can begin.
If the outage follows a website change, mention that clearly. If you are unsure whether something changed, say so. Accurate uncertainty is more helpful than a confident guess.
Keep routine maintenance separate
A sudden outage needs triage, not an improvised maintenance session. Once the immediate issue is resolved, you can review your regular care plan separately. Our article on a website maintenance routine you will actually keep covers that different task.
For now, keep your notes, avoid risky live-site changes, and ask for help when the next step is unclear. That is a sensible response, not a failure to fix your own website.
A calm first hour can make the fix faster
A website outage is usually recoverable, especially when backups exist. The first hour is about gathering information, not performing heroics.
Confirm what is down, record what you see, check the simple administrative causes, and share the facts with your host or developer. Then let the right person investigate before making changes. Hopefully, this checklist helps you slow the moment down and get the repair moving.
European Union General Data Protection Regulation Compliant