A WordPress critical error means something on your site stopped WordPress from running as expected. The message hands you the first step itself. Check the inbox of the site admin email address, because that’s where WordPress sends its instructions. Don’t start pulling plugins. Open that inbox.

While that message shows, visitors can’t use the pages, forms or checkout behind it. You might not be able to log in and fix it either. A rushed fix can make the job harder. And a fix that only works for you leaves customers looking at the error. The email can get you back into your dashboard, the admin screen where you manage the site, but it doesn’t fix the site for visitors on its own.

What Does a WordPress Critical Error Mean?

Visitors see one line. Here it is, word for word: There has been a critical error on this website. Please check your site admin email inbox for instructions. As WordPress’s documentation on common errors puts it, the message indicates that something in your site has caused a critical error that prevents WordPress from running as expected. That’s the whole meaning of it.

The same page lists causes you might find behind it. A conflict between plugins, the add-ons that bolt extra features onto WordPress. A compatibility issue with your theme, which controls how your pages look. An incompatible version of PHP, the programming language WordPress runs on. Hitting the memory limit. Or corrupted WordPress files. The message doesn’t tell you which of those it is. It can’t.

What Should You Do First?

Check your email. WordPress’s page says to look there first, to see whether WordPress has sent you details about the error. The email goes to the site’s admin email address. That address lives inside WordPress itself, and it might not be yours. Confirming which one it is takes a moment, and it decides whether the rest of this works.

Three habits make that inbox check go smoother. They’re habits, not rules WordPress sets:

  • Know which address is set as the site admin email. It might be an old address, someone else’s, or a mailbox nobody reads.
  • Check the spam folder. The email carries the link, so it’s worth finding.
  • Write down what changed just before the message appeared: an update, a plugin you added, a theme change. Whoever fixes the site will want to know where to look.

How Does the Recovery Mode Link Work?

The email can carry a way back in. As the WordPress core team’s note on recovery mode describes it, a fatal error, meaning an error that stops the code from running, sends an email to the admin address with a secret link to a feature called recovery mode. That link is why the inbox check comes first. You click it. Then you log in. The plugins and themes causing the error, which the note calls extensions, are paused for you alone. A notice in your dashboard tells you recovery mode is on, and it shows which extensions are paused and what the errors are.

From there, the note gives you three routes. Deactivate the extension, which it calls a temporary but immediate resolution for when keeping a working version of the site matters more than that extension’s features. Fix the problem, if you have the technical skills. Or contact the extension’s author or a developer, and point out the exact error. You can leave recovery mode whenever you want, with a button in the admin bar.

Does Recovery Mode Fix the Site for Your Visitors?

No. The note is plain about it. The pause applies to the person using recovery mode, and for everyone else the site stays in a broken state until the issue is fixed or mitigated. The note adds that if an extension is still broken, the fatal error remains. So a working dashboard is progress. It isn’t the finish line.

One habit closes that gap. In recovery mode, your browser is the one place the pause applies. So after any fix, open your own site in a private browser window, where you aren’t logged in. That’s roughly what a visitor sees. If the error is still sitting there, you have more to do.

What Comes After the Email?

WordPress’s page gives the step after the email. Turn on debug mode in the wp-config.php file, then review the error log at wp-content/debug.log to find out what specifically went wrong. Debug mode writes the details into a file instead of leaving everyone to guess. That’s work for whoever looks after your site, not a step you need to take yourself. Hand over the email and what you wrote down, and let them read the log.

For whoever takes that step, a separate piece explains how to read the WordPress debug log and what its entries point to.

And if an update landed just before the error appeared, another piece shows how to plan WordPress updates with a rollback, so the one after it has a way back.

When Is It Worth Getting Help?

Spilt Media’s WordPress support page says its support plans handle updates, security, backups, performance optimization, content changes and troubleshooting.

The same page says the team tests and applies every WordPress core update, plugin update and theme update in a staging environment, which is a private copy of the site, before pushing it to the live site.

Treat these as habits for drawing the line. No WordPress email arrived. You can’t log in even with the link. The error comes back when you leave recovery mode. Or you don’t know which extension to turn off. If one of those fits, book a consultation with Spilt Media and bring the email and the error details along. The exact wording of the error matters more than a description of the screen.

Frequently Asked Questions About the WordPress Critical Error

Who gets the WordPress email?

The note says it goes to the site’s admin email address. That’s the address set inside WordPress, which might not be the owner’s own inbox. It can be an old address or a staffer’s. Checking which one it is before you need it is worth the minute.

Can visitors use my site while I’m in recovery mode?

No. The note says the pause applies to the person using recovery mode, and that for everyone else the site remains in a broken state until the issue is fixed or mitigated. So you can be looking at a working dashboard while a customer still gets the error.

Is deactivating the plugin a permanent fix?

The note treats deactivating as temporary, though it calls it an immediate resolution when keeping a working version of the site matters more than that extension’s features. The cause still needs dealing with. The note also says that if an extension is still broken, the fatal error remains.

What causes a WordPress critical error?

WordPress’s page lists causes you might find: conflicts between plugins, compatibility issues with your theme, an incompatible PHP version, hitting the memory limit, or corrupted WordPress files. The message doesn’t say which one applies to your site. That’s what the error log is for.