Skip to content

Guide · WordPress · 6 min read

“There has been a critical error on this website”: what to do, step by step

In short: this WordPress message means that a code error is preventing part of the site from working, most often because of a plugin, the theme or a change in the version of PHP, the server’s language. Your content is usually not lost. Start by looking for the email WordPress sends to the site administrator: it contains a link to get in despite the failure and deactivate the cause.

See the 6 steps Assess my website

Getting out of a critical error in three movesThree steps out of a critical error: the email WordPress sends to the administrator, its recovery link, then deactivating the cause. The site content is usually intact.THE FASTEST WAY OUTThe email1from WordPressThe link2to recovery modeThe cause3to deactivateWordPress warns the site administrator by emailKEY TAKEAWAYYour content is usually intact:it is the display that has failed.Getting out of a critical error in three movesThree steps out of a critical error: the email WordPress sends to the administrator, its recovery link, then deactivating the cause. The site content is usually intact.THE FASTEST WAY OUTThe email1from WordPressThe link2to recovery modeThe cause3to deactivateWordPress warns the siteadministrator by emailKEY TAKEAWAYYour content is usuallyintact: it is the displaythat has failed.

What this message means

Since 2019, WordPress has protected itself against serious errors. Instead of showing a blank page or an incomprehensible technical message, it shows your visitors “There has been a critical error on this website”. Behind the scenes, an error in the code prevents part of the site from loading.

Good news: most of the time, nothing has been deleted. Your pages, articles and orders are still in the database, the place where WordPress stores all the site’s content. It is the display that has failed, not your data.

The most common causes

The causes of a critical error, and how to recognise them
CauseWhat happenedThe clue
A pluginIts update contains an error, or it clashes with another pluginThe failure follows an update or an installation
The themeA change or an update of the theme introduced an errorThe site’s look had just been changed
The PHP versionThe host changed the version of PHP, the server’s language, and an old plugin does not support itNobody touched the site
Server memoryThe site needs more memory than the hosting allowsOnly some heavy pages are affected
Damaged filesAn interrupted update left incomplete filesAn update stopped halfway

The first 30 minutes

The message has just appeared? Before any repair, do this, in order:

  1. Note what just happened. The time, and what was done just before: an update, a new plugin, a settings change.
  2. Look for the WordPress email. In the site administrator’s mailbox, including the spam folder.
  3. Measure the extent of the failure. Is the whole site affected, or only the admin area, or a single page?
  4. Delete nothing. And do not run other updates: it would make finding the cause harder.
  5. Act fast if you sell online. Every hour of downtime costs sales: if you cannot fix it yourself, call a professional right away.

The 6 steps to fix it

  1. Open the WordPress email. It is sent to the administrator’s address, with a subject along the lines of “Your Site is Experiencing a Technical Issue”. It often names the plugin or theme at fault.
  2. Use the recovery link. This special link opens the admin area in “recovery mode”, even though the site is down: you then log in with your usual username and password. From there, you can deactivate the faulty plugin. The link only works for a limited time, one day by default.
  3. No email? Go through the hosting. In your hosting file manager, rename the folder of the suspected plugin, in wp-content/plugins: WordPress deactivates it immediately. Renaming the whole plugins folder deactivates them all at once: then open the Plugins page in the admin area, rename the folder back and reactivate them one by one to find the culprit.
  4. Look at PHP. If nobody touched the site, ask your host whether the PHP version changed. Temporarily going back to the previous version can unblock things, while the plugin at fault gets updated.
  5. Restore a backup, as a last resort. A backup made just before the failure puts the site back on its feet, but orders and messages received since then would be lost: note them first. And without understanding the cause, the error may well come back with the next update.
  6. Fix the cause, not just the symptom. Once the site is back, update or replace the faulty plugin, check it is compatible with your PHP version, and test future updates on a copy of the site.

The fastest way out

In most cases, all you have to do is follow the route WordPress provides:

The fastest way out of a critical errorOpen the WordPress email, follow the recovery link, deactivate the cause, then fix and test before reactivating.1WordPressemail2Recoverylink3Deactivatethe cause4Fix,then testThe fastest way out of a critical errorOpen the WordPress email, follow the recovery link, deactivate the cause, then fix and test before reactivating.1WordPress email2Recovery link3Deactivate the cause4Fix, then test
The WordPress email is often enough to get back in, and it points to the cause.

5 mistakes to avoid

  • Reinstalling WordPress in a hurry

    It does not fix the plugin at fault, and it can overwrite settings or custom work.

  • Deleting plugins at random

    Deactivating is enough. Deleting a plugin can erase its settings and data.

  • Updating everything at once to fix it

    If an update caused the failure, running others muddies the trail. One thing at a time.

  • Neglecting the administrator address

    If nobody reads that mailbox any more, the recovery email gets lost. Check it is up to date, under Settings > General.

  • Leaving technical errors on display

    Showing error messages helps find the cause, but your visitors must never see them: they reveal information about the site.

Your site shows a critical error?

I find the cause, bring the site back online, then fix what caused the failure so it does not come back. And you talk directly to the person who writes the code.

Let’s talk about your website See takeover and maintenance

Reply within one business day

Frequently asked questions

Is my content lost?

Almost never. The error prevents the site from displaying, but pages, articles and orders remain in the database.

I did not receive the WordPress email: why?

It goes to the administrator’s address, which is not always yours. It may also never be sent if the site’s email sending is misconfigured. Remember to check the spam folder. Finally, WordPress only sends it when the failure comes from a plugin or the theme, and at most once a day.

The error only appears in the admin area: is it serious?

The site stays visible to your customers, but you can no longer change anything. It is often a plugin used only in the admin area: fix it quickly.

Should I update PHP?

Yes, because old versions no longer receive security fixes: that is the case for every version before 8.2, and 8.2 itself stops receiving them after 31 December 2026. But first check that your plugins and theme are compatible, ideally on a copy of the site.

My site may have been hacked: is it related?

Most often not: a critical error comes from a code problem. But if you also see unknown pages or redirects, follow my guide on hacked WordPress sites.

How much does a repair cost?

It depends on the cause and the state of the site. I never quote without looking first. Describe the situation: I will send you a clear, itemised quote. Reply within one business day.

Sources

Keep reading