Finding your WordPress site down is a horrible feeling, especially if it’s how customers reach you. The good news: most outages come from a short list of causes, and you can work through them calmly in a few minutes. This checklist walks you through it in order — quickest, most common fixes first — so you’re not randomly clicking buttons while the clock runs.
Before you change anything, take a breath. A site that’s down is almost always recoverable. Panic edits are what turn a ten-minute fix into a rebuild.
First: is it actually down, or just down for you?
Half of all “my site is down” scares aren’t outages at all — they’re a stale cache or a local network hiccup on your end. Rule that out in thirty seconds:
- Try a different device or network. Load the site on your phone using mobile data (not your home Wi-Fi). If it works there, your site is fine and the problem is your browser or connection.
- Do a hard refresh. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to bypass your browser’s cache.
- Use a “is it down” checker. Free tools like downforeveryoneorjustme.com or a quick check from a phone on cellular tell you if the outside world sees it too.
If it loads for everyone else, you’re done — clear your cache and move on. If it’s genuinely down for the world, keep going.
The 60-second triage
Look closely at what you’re seeing. The screen is your best clue, and it usually points straight at the cause:
- A blank white page → almost always a plugin, theme, or PHP (the programming language WordPress runs on) memory problem. See our walk-through on the WordPress white screen of death.
- “Error establishing a database connection” → your site can’t reach its database. We cover this one step by step in how to fix that database connection error.
- “500 Internal Server Error” → usually a broken plugin, a corrupt
.htaccessfile (a server settings file), or exhausted memory. - “503 Service Unavailable” → the server is overloaded or in maintenance mode.
- Someone else’s page, spam, or a redirect to a sketchy site → this isn’t an outage, it’s a hack. Go straight to how to fix a hacked WordPress site.
The step-by-step checklist
1. Ask yourself: what changed?
Sites rarely fall over on their own. Nine times out of ten, something changed right before the outage — you updated a plugin, added a new one, edited the theme, or an automatic update ran overnight. Whatever you touched last is your prime suspect. If you know what it was, undoing that one change is often the entire fix.
2. Deactivate plugins — the number-one cause
A single incompatible or badly-coded plugin can take down an entire site. If you can still reach your dashboard, deactivate plugins one at a time, checking the site after each one, until it comes back. That tells you the culprit.
If you can’t reach the dashboard, you can do the same thing over SFTP (a secure way to connect to your site’s files) or your host’s file manager: rename the wp-content/plugins folder to plugins-off. That deactivates everything at once. If the site returns, rename it back and disable plugins one by one to find the bad one.
3. Switch to a default theme
If plugins aren’t it, a theme update or a bad edit to functions.php may be the problem. Temporarily switch to a stock theme like Twenty Twenty-Four (rename your active theme’s folder over SFTP if you’re locked out of the dashboard). If the site loads, the theme is your answer.
4. Increase the PHP memory limit
A site that runs out of memory often shows a blank page or a 500 error. Adding a single line to your wp-config.php file (WordPress’s main settings file) — define('WP_MEMORY_LIMIT', '256M'); — is a common fix. If your host caps memory low, this is also a sign you’ve outgrown a cheap plan.
5. Rule out the domain and SSL
Sometimes the site is fine but nobody can get to it. Check that your domain hasn’t quietly expired (it happens more than you’d think) and that your SSL certificate (what powers the HTTPS padlock) is still valid — an expired certificate throws a scary “not secure” warning that stops visitors cold. Good hosting renews certificates automatically so this never becomes your problem.
When it’s the host, not you
If you’ve ruled out plugins, themes, memory, and your domain — and especially if you’re seeing 503 errors or database connection failures that come and go — the problem is likely on the server. That’s the host’s job, not yours. On cheap shared hosting, “the server is overloaded” often means a hundred other sites on the same box are having a busy afternoon and yours is paying for it.
This is exactly where the kind of hosting you’re on matters. Managed WordPress hosting is built so that one busy neighbor can’t drag you down, and so that when something does break, we are alerted to it. Our plans include a layered firewall and a live list of known attackers, speed tuning and fast worldwide delivery, and automatic, verified updates — so the things that cause most self-inflicted outages are handled before they reach you. And every time we update your site, we verify it still looks and works right, so an update doesn’t become tomorrow’s outage.
How to never get surprised again
The worst part of an outage is finding out about it from an angry customer. Uptime monitoring fixes that: your site is monitored automatically, and the moment it stops responding, the alert goes to the people who can act on it — not to you at 2am. It’s part of every plan we run, along with off-site backups 3 times a day so that if a fix goes sideways, there’s always a clean copy to fall back to. If today’s outage turned into a mess, our guide on how to restore WordPress from a backup gets you back to a known-good version.
Still stuck?
If you’ve worked through this list and your WordPress site is still down, don’t keep making changes under pressure — that’s how a recoverable outage becomes a rebuild. Restore from your most recent clean backup, or move the site to us. We only repair sites we host: we clean it up as part of the move, get it working, and tell you in plain English what happened and how to keep it from happening again. See what’s included — and if you’re mid-emergency, your move starts as soon as you sign up: Start my move.