The WordPress message “There has been a critical error on this website” means a PHP error stopped WordPress from completing the page request. The website may be completely unavailable, or the error may affect only the dashboard, one page, or a specific feature.
The most common causes are a failed plugin update, incompatible theme code, an unsupported PHP version, exhausted memory, or damaged WordPress files. Follow these steps in order and create a backup before changing files whenever possible.
1. Check the WordPress Recovery Mode Email
WordPress may send an automated email to the site administrator when it detects a fatal error. The subject usually says that the site is experiencing a technical issue.
The email may identify the plugin or theme causing the problem and include a special Recovery Mode login link. Check the administrator inbox and spam folder before editing website files.
Recovery Mode temporarily pauses the broken component for your administrator session so you can log in and investigate. It does not permanently repair the underlying problem.
2. Check What Changed Immediately Before the Error
Start with the most recent change. Common triggers include:
- Updating or installing a plugin
- Updating or switching themes
- Changing the PHP version
- Adding custom PHP through WPCode or functions.php
- Running a WordPress core update
- Migrating or restoring the website
If the error appeared immediately after one of these actions, reverse that specific change first.
3. Disable the Suspected Plugin
If you can access the WordPress dashboard, deactivate the plugin associated with the error. If the dashboard is unavailable, use your hosting file manager, SFTP, or FTP.
- Open the
wp-content/pluginsdirectory. - Find the suspected plugin folder.
- Rename it by adding
-disabledto the folder name. - Reload the website.
If you do not know which plugin caused the error, rename the entire plugins directory to plugins-disabled. If the website loads, restore the original folder name and activate plugins individually until the error returns.
Do not leave every plugin disabled longer than necessary. Security, forms, caching, redirects, and other important functions may depend on them.
4. Temporarily Switch the Theme
A theme or child theme can trigger a critical error after a code change, update, or PHP upgrade.
If you cannot access the dashboard, open wp-content/themes and rename the active theme folder. WordPress may switch to an installed default theme automatically.
Confirm that a default WordPress theme is installed before renaming the active theme. You can also review which WordPress themes to keep or delete.
5. Review the WordPress Debug Log
The debug log can identify the exact file, plugin, theme, or function that failed. Add these lines to wp-config.php above the line that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the broken page, then check:
/wp-content/debug.logLook at the newest fatal error and note its file path. That path often identifies the responsible plugin or theme.
The official WordPress debugging documentation explains these settings in more detail. Disable debugging and remove any publicly accessible log after troubleshooting.
6. Check the PHP Version and Memory Limit
A plugin or theme may require a newer PHP version, while older code may fail after a PHP upgrade. Check the requirements of the affected software before changing versions.
A fatal error containing “Allowed memory size exhausted” indicates a memory problem. Increasing the limit may restore the site temporarily, but you should still identify what exhausted the available memory.
7. Restore Clean WordPress Core Files
If an interrupted update damaged WordPress core files, download a clean copy of WordPress and replace the core files without replacing wp-content or wp-config.php.
Create a backup first. If you are unsure which files are safe to replace, ask your hosting provider or developer to complete this step.
8. Restore a Recent Working Backup
If the cause is unclear and the website must be restored quickly, use a backup created before the error appeared. Confirm that the backup includes both the files and database.
After restoring it, determine what caused the failure before repeating the update or code change.
Can a WordPress Critical Error Affect SEO?
Yes. Search engines and visitors may receive an error page or 500 response while the site is unavailable. A brief incident is unlikely to cause lasting ranking damage, but recurring or extended downtime can interfere with crawling, indexing, conversions, and user trust.
After recovery, test important URLs and review Google Search Console for new server errors.
Preventing Future Critical Errors
- Maintain automatic daily backups.
- Test major updates on staging first.
- Remove abandoned plugins and themes.
- Keep a record of code and configuration changes.
- Confirm PHP compatibility before upgrading.
- Use ongoing WordPress website maintenance.
Need Help Fixing a WordPress Critical Error?
If your website is unavailable and you are not comfortable editing files or reading PHP logs, stop before making additional changes.
