"There Has Been a Critical Error on This Website"
Higher-risk issue — be cautious and consider professional help sooner.
WordPress shows a bare white page saying "There has been a critical error on this website" — often with a line about checking your admin email inbox.
Common signs of this issue
- Visitors see a plain page: "There has been a critical error on this website."
- It may add "Please check your site admin email inbox for instructions."
- It can affect the whole site, or only the admin area while the public site still works (or vice versa).
- It usually appears immediately after a plugin update, a theme update, a WordPress core update, or a PHP version change at your host.
- This is WordPress's modern version of the old "white screen of death" — same causes, better message.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Check the admin email inbox for the site (including spam) for a message titled roughly "Your site is experiencing a technical issue." It names the exact plugin or theme that crashed and contains a special recovery mode link that lets you log in with the broken plugin safely switched off.
- That recovery link is the single most useful thing WordPress gives you here — from recovery mode you can deactivate the named plugin without touching server files.
- Note what happened right before the error: which plugin updated, whether auto-updates ran overnight, or whether your host changed PHP versions. That's almost always the trigger.
- Try
yoursite.com/wp-admin— if the login still loads, the crash may be limited to the public theme, and you can work from the dashboard. - Confirm you have a recent backup (or that your host keeps them) before any fixing starts — check, don't assume.
- If you can't find the recovery email, check which address WordPress has on file if anyone on your team knows it — it's often an old address from whoever built the site.
What this usually means
A critical error means some piece of PHP code — nearly always a plugin or theme — crashed hard enough that WordPress stopped rather than continue. The single most common story: a plugin update that isn't compatible with your PHP version or with another plugin.
The fix is usually not complicated: identify the crashing component (the email names it; otherwise the server's error log does) and deactivate it. The site typically comes straight back, minus that one plugin, and then the plugin can be updated, replaced, or fixed calmly.
Because it strikes right after updates, this error is the best argument for two habits: updating one thing at a time (so the culprit is obvious), and having a staging copy of the site to test updates on first.
What not to do
- Don't reinstall WordPress from scratch — the software isn't broken, one component is, and a reinstall risks the content database for no benefit.
- Don't start deleting plugin folders by FTP as a first move if the recovery email is available — recovery mode does the same thing more safely.
- Don't restore a week-old backup as step one; you'll lose recent orders, posts, or form entries when a two-minute plugin deactivation would have fixed it.
- Don't ignore it because the admin area still works — visitors are seeing a dead site, and Google notices sites that stay broken.
When to get help
If the recovery email can't be found and you're not comfortable in cPanel or FTP, this is a genuinely quick job for a WordPress professional — the error log names the culprit, deactivating it brings the site back, and the whole thing is often under an hour. For a business site that's fully down, that hour is easily worth it.
Could your hosting be the problem?
If your host is slow, unreliable, or hard to deal with, moving to a better one can clear up issues like this for good. One we genuinely recommend is Instant Access Internet Services — a smaller, compassionate company with 30 years in the business, known for being one of the fastest, with great management and low pricing. (Just a recommendation — no affiliate link, no kickback.)
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What causes 'there has been a critical error on this website'?
A fatal PHP crash — nearly always a plugin or theme, most often right after an update or a PHP version change. WordPress shows the generic message to visitors and emails the details to the site's admin address.
Where is the WordPress recovery mode email?
It goes to the admin email address set in WordPress (Settings → General), which is often an old address from whoever built the site. Check spam folders too. The email contains a special link that logs you in with the broken component paused.
Can I fix a critical error without the recovery email?
Yes — the crashing plugin can be identified from the server error log and deactivated via the hosting file manager or FTP by renaming its folder. If those words sound unfamiliar, it's a fast job for a professional rather than a good first FTP lesson on a live site.
Will my content be lost?
Almost never. Posts, pages, orders, and settings live in the database, which this error doesn't touch. The crash is in code, not content.
Is the critical error the same as the white screen of death?
Essentially yes — same class of fatal error. Older WordPress showed a blank white page; modern WordPress shows this message and sends the recovery email, which makes it much easier to fix.
How do I stop this happening again?
Update one plugin at a time rather than all at once, keep backups automatic, and if the site matters to your income, test updates on a staging copy first — most hosts offer one-click staging.