That message looks like the end of the world, and in practice it almost always means one broken plugin or theme. “There has been a critical error on this website” is WordPress saying: a piece of PHP code fell over and I stopped everything before it got worse. Your data is intact - products, posts and orders are sitting in the database untouched. All that is left is to find the culprit and unplug it.
I am writing this so you can walk through the repair yourself, step by step, without knowing any code. And if at some point you feel this is not your thing, there is a shortcut at the end.
What this error actually means
WordPress is an engine plus a few dozen add-ons: the theme and the plugins. Every update, every new plugin, every change on the server can make one of those stop getting along with the rest. PHP then halts, and you get exactly this message - often at the worst possible moment, because the error likes to surface after an automatic update overnight.
The most common causes, in order of likelihood:
- A plugin after an update - a conflict with another plugin or with an older version of WordPress
- The theme - especially one edited by hand or not updated in a long time
- A PHP version that is too old or too new on the server relative to what one of the plugins requires
- Memory limit exhausted - the site grew, the limit stayed from back when it was small
- Corrupted files after a failed update or an interrupted upload
Step 1 - check your email
On a critical error WordPress sends a message to the site administrator’s address, with a subject along the lines of “Your site is experiencing a technical issue”. Inside are two valuable things: the name of the plugin or theme that caused the error, and a link to recovery mode - a special login that opens the admin panel with the culprit disabled.
If you have that email: click the link, log in, disable the plugin it names and the site comes back. Then check whether a newer version exists, or look for a replacement. That is the shortest version of the whole repair.
What helps: check the spam folder too, and confirm which address is set as the administrator email. On plenty of the sites I rescue, that address is an old mailbox from years ago - and the valuable rescue emails fly off into the void.
Step 2 - no email: disable the plugins over FTP
No email, or the link has expired? You go in through the back - over FTP or the file manager in your hosting panel (every host has one, usually called “File Manager” or “WebFTP”).
- Find the
wp-content/pluginsfolder - Rename the whole
pluginsfolder toplugins-off- that disables every plugin at once - Open the site. Working? The culprit is one of the plugins
- Restore the
pluginsname, then rename individual plugin folders one by one, checking the site each time - until you find the one - Leave that one disabled and switch the rest back on
If disabling every plugin changed nothing, run the same manoeuvre on the theme: in wp-content/themes, rename the active theme’s folder. WordPress will fall back to the default theme and the site - ugly as it may be - should come back up.
Step 3 - when it is neither a plugin nor the theme
What is left is server-side. In your hosting panel, check the PHP version - if it is older than 8.1, raising it alone can solve the problem (and speed the site up along the way). If the error appeared right after you raised the version, drop back down one step and plan updates for the plugins that could not keep up.
The memory limit is raised with an entry in the wp-config.php file, but here we are already at the edge of a DIY repair - one typo in that file and the site will not come back at all. If you have got this far with no result, the problem is probably deeper: corrupted core files, the database, or something that looks like a critical error but is actually a 500 error on the server side - a related failure, but one you diagnose differently.
What not to do
- Do not reinstall WordPress from scratch - it is almost never necessary and it is easy to lose your configuration doing it
- Do not delete plugins blind - disabling one (renaming its folder) is reversible, deleting sometimes is not
- Do not leave the site “until tomorrow” - to Google and to customers, a site showing an error is a site that does not exist; after a few days it starts costing you rankings
A separate note: if alongside the error you see unfamiliar content on the site, strange redirects, or your host is writing to you about malicious code, this is not an ordinary failure. In that case work through the recovery plan for a hacked site, because disabling plugins alone will not remove the intruder.
How not to be back here in a month
A critical error is almost always an effect, not a cause. The cause is a missing rhythm: updates done in bulk once every six months, with no backup and no check of the site afterwards. How to organise that - with a backup before and a test after - is written out in the safe update checklist. The alternative is handing that rhythm to someone who does it professionally as part of ongoing site care - then a failure like this ends with a “fixed” text message before you even notice it happened.
FAQ
Will the critical error go away on its own? No. Until the culprit is disabled the site stays down - and every day is lost customers and a signal to Google that the site is out of service.
Is my data safe? Yes, content and orders live in the database, which this error does not touch. The risk only appears with panicked moves - reinstalls and deleting files.
What does a professional repair cost? A typical diagnosis plus repair is hours of work, not days. I give the specific figure after looking at the site - always in writing, before we start.
Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.