When WordPress shows “There has been a critical error on this website”, a PHP error stopped the page before it could finish. The site is not necessarily deleted or hacked. The request crashed. Email from WordPress may include a recovery link; the useful detail is almost always in the error log.
This article is a first-pass checklist. Work it in order. If one covered WordPress issue is clearly to blame and you want help, use the $99 one-time fix after you can authorize access.
What the screen actually means
- A PHP error stopped WordPress from finishing the page.
- WordPress shows a general error message rather than the technical details.
- Admin may still work, or it may fail the same way. Try both
/wp-admin and the homepage.
A critical error is different from a full host outage. If every site on the server is unreachable, start with the host. A failure affecting only one site can still involve hosting resources or configuration. Ask your host to check if the WordPress logs do not explain it.
Read the recovery email and the log
- If a recovery email arrived, check that its link points to your site's domain before opening it. Keep the link private. Recovery Mode can pause the faulty plugin or theme for your admin session; it does not by itself repair the public site.
- In the host panel or SFTP, open the PHP error log for the same minute the screen appeared. Look for a file path under
wp-content/plugins or wp-content/themes.
- Note the plugin or theme folder name in that path. That is your first suspect, not a random reinstall of WordPress core.
If no error appears in the log, follow your host's instructions to enable private error logging. Keep errors hidden from visitors throughout, reproduce the problem once, and turn temporary debug logging off afterward. Do not share logs publicly; they may contain sensitive information.
Isolate plugins and the theme safely
If the dashboard or Recovery Mode loads, start by deactivating the plugin identified in the error notice. Check the public site separately after the change.
Use a staging copy when possible. Before changing the live site, take a backup and record which plugins are active. Disabling plugins can stop checkout, forms, bookings, and other features.
If you cannot reach the dashboard, use SFTP or your host's file manager:
- If the error log identifies a plugin, temporarily rename that plugin's folder under
wp-content/plugins and retest.
- If you need to test all regular plugins, temporarily rename
wp-content/plugins to plugins-off, then visit /wp-admin/plugins.php so WordPress marks the missing plugins inactive. Restore the folder name and reactivate the previously active plugins one at a time, checking the site after each. This does not disable must-use plugins or all caching components.
- To test the theme, first confirm a default WordPress theme is installed. Then temporarily rename the active theme's folder under
wp-content/themes and retest. If you are unsure how to restore it, ask your host for help.
Recent updates and partial upgrades
Critical errors often appear right after a plugin, theme, or PHP version change. Check:
- Whether the host changed the PHP version. Older plugins or themes may be incompatible with the new version.
- Whether an update was interrupted (disk full, timeout, killed process).
- Must-use plugins under
wp-content/mu-plugins. They load even when you disable the normal plugins folder.
If a plugin update broke a site that was fine minutes earlier, see also plugin update broke WordPress site.
When the whole site will not load at all
If you get timeouts, blank responses, or host parking pages with no WordPress critical-error screen, start with the site down / not loading checklist. That checklist helps you check hosting, DNS, certificates, and maintenance mode.
When a $99 one-time fix fits
Request the $99 one-time WordPress fix for help with one clearly defined issue on one WordPress site. Describe the error and the last change you made. We confirm the scope before work begins. Send credentials only through the private access link provided after your request is accepted.
Full rebuilds, new custom features, full migrations, broad security audits, and multiple unrelated issues are outside this offer. If you suspect malware, include that in the request so we can confirm what work is covered.
Related checks
If you cannot identify the cause, ask your host for help and share the error message and when it began. Suspected compromise needs a security investigation as well as restoring the page.