"There has been a critical error on this website. Please check your site admin email inbox for instructions."

If you're seeing this message, don't panic. This is WordPress's way of telling you something broke—but it's also trying to help you fix it.

What Is the Critical Error?

Starting with WordPress 5.2, instead of showing a blank white screen when something goes wrong, WordPress displays this friendlier error message and attempts to email you a recovery link.

Like the White Screen of Death, a critical error is a server-level PHP error. Something in your site's code—usually a plugin or theme—failed badly enough that WordPress couldn't continue loading.

The difference is that WordPress now catches these errors and tries to give you a way back in.

Did You Get the Recovery Email?

When a critical error occurs, WordPress sends an email to the site administrator with:

  • Details about what caused the error
  • A special link to access "recovery mode"

If you don't see it, check your spam folder. The email comes from your site's domain and may be filtered.

If you're set up as the site administrator, you should receive these emails. We often see clients forward these to us—they're useful because they point directly to the problem.

About Recovery Mode

Recovery mode is WordPress's attempt to let you access your admin dashboard even when there's a fatal error. It temporarily disables the problematic plugin or theme so you can log in and fix things.

Here's our honest take: we've never actually needed to use official recovery mode. When we get these errors, we go straight to the server logs, identify the problem, and fix it directly. Recovery mode is helpful for site owners without server access, but it's not always reliable.

If recovery mode isn't working, skip it and use the manual troubleshooting steps below.

Fixing the Critical Error

Step 1: Identify the Cause

The error email usually tells you which plugin or theme triggered the problem. If you have it, you already know where to look.

If you don't have the email, you'll need to:

  1. Check server error logs through your hosting control panel
  2. Enable WordPress debug mode by adding define('WP_DEBUG', true); to wp-config.php

The logs will show you the exact file and line causing the error.

Step 2: Access Your Site

If recovery mode works:

  • Click the recovery link in the email
  • Log in to WordPress in recovery mode
  • Deactivate the problematic plugin or switch themes
  • Exit recovery mode

If recovery mode doesn't work:

  • Access your site via FTP/SFTP or hosting file manager
  • Navigate to /wp-content/plugins/
  • Rename the problematic plugin's folder (e.g., problem-plugin to problem-plugin-disabled)
  • Try loading your site again

Step 3: Resolve the Issue

Once you've identified and deactivated the problematic code:

  • Check for updates: The plugin/theme developer may have already released a fix
  • Roll back: Install the previous version that was working
  • Find an alternative: If the plugin is abandoned or consistently problematic, replace it
  • Contact the developer: Report the issue so they can fix it

A Common Misconception

When clients forward us critical error emails, they often mention: "But I cleared my cache," or "I tried a different browser."

These aren't caching issues. They're not browser issues. Critical errors are server-level problems that only someone with code and server access can fix.

Clearing your cache won't help. Trying a different browser won't help. The problem is in the server-side code.

Critical Errors vs. Front-End Errors

One thing we've noticed: critical errors often affect only the admin side, not the public website.

This means your visitors might see a perfectly functional site while you're getting error emails. It's still important to fix those errors, which indicate something is wrong—but it's not always the emergency it feels like.

When to Call for Help

If the error message doesn't make sense to you or you're not comfortable editing files on your server, this is when to seek help.

These errors are usually straightforward for someone with WordPress development experience. What appears to be a scary server error is often just a plugin that needs to be rolled back or deactivated.

Prevention

  • Update plugins one at a time, not all at once
  • Use staging environments to test updates before applying to production
  • Maintain current backups so you can restore if needed
  • Work with a managed hosting provider that monitors for these errors proactively

With proper monitoring, critical errors trigger immediate alerts. We often investigate and resolve issues before clients even realize there was a problem.

Dealing with a critical error? Contact our support team for fast, expert resolution.

This article is part of our WordPress Troubleshooting guide—a complete resource for diagnosing and fixing common WordPress errors.