If your site suddenly shows the message “There has been a critical error on this website,” don’t panic. This message means WordPress hit a fatal PHP error, and in most cases the cause is a plugin conflict, a theme problem, or a failed update. Your content is almost certainly safe. Here is exactly how to diagnose it and fix it.
What causes the critical error in WordPress?
WordPress shows this message whenever PHP, the code that runs your site, crashes before the page can finish loading. The most common triggers are a plugin update that conflicts with another plugin or your theme, a theme update that broke something, a PHP version mismatch after a hosting change, a corrupted file from an interrupted update, or your site running out of memory. Older versions of WordPress showed a blank page instead (the famous white screen of death), so this message is actually an improvement. At least now you know something crashed.
Step 1: Check your email for the recovery link
WordPress usually emails the site admin when a critical error happens. That email names the plugin or theme that caused the crash and includes a special recovery mode link. Click it, log in, and WordPress will let you deactivate the broken plugin or theme even though the site is down. This is the fastest fix, so check your inbox (and spam folder) first.
Step 2: No email? Deactivate plugins manually
If there’s no recovery email, connect to your site with your host’s file manager or FTP and open the wp-content folder. Rename the “plugins” folder to “plugins-off” and reload your site. If it comes back, a plugin caused the crash. Rename the folder back to “plugins,” then rename individual plugin folders one at a time until you find the culprit. When you find it, leave it deactivated and look for an update, a replacement, or a fix.
Step 3: Rule out your theme and PHP version
If plugins aren’t the problem, rename your active theme’s folder inside wp-content/themes. WordPress will fall back to a default theme. If the site loads, your theme is the issue. Also check your hosting control panel for your PHP version. Sites running very old PHP versions crash when modern plugins expect newer code, and sites pushed to a brand new PHP version can crash when an old plugin isn’t compatible with it.
Step 4: Read the error log
Every crash leaves a trail. Your hosting account has an error log (often a file called error_log in your site’s root folder) that names the exact file and line that failed. The last entry usually points straight at the broken plugin or theme. If the log mentions “memory exhausted,” raising the PHP memory limit in wp-config.php often solves it.
Frequently asked questions
No. The critical error means the code that displays your site crashed, not that your content is gone. Posts, pages, images, and settings live in your database, which is separate from the plugin and theme files that usually cause the crash. Once the faulty plugin or theme is deactivated or repaired, your site comes back exactly as it was. The only real risk to your content comes from aggressive fixes attempted without a backup, which is why we always back up a site before repairing it.
Most critical errors are diagnosed and fixed in one to two hours of work, so the cost is usually modest compared to the revenue lost while a site is down. Simple plugin conflicts sit at the low end. Corrupted core files, hacked sites, or errors tangled up with other problems take longer. We give you an honest estimate after a quick look at the error log, before any billable work begins.
Simple cases, like a single plugin conflict named in the recovery email, can be fixed in under an hour. Most critical errors are resolved the same day. If the error log points to deeper problems, such as database corruption or malware, we tell you up front what is involved and how long it should take before we start.
When to call in help
If you’ve tried these steps and the critical error won’t go away, or you’re not comfortable renaming folders on a live site, that’s a completely reasonable place to stop. One wrong move in the file manager can make things worse. We fix critical errors for small businesses across Durham, Raleigh, and beyond, usually the same day, and we always take a full backup before touching anything. Visit our WordPress troubleshooting and repair page or request a quote and tell us what you’re seeing.