There has been a critical error on this website. Sometimes followed by Please check your site admin email inbox for instructions. That is all WordPress tells you — and for many site owners, this one sentence is the first sign that something has gone seriously wrong.
The message looks alarming, but it is actually WordPress protecting you. Older versions simply showed a blank white page. Today, WordPress catches the failure and tells you something broke. What broke, and why, is the part it keeps to itself.
What the Message Means
Behind the scenes, a piece of PHP code on your site has hit a fatal error — a mistake serious enough that WordPress cannot continue building the page. Instead of crashing silently, it stops, shows this generic message to visitors and, if it can, sends an email to the site's admin address.
The error can affect the whole site or only certain pages. Sometimes the admin area still works while the front end is broken; sometimes it is the other way around. Which parts fail is already a clue to where the problem sits.
The Email You Should Look For
When WordPress detects a fatal error, it tries to send a message to the administrator email address set in your site's settings. That email usually names the plugin or theme that caused the problem and contains a special link that opens a limited "recovery mode" in the dashboard.
Two common snags: the email often lands in spam, and on many sites the admin address belongs to whoever built the site years ago. If nobody receives that email, you are left with only the error message — and no hint where to start.
The Most Common Causes
1. A plugin update gone wrong
By far the most frequent trigger. A plugin updates, and the new version clashes with another plugin, your theme or your PHP version. The site worked yesterday; today it does not.
2. A theme problem
Themes that have not been updated in a long time — or custom themes built for an older WordPress — can call functions that no longer exist. Everything falls over the moment WordPress or PHP moves on.
3. A PHP version change at the host
Hosting providers regularly retire old PHP versions. When your site is moved to a newer version, older plugins and themes that were never updated can stop working overnight — even though you did not change anything yourself.
4. Running out of memory
Heavy page builders, large imports or poorly optimised plugins can exceed the PHP memory limit set by the host, which ends in a fatal error.
5. Edited or damaged files
A small code change in a theme file, a snippet pasted into the wrong place, an interrupted update or malicious code injected into the site can all produce the same message.
What to Check Before Touching Anything
- Search your inboxes for the WordPress email, including spam, and check which address is set as the site admin.
- Note what changed recently: updates, new plugins, theme edits, or a notice from your host about PHP.
- Check whether the admin area still loads. If it does, the problem is more likely front-end or theme related.
- Make sure a recent backup exists before anyone starts changing things.
Why Guessing Makes It Worse
The usual advice online is to deactivate plugins one by one until the site comes back. It can work — but on a business site, switching plugins off at random can break forms, checkout, redirects or SEO settings, and on WooCommerce sites it can interrupt live orders. Reactivating them later does not always restore their settings either.
The faster and safer route is to read the actual error first. The server's error log names the exact file and line that failed, which turns a guessing game into a targeted fix. Getting to those logs, reading them correctly and fixing the cause without side effects is where most site owners understandably get stuck.
Stopping It From Happening Again
A critical error is almost always the result of an untested change hitting the live site: an update, a PHP switch, an edit. Testing updates on a staging copy first, keeping plugins and themes current, watching for PHP deprecation notices from your host and monitoring the site around the clock turns this from a crisis into a non-event.