Find and fix WordPress errors before your visitors do
Lion Debug Tools reads WordPress' own debug log and scans your site for common problems, giving you a plain-English overview instead of a raw PHP error log.
WordPress only writes detailed error logs when debug logging is turned on. If the Debug Log page shows no data, add these lines to your site's wp-config.php (above the "That's all, stop editing!" line):
define('WP_DEBUG', true);define('WP_DEBUG_LOG', true);define('WP_DEBUG_DISPLAY', false); - keeps errors out of visitors' view while still logging themOnce enabled, the Debug Log page shows real PHP notices, warnings, and fatal errors as they happen, and lets you clear the log with one click.
The Debug Scan page actively checks your site for common issues - broken plugin/theme files, PHP version compatibility problems, misconfigured permissions, and known problematic patterns - and reports them with a plain explanation of what to fix.
The Health Check page gives a broader snapshot of your WordPress environment: PHP version, memory limits, active plugin count, and other server-level details that commonly cause hard-to-diagnose issues.
The Debug Report page compiles everything - recent log entries, scan results, and environment info - into a single shareable report, useful when asking for support help from a developer or hosting provider.
Yes. Every feature - the debug log viewer, scanner, health check, and reports - is unlocked with no license required.
No - as long as WP_DEBUG_DISPLAY is set to false, errors are only written to the log file and never shown on the live site.
No - logging only writes to a file when an actual error occurs, so it has no measurable impact on normal page load times.
Yes - the Debug Log page has a one-click button to clear the log file so you can start monitoring fresh.