When a WordPress site misbehaves, the usual reflex is to deactivate every plugin to find the culprit. On a live site, that is risky: meanwhile, visitors see a broken site, forms stop working and a shop stops selling. The Health Check & Troubleshooting plugin, maintained by the WordPress team, solves exactly that problem.
Site health, already built into WordPress
Part of the tool has been built into WordPress core since version 5.2, under Tools then Site Health. The Status tab lists critical issues and recommended improvements: outdated PHP version, late scheduled tasks, inactive plugins to remove, failing HTTPS requests. The Info tab gathers the whole server configuration, and a button lets you copy it to send to a developer.
Troubleshooting mode: test without breaking anything
This is the real reason to install the plugin. Troubleshooting mode deactivates every plugin and switches to a default theme, but only for your session. Visitors keep seeing the normal site. You then reactivate plugins one by one from the admin bar until the problem comes back: the last plugin reactivated is the culprit.
- Install and activate Health Check & Troubleshooting.
- In Site Health, open the Troubleshooting tab and enable troubleshooting mode.
- Check that the problem has gone, then reactivate plugins one by one from the Troubleshooting Mode menu in the admin bar.
- When the problem comes back, note the plugin, then disable troubleshooting mode.
The mode relies on a small file placed in the mu-plugins folder and on a cookie specific to your browser. Remember to disable it at the end of the session, and note that a very aggressive page cache can sometimes serve you the normal version of the site during the test.
The plugin's other tools
The Tools tab adds a file integrity check, which compares core files with those from wordpress.org and flags any change, useful after a hack. An email test also tells you whether the server can send messages, which often explains silent contact forms.
What the plugin does not do
Health Check points to a conflicting plugin, it does not fix the conflict. You then have to update the plugin, contact its developer or replace it. Nor does it detect fine performance issues or intermittent PHP errors: for those, the error log and Query Monitor remain essential.
Frequently asked questions
Can it be used on a live site?
Yes, that is precisely the point. Troubleshooting mode only affects the administrator who enables it. A backup beforehand remains a good habit.
Should the plugin stay active?
It does not slow the site down, but you can deactivate it between diagnoses. The site health report stays available without it.
Author
Walid SadfiWalid Sadfi is the founder of Evolurise, a team of engineers deployed on site with its clients: custom development (WordPress, Drupal, React, Laravel), AI agents, DevOps and team training. With 8 years of experience, he supports SMEs and large companies, from understanding the problem to deploying the solution. On this blog he shares practical, field-tested insights.