WordPress Site Down: A Troubleshooting Guide for Owners

When your WordPress site is down, the cause is usually one of five things: the domain or DNS, the hosting server, the database connection, a broken plugin or theme update, or an expired SSL certificate. Start by confirming it is down for everyone, then read the exact error on the screen, because each message points to a different layer. Most outages trace back to something that changed recently, so the fastest fix is often undoing the last update.

What it is, in plain English

"Site down" covers anything that stops a visitor from seeing your pages: a blank white screen, an error message, a browser warning, or a page that never finishes loading. WordPress itself is only one piece. It runs on a web server (the rented computer at your hosting company), stores its content in a database (a separate program that holds your posts, pages, and settings), and is found by browsers through DNS (the internet's address book that turns your domain name into the server's address).

Any one of those pieces can fail on its own, and the symptom looks similar to a visitor: your site simply isn't there. For a small business, that means booking forms that don't submit, product pages that don't load, and ad clicks you pay for landing on an error. The good news is that the error you see usually tells you which piece broke, which narrows the fix a lot.

How to find the cause: a step-by-step check

Work through these in order. Each step either finds the problem or rules out a whole layer, so you don't waste time editing files when the real issue is an unpaid domain.

Check whether it's down for everyone. Open the site on your phone with Wi-Fi turned off, or use a free "is it down" checker. If it loads elsewhere, the problem is your own network, browser cache, or a firewall that blocked your IP address.
Write down the exact message. Take a screenshot. "Error establishing a database connection" and "There has been a critical error on this website" lead to completely different fixes.
Ask what changed. A plugin update, a new theme, a PHP version change at the host, a DNS edit, a billing email you ignored. Recent changes explain most outages.
Check your email, including spam. Since version 5.2, WordPress emails the site admin when a plugin or theme causes a fatal error, with a link to recovery mode that lets you log in and deactivate the culprit. Your host and domain registrar also send expiry and suspension notices.
Look at your hosting dashboard. Check for a status or outage notice, a suspended account, or a full disk. Many hosts show resource limits and error logs right there.
Try the admin area. Go to yourdomain.com/wp-admin. If the dashboard loads while the front of the site doesn't, the theme is the likely suspect.
Disable plugins without the dashboard. If you can't log in, open your host's file manager or connect by SFTP (a secure way to browse the server's files), go to wp-content, and rename the plugins folder to plugins-off. If the site returns, rename it back and turn plugins on one at a time until it breaks again.
Restore a backup if nothing else works. A backup from before the problem started is often faster than diagnosing. Most managed hosts keep daily snapshots you can restore from the dashboard.

What each error usually means

What you see	Most likely cause	First thing to try
"This site can't be reached" or a DNS error	Domain expired, or DNS records changed or pointing to the wrong server	Log in to your domain registrar, check the expiry date and nameservers
"There has been a critical error on this website"	A PHP fatal error, usually from a plugin, theme, or PHP version change	Use the recovery mode link in your email, or rename the plugins folder
Blank white screen	Same as above, with error display turned off, or the server ran out of memory	Disable plugins, switch to a default theme, check the host's error log
"Error establishing a database connection"	Database server down, wrong credentials in wp-config.php, or a corrupted table	Check the host's status page, then confirm the database name, user, and password
500 Internal Server Error	Broken .htaccess file, a plugin error, or server resource limits	Rename .htaccess, then re-save permalinks once you're back in
"Briefly unavailable for scheduled maintenance"	An update was interrupted and left a .maintenance file behind	Delete the .maintenance file in the site's root folder
Browser warning "Your connection is not private"	SSL certificate expired or not renewed	Renew or reissue the certificate from your hosting dashboard
403 Forbidden or an "account suspended" page	Security plugin rule, wrong file permissions, or a billing or abuse suspension at the host	Check your host's messages and billing first, then permissions

If you want more detail on a PHP error, you can turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php. That writes errors to a log file instead of the screen. Turn it off again once you've found the problem, so visitors never see raw error output.

Examples for small businesses

A home services contractor after a plugin update. A forms plugin updates overnight and conflicts with the page builder. The site shows a critical error, and quote requests stop coming in. The owner finds the recovery mode email, deactivates the forms plugin, and the site loads again. The real fix is then waiting for a patched version or rolling the plugin back, and testing the quote form end to end before relying on it.

A dental office or med spa whose domain lapsed. The domain was registered years ago by a former web person, on a card that has since expired. Renewal notices went to an inbox nobody reads. The site and the office email both stop working on the same day. The fix sits entirely at the registrar: renew, then move the domain into an account the practice owns and controls.

An e-commerce store on WooCommerce during a sale. Traffic spikes, the shared hosting plan hits its limits, and pages start returning errors or timing out. Nothing is broken in WordPress itself. Short term, a caching plugin and pausing heavy background tasks can help; longer term, the store needs hosting sized for its busiest days, not its average ones.

A restaurant or cafe after a host-side change. The host upgrades the PHP version, and an old theme that hasn't been updated in years stops working. The menu page and online ordering link go blank. Switching back to the older PHP version buys time, but the lasting fix is replacing or updating the theme, because hosts eventually retire old versions for security reasons.

In every one of these, your Google Business Profile still shows your phone number and hours while the site is down. If the outage will last more than a few hours, it's worth checking that the listing is accurate, since it becomes your main front door. Our Google Business Profile checklist covers what to keep current.

Common mistakes

Updating everything at once on a live site. When ten plugins update together and the site breaks, you can't tell which one did it. Update in small batches, or on a staging copy first (a private duplicate of the site used for testing).
Assuming the host keeps backups you can use. Some plans back up only the server, keep copies for a short window, or charge to restore. Know where your backups are and test a restore before you need one.
Reinstalling WordPress as a first move. It rarely fixes plugin, database, or DNS problems, and a careless reinstall can overwrite changes you wanted to keep.
Leaving the domain in someone else's account. If a past developer or agency registered it, you may not get renewal notices and can't act quickly when something expires.
Leaving debug output switched on. Error messages shown publicly can reveal file paths and plugin names that help attackers. Log errors to a file, not the screen.
Ignoring repeat outages. If the site goes down every few weeks, the underlying cause (outdated plugins, underpowered hosting, a hacked file) is still there. Each quick fix just resets the clock.

You also don't always need outside help. If the cause is an expired domain, a lapsed hosting payment, or a single plugin you can switch off, you can usually fix it yourself in minutes. Hands-on help earns its cost when the database is damaged, the site was hacked, or you can't identify what changed.

What it costs and what drives the price

A self-service fix can cost nothing beyond your time, or just the renewal fee for a domain or certificate. When you bring someone in, the price depends less on the error message and more on how much digging it takes. These are the factors that move it:

Access. If you can hand over hosting, registrar, and WordPress logins right away, work starts immediately. Hunting down lost credentials or a former developer adds time.
Backups. A recent, working backup can turn a long repair into a short restore. No backup means rebuilding or repairing by hand.
Cause. A single bad plugin is quick to isolate. A hacked site needs cleanup, a search for backdoors, password resets, and sometimes a request to Google to remove a security warning, which takes much longer.
Site complexity. A brochure site with a handful of plugins is simpler to test than a WooCommerce store with payments, shipping rules, and customer accounts.
Urgency. Same-hour, after-hours, or weekend work typically costs more than a fix scheduled for the next business day.
Ongoing care. A one-time repair is priced per job. A monthly maintenance plan with updates, monitoring, and backups costs a recurring fee but usually catches problems before visitors see them.

FAQ

Why is my WordPress site down?

The most common causes are a plugin or theme conflict after an update, an expired domain or SSL certificate, a hosting outage or suspension, a database connection problem, or the server running out of resources. The error message on screen narrows it down.

How do I check if my WordPress site is down for everyone or just me?

Load it on your phone using mobile data instead of Wi-Fi, or use a free online "is it down" checker. If it works elsewhere, clear your browser cache and check whether a security plugin blocked your IP.

How do I fix "There has been a critical error on this website"?

Look for the recovery mode email WordPress sends to the admin address and use its link to deactivate the plugin or theme that failed. No email? Rename the plugins folder through your host's file manager or SFTP.

How do I fix the WordPress white screen of death?

Disable all plugins by renaming the plugins folder, then switch to a default theme if needed. If neither helps, check the error log in your hosting dashboard for memory or PHP errors.

What does "Error establishing a database connection" mean?

WordPress can't reach its database. Either the database server is down at the host, the login details in wp-config.php are wrong, or the database needs repair. Check your host's status page first.

Can a hacked site cause WordPress to go down?

Yes. Malicious code can break pages, redirect visitors, or get your account suspended by the host. If you see unfamiliar admin users, strange redirects, or a browser security warning, treat it as a hack, not an ordinary error.

Tell us what's broken, and we'll tell you where to look first: send a short brief.