WordPress has a particularly cheerful way of telling you something has gone wrong: “There has been a critical error on this website.”
It sounds terminal, but it usually is not. A critical error generally means WordPress has encountered a fatal PHP error and cannot continue loading the page normally. Your website and its content are still there. Something inside the site has simply stopped WordPress from completing the request.
Check the administrator email first
When WordPress catches certain fatal errors, it can send a message to the site’s administrator. That email may identify the plugin or theme involved and can include a special Recovery Mode link.
Recovery Mode temporarily pauses the problematic component for your administrator session, giving you a chance to access WordPress and investigate without necessarily having to work directly with server files.
If the error appeared immediately after updating a plugin, updating WordPress, installing a theme, changing PHP version or adding custom code, make a note of it. Knowing exactly what happened immediately before the problem appeared can save a lot of time.
If you can access the error logs, have a look
Hosting error logs often show the fatal error that triggered WordPress’s critical error message. A file path may point towards a plugin, theme or piece of custom functionality involved.
That does not always mean the named component is solely responsible. Compatibility issues can involve several different pieces of the site. Still, it gives you somewhere sensible to start.
If you clearly identify a non-essential plugin as the problem, disabling it may get the website back online temporarily. Context is important though. Disabling a visual effect plugin is one thing. Disabling WooCommerce, your booking system or your membership platform could remove a major part of the website.
If both the website and WordPress admin are inaccessible, investigation can still continue through the hosting environment, SFTP or server-level tools. If those are not familiar territory, you do not need to learn server administration while your live website is offline.
Try not to turn one error into several
Critical errors understandably cause a bit of panic, but this is not the moment to update everything else, delete several plugins, install a collection of repair tools and restore an old backup all at once.
One controlled change gives you information. Ten simultaneous changes make the original cause much harder to identify.
Need a company to help you now?
If you need somebody to make sense of the error, send us the website address and whatever information you have, even if that is simply a screenshot. We can take a look, work out the likely cause and explain what we would do next.
