If your WordPress site is down, first confirm it’s actually down for everyone (not just you), then check what kind of error you’re seeing, since that determines the fix. A blank white screen usually means a plugin or theme conflict. A “database connection error” points to your host. A message saying the site is “briefly unavailable for scheduled maintenance” that never clears means an update got interrupted partway through.
Here’s how to work through it in order, without guessing.
Step 1: Confirm It’s Actually Down
Before anything else, rule out your own connection. Try the site on your phone with WiFi off, using mobile data, or ask someone in a different location to check. If it loads for them, the problem is local (your browser cache, DNS, or network), not the site itself. A third-party uptime checker works too, if it shows the site as reachable, clear your browser cache and try again before doing anything to the site.
Step 2: Identify the Type of Error
What you’re actually seeing narrows down the cause fast:
- A blank white screen (“White Screen of Death”): almost always a plugin or theme conflict, or a PHP memory limit that’s been exceeded.
- “Error establishing a database connection”: the site can’t reach its database, usually a hosting-side issue or corrupted database credentials.
- A 500 Internal Server Error: a server-level problem, often triggered by a bad plugin update, a corrupted .htaccess file, or a resource limit.
- Stuck in maintenance mode (“Briefly unavailable for scheduled maintenance”): an update process was interrupted, usually by a timeout or a lost connection mid-update, and WordPress never cleared the maintenance flag.
- A DNS or SSL error: not really a WordPress problem at all, usually an expired domain, an expired SSL certificate, or a DNS change that hasn’t finished propagating.
Step 3: What to Do for Each
If a plugin or theme conflict is likely, the fastest safe fix is deactivating plugins one at a time via FTP or your host’s file manager (renaming the plugin’s folder deactivates it without needing site access) until the site comes back. For a stuck maintenance-mode message, deleting the .maintenance file from the site’s root directory usually clears it. For a database connection error or 500 error, that’s the point to stop guessing and check with whoever manages your hosting, since it often points to something on the server side that isn’t fixable from the WordPress dashboard.
If none of that resolves it and a recent change caused the problem, restoring from a backup taken just before the issue started is usually faster and safer than continuing to troubleshoot live. This is where having real, recent backups actually matters, a backup from a week ago still means losing a week of changes.
Common Reasons WordPress Sites Go Down
- A plugin or theme update that wasn’t tested against the rest of the site before going live
- Server resource limits being exceeded, common on shared or underpowered hosting during traffic spikes
- An expired domain registration or SSL certificate
- Malware or a compromised plugin, especially on sites that haven’t had security updates applied
- An update process that got interrupted partway through and left the site in maintenance mode
Preventing This From Happening Again
Most of the causes above are preventable with the right setup: updates tested in staging before going live, real uptime monitoring that catches an outage in minutes instead of whenever someone happens to notice, and backups frequent enough that restoring one doesn’t mean losing days of work. That’s the core of what managed WordPress hosting is supposed to handle, and it’s why sites on properly managed infrastructure go down far less often than sites on cheap shared hosting with no one watching.
If your site is already down and you’d rather have someone else fix it than work through the steps above, that’s exactly what website support is for, same-day help from someone who can actually access the server, not just the WordPress dashboard.
Frequently Asked Questions
Why is my WordPress site showing a white screen?
A white screen with no error message is almost always caused by a plugin or theme conflict, or the site running out of available PHP memory. Deactivating plugins one at a time (or switching to a default theme temporarily) usually identifies the cause.
How long does WordPress downtime typically last?
It depends entirely on the cause and how quickly someone notices. A plugin conflict can often be fixed within minutes once identified. A hacked site or a hosting-level failure can take hours if there’s no monitoring in place to catch it immediately, which is the main reason uptime monitoring matters more than most site owners realize.
Can a hacked WordPress site be fixed?
Usually, yes. Malware removal, restoring from a clean backup, and closing whatever vulnerability let it happen (typically an outdated plugin) can get a site back online and secure. The bigger risk is Google flagging the site as compromised in search results, which can affect rankings even after the site itself is fixed.
Why does my site say it’s down for maintenance when I didn’t put it in maintenance mode?
This happens when a plugin, theme, or WordPress core update gets interrupted, often by a timeout, and WordPress never gets the signal to remove the temporary maintenance flag it sets during updates. Deleting the .maintenance file from the site’s root directory typically resolves it.
