Your website is down. Maybe you are staring at a white screen. Maybe there is a scary red error message. Maybe the whole thing just vanished. Whatever happened, here is the most important thing to know right now: this is almost certainly fixable, and panicking will only make it worse.
This guide covers the most common WordPress emergencies, what to do about each one, what absolutely not to touch, and when to stop trying and get professional help. Read the section that matches your situation and follow the steps in order.
Site down right now?
Sparks Motion handles WordPress emergencies quickly. Tell us what is happening and we will get your site back up.
White Screen of Death
You load your site and get a completely blank white page. No error message, no content, nothing. This is one of the most common WordPress failures, and it is almost always caused by a PHP error in a plugin or theme.
What to do: If you can access your hosting file manager or FTP, navigate to /wp-content/plugins/ and rename the folder of the most recently updated plugin. This deactivates it without needing dashboard access. If the site comes back, that plugin was the problem. If you cannot identify which plugin was updated last, rename the entire plugins folder to plugins-disabled. This deactivates all plugins at once and will usually restore the site.
What not to do: Do not delete plugin folders. Renaming is reversible. Deleting is not.
Critical Error Message
WordPress displays a message that says "There has been a critical error on this website." This was introduced in WordPress 5.2 and is actually helpful because it means WordPress detected the error and sent you a recovery email with a link to log in safely.
What to do: Check your admin email inbox (including spam) for the recovery mode email. The link lets you log into a special recovery dashboard where you can deactivate the problem plugin or switch themes. If you never received the email, you can still use the FTP method described above to deactivate plugins manually. For a full walkthrough, see our guide on WordPress critical errors after plugin updates.
500 Internal Server Error
A 500 error means something went wrong on the server, but the server cannot tell you what. It is the least helpful error message in web development, which is why it is also the most frustrating.
What to do: Start with the .htaccess file. Use FTP or your file manager to rename it to .htaccess-backup. If the site loads, the file was corrupted. You can regenerate it by going to Settings, then Permalinks in your WordPress dashboard and clicking Save. If that does not fix it, check your server error logs through your hosting control panel. The log will show the specific error causing the 500.
Database Connection Error
"Error establishing a database connection" means WordPress cannot communicate with your MySQL database. This can happen after a hosting migration, a server restart, or if your database crashed.
What to do: Open your wp-config.php file and verify the database credentials: DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST. Log into your hosting control panel and confirm the database exists and the user has correct permissions. If everything looks right, contact your hosting provider. The database server itself may be down or overloaded.
Not comfortable with FTP or file managers?
That is completely normal. Most business owners should not have to troubleshoot server configuration files. We do this every day and can resolve most emergencies within a few hours.
Plugin Conflict
Your site loads but something specific is broken: a form does not submit, the menu is missing, the page layout is scrambled, or a feature stopped working. This is almost always a plugin conflict, usually triggered by an update.
What to do: Deactivate plugins one at a time, starting with the most recently updated. Test after each deactivation. When the broken feature starts working again, you have found the conflict. Check if an update is available for the conflicting plugin, or contact the plugin developer. For more detail, see our WordPress plugin risk checklist.
Hacked Site
You see unfamiliar content on your site, your visitors are being redirected to spam websites, Google is showing a "This site may be hacked" warning, or your hosting provider sent a malware notification. This is a security breach and it needs immediate professional attention.
What to do: Do not try to clean a hacked site yourself unless you have experience with malware removal. Change your WordPress admin password and your hosting account password immediately. Contact your hosting provider to see if they offer malware scanning and removal. Then get professional help. A hacked site needs a systematic cleanup: every file needs to be inspected, backdoors need to be found and removed, and the entry point needs to be identified and closed.
What not to do: Do not just delete suspicious files. Hackers typically install multiple backdoors, and removing one without finding the others means they will be back within days.
Locked Out of Your Dashboard
You cannot log into WordPress. The login page loads but your password does not work, or the login page itself is broken.
What to do: Try the password reset link first. If that email never arrives, you may have an email delivery issue (see our guide on why contact forms stop sending emails for related fixes). If you need to reset your password manually, you can do it through phpMyAdmin in your hosting control panel by editing the wp_users table. If a security plugin locked you out, rename that plugin's folder via FTP to deactivate it.
What NOT to Touch During an Emergency
When your site is down, there are several things that will make the problem worse if you touch them without understanding the consequences:
- Do not edit the database directly unless you know exactly which table and which row to change
- Do not delete your theme folder — this removes all of your customizations permanently
- Do not update WordPress core, plugins, or themes while your site is in a broken state
- Do not restore just the database without also restoring the matching files
- Do not switch hosting providers in the middle of an emergency — fix the problem first, then evaluate
When to Get Help Immediately
Get professional help right away if any of these are true: your site has been hacked, you run a WooCommerce store and checkout is broken, you are not comfortable using FTP or file managers, the error involves your database, or you have already tried fixes that did not work and the situation is getting worse.
Our WordPress Plugin Fix service handles emergencies. The How to Fix a Broken WordPress Website guide covers additional scenarios in detail.
Let us handle the emergency
Describe the problem and we will respond quickly. Most WordPress emergencies are resolved the same day.
Frequently Asked Questions
Q: How long does it take to fix a WordPress site that is down?
Most common issues (plugin conflicts, white screen, 500 errors) are resolved within one to three hours. Hacked sites take longer because every file needs to be inspected and cleaned, which can take four to eight hours depending on severity.
Q: How much does emergency WordPress help cost?
A single-issue fix starts at $175. More complex problems like hacked site cleanup or database repair are quoted based on scope. We never bill by the hour, so you know the cost before work begins.
Q: My hosting provider says my site is using too many resources. What does that mean?
This usually means a plugin or a script is consuming excessive server resources, often caused by a poorly coded plugin, a brute force attack on your login page, or a database that needs optimization. It does not necessarily mean you need a bigger hosting plan.
Q: Can I fix a hacked WordPress site myself?
You can try, but it is risky. Hackers install multiple backdoors, and if you miss even one, they will regain access. Professional malware removal includes a systematic inspection of every file and database table, which is difficult to do thoroughly without experience.
Q: My site was working yesterday and broke overnight. What happened?
The most common cause is an automatic plugin or WordPress update that introduced a conflict. Check your update log under Dashboard then Updates in your admin area. If you cannot access the admin, check with your hosting provider to see if any server-level changes were made.
Q: Should I just start over with a new WordPress installation?
Almost never. Even a severely broken site can usually be repaired without losing content, settings, or configurations. Starting over means rebuilding every page, every setting, and every plugin configuration from scratch. Fix first, rebuild only if fixing is genuinely more expensive than rebuilding.
Q: How do I prevent emergencies in the future?
Three things: keep automated backups running daily, never click "Update All" without testing on a staging site first, and have a maintenance plan that includes regular security scans. Our maintenance checklist covers everything you need.
Need help right now?
Our WordPress emergency help page explains how it works, what it costs, and how to send us the details.
Prefer to try it yourself first? Our step-by-step guide to fixing a broken WordPress site covers the most common causes in order.