Your WordPress site is down. Maybe it's showing a blank white page, maybe there's an ominous error message, or maybe your customers are telling you the checkout isn't working. Whatever the symptom, the sinking feeling is the same.
Before you do anything drastic, take a breath. Most WordPress emergencies have straightforward causes, and many can be resolved without calling in a professional. This guide walks you through the most common issues, what causes them, and what you can do right now to get your site back online.
First Steps: Don't Panic, Diagnose
Before you start changing things, take a systematic approach. Making random changes to a broken site often makes things worse.
Start by checking whether the problem is actually your site or your internet connection. Try loading the site on your phone (using mobile data, not Wi-Fi) or ask a colleague to check from their location. You can also use a free tool like Down For Everyone Or Just Me to confirm.
If the site is genuinely down, check your hosting provider's status page. Many outages are server-side and completely outside your control. Your host may already be working on it.
Next, think about what changed recently. Did you update a plugin? Change a theme? Edit a file? Install something new? In most cases, the cause of a WordPress crash is something that changed in the last few hours.
White Screen of Death
The WordPress "white screen of death" (WSOD) is exactly what it sounds like — a completely blank white page with no error message. It's one of the most common WordPress emergencies and usually one of the easiest to fix.
Common causes:
A PHP error in a plugin or theme is the most frequent culprit. Memory limit exhaustion can also trigger it, particularly on shared hosting. Occasionally, a corrupted WordPress core file is to blame.
What to try:
If you can still access your WordPress admin dashboard, go to Plugins and deactivate all plugins. If the site comes back, reactivate them one by one until you find the offender.
If you can't access the dashboard, you'll need FTP or file manager access through your hosting control panel. Navigate to wp-content/plugins/ and rename the folder to something like plugins-disabled. This deactivates all plugins at once. If the site loads, rename the folder back and then rename individual plugin folders to isolate the problem.
You can also try increasing the PHP memory limit by adding this line to your wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
To see the actual error message, add this to wp-config.php:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
Then check wp-content/debug.log for the specific error. This tells you exactly which file and line number caused the crash.
500 Internal Server Error
A 500 error means something went wrong on the server, but the server can't tell you exactly what. It's frustratingly vague, but the causes are usually predictable.
Common causes:
A corrupted .htaccess file is the number one cause. Plugin or theme conflicts are close behind. PHP version incompatibility, file permission issues, or an exhausted PHP memory limit can also trigger it.
What to try:
First, check your .htaccess file. Using FTP or your hosting file manager, find the .htaccess file in your WordPress root directory. Rename it to .htaccess-backup. Then go to Settings > Permalinks in your WordPress dashboard and click Save Changes — this regenerates a fresh .htaccess file.
If that doesn't work, try the plugin deactivation method described above. You can also try switching to a default WordPress theme (like Twenty Twenty-Four) by renaming your active theme's folder in wp-content/themes/.
Check with your host whether they've recently updated the PHP version. Some older plugins aren't compatible with PHP 8.x, and a server-side PHP upgrade can break things without any action on your part.
Database Connection Errors
If you see "Error establishing a database connection," your WordPress site can't communicate with its database. This is a serious error because your entire site — every page, post, product, and setting — lives in that database.
Common causes:
Incorrect database credentials in wp-config.php (sometimes changed during hosting migrations), a corrupted database, the database server being down, or your database hitting its size or connection limits.
What to try:
Open wp-config.php and verify these four values are correct:
DB_NAME — your database name
DB_USER — your database username
DB_PASSWORD — your database password
DB_HOST — usually 'localhost', but not always
You can find the correct values in your hosting control panel under the database section. If the credentials look right, your database server may be down — contact your host.
If the database is corrupted, you can try a repair by adding this to wp-config.php:
define('WP_ALLOW_REPAIR', true);
Then visit yoursite.com/wp-admin/maint/repair.php. Remember to remove that line from wp-config.php once the repair is complete, as it's accessible without authentication.
Plugin and Theme Conflicts After Updates
Updates are essential for security, but they occasionally break things. A plugin update might conflict with another plugin, or a WordPress core update might not be compatible with your theme.
Symptoms vary widely: broken layouts, missing functionality, error messages, or complete downtime. The key clue is timing — if the site broke right after an update, that update is almost certainly the cause.
What to try:
If you can access the dashboard, roll back the update. Plugins like WP Rollback let you revert to a previous version. If you can't access the dashboard, use FTP to replace the updated plugin folder with the previous version from your backup.
If you don't have a backup of the plugin, you can download older versions from the WordPress.org plugin repository. On any plugin's page, click "Advanced View" and scroll to "Previous Versions."
The safest long-term solution is to use a staging site for testing updates before applying them to your live site. Most good hosting providers offer one-click staging environments.
Hacked Site: Symptoms and Immediate Actions
A hacked WordPress site is every business owner's worst nightmare, but it's more common than you'd think. If your site has been compromised, acting quickly limits the damage.
Warning signs:
You might notice unexpected redirects to spam or malicious sites, new admin users you didn't create, strange content or links appearing on your pages, Google showing a "This site may be hacked" warning, your host suspending your account, or a significant sudden drop in search traffic.
Immediate actions:
First, change all your passwords immediately — WordPress admin, hosting account, FTP, and database. Do this from a device you trust is clean.
If your host hasn't already, take the site offline temporarily. You can do this by enabling maintenance mode or, in extreme cases, renaming the index.php file.
Scan the site using a security plugin like Wordfence or Sucuri. These can identify malicious files and code injections. Look particularly for unfamiliar files in your WordPress root, wp-content/uploads/, and wp-includes/ directories.
Restore from a clean backup if you have one. Make sure the backup predates the hack — check file modification dates carefully.
After cleaning up, harden the site. Update everything, remove unused plugins and themes, install a security plugin, and consider changing your hosting if the vulnerability was server-side.
Cleaning a hacked site properly is complex work. If you're not confident in what you're doing, this is one situation where calling a professional is strongly recommended. An incomplete cleanup almost always leads to reinfection.
WooCommerce-Specific Emergencies
When your online shop breaks, you're actively losing money with every minute of downtime. WooCommerce issues need fast, careful attention.
Checkout not working: This is often a payment gateway configuration issue, an SSL certificate problem, or a plugin conflict. Check your WooCommerce > Settings > Payments page first. Make sure your payment gateway is enabled and the API keys are correct. Test in WooCommerce's built-in test mode if available.
Orders not processing: If customers can place orders but they're not being completed, check your payment gateway dashboard directly. The issue might be on the gateway's side, not yours. Also check WooCommerce > Status > Logs for detailed error messages.
Cart or product pages broken: Usually a theme or plugin conflict. The WooCommerce Status page (WooCommerce > Status) includes a system check that flags common issues. The "Tools" tab also lets you clear transients, recount terms, and reset capabilities — any of which might resolve display issues.
Email notifications not sending: Order confirmations and shipping notifications are critical for customer confidence. Go to WooCommerce > Settings > Emails and verify they're enabled. Most email delivery issues are solved by installing an SMTP plugin like WP Mail SMTP and routing emails through a proper mail service rather than relying on your server's built-in mail function.
When to Call a Professional vs DIY
Some WordPress emergencies are genuinely straightforward to fix yourself — especially if you're comfortable with FTP access and editing configuration files. Plugin conflicts, .htaccess issues, and basic error diagnosis are all manageable for a confident site owner.
However, there are situations where you should get professional help:
Call a professional if your site has been hacked and you're not sure the infection is fully cleaned, you're dealing with database corruption or data loss, the problem involves server configuration you don't have access to, your WooCommerce store is losing orders and you can't identify the cause, or you've tried the steps above and the site is still down.
The cost of a professional fix is almost always less than the cost of extended downtime — especially if your site generates revenue. A few hours of expert time is cheaper than a week of lost sales and damaged customer trust.
The best emergency is the one that never happens. Regular maintenance — keeping WordPress, plugins, and themes updated, running daily backups, monitoring uptime, and hardening security — prevents the vast majority of these issues. A good WordPress care plan from a provider like wp-maintenance.pro includes all of this, plus emergency support when you need it.
Need Help Right Now?
If your WordPress site is down and you need it fixed fast, get in touch with Hampshire Websites. I've been fixing WordPress emergencies for over 14 years across Southampton, Portsmouth, Winchester, and the wider Hampshire area. Most issues are resolved same-day.
If you'd rather prevent emergencies altogether, take a look at the WordPress care plans at wp-maintenance.pro. Every plan includes proactive monitoring, regular updates, daily backups, and emergency support — so you're covered before, during, and after any issue.
