When a WordPress site breaks, the symptoms can vary widely. You might see a blank page, lose access to the dashboard, encounter a server error, or discover that WooCommerce orders are no longer completing. The most reliable response is not to change several settings at once. Instead, work through the problem methodically: identify what changed, protect the site, and test one possible cause at a time.
This guide covers a practical troubleshooting process for business websites, client projects, and WooCommerce stores. If an issue affects sales, security, or a live production site, you can also hire me as a full-stack WordPress developer to investigate and implement a suitable fix.
Back Up the Site and Describe the Problem Clearly
Before editing files, disabling plugins, or changing database settings, create a current backup of the WordPress files and MySQL database. A usable backup gives you a way to recover if a diagnostic change causes further damage. If you use cPanel, follow this guide to create and restore a WordPress backup.
Then write down exactly what is happening. Include the affected URL, the user role experiencing the problem, when the issue started, and any recent changes, such as plugin or theme updates, PHP changes, a hosting migration, or new custom code. An exact error message is far more useful than “the site is not working.”
Find Out Whether the Issue Is Local or Site-Wide
Open the site in a private browser window and test it from another device or network. This helps distinguish a browser or local cache problem from an issue with WordPress or the server. Record the original behavior before clearing caches, since cached assets can sometimes hide the actual cause.
Check the homepage, a standard post, the login page, the dashboard, and any important form or checkout page. On a WooCommerce site, test product pages, cart updates, checkout, payment confirmation, and stock changes. If only one page fails, investigate its template, shortcode, query, or page-specific plugin settings before treating the problem as a site-wide failure.
Use Safe Testing to Identify Plugin and Theme Conflicts
Plugins and themes are frequent causes of WordPress problems, particularly after an update. A conflict may affect the front end, block editor, REST API, login process, or WooCommerce checkout.
Disable plugins one at a time
If you can access the dashboard, deactivate all plugins and test the failing feature. If it works again, reactivate the plugins individually until the problem returns. The last plugin activated is a strong suspect, but check its compatibility, settings, and error logs before confirming the diagnosis.
When wp-admin is unavailable, rename the wp-content/plugins directory using cPanel File Manager or SFTP. WordPress will treat the plugins as inactive. Rename the directory back after testing, then reactivate the plugins gradually. Do not delete plugin folders during the initial investigation.
For more guidance, read how to choose, install, troubleshoot, and manage WordPress plugins safely.
Test a default theme
Temporarily switch to an available WordPress default theme. If the issue disappears, inspect the active theme’s functions, templates, custom JavaScript, and integration code. Avoid editing a parent theme directly; use a child theme or custom plugin for changes that need to remain after updates.
Investigate Server, PHP, and Database Errors
The error itself often indicates which part of the stack needs attention. A 502 Bad Gateway response may involve PHP-FPM, server limits, or a process failing upstream. Use this practical 502 troubleshooting guide when the server returns that error.
For a database connection error, verify the database credentials, database availability, hosting status, and server limits. Do not change wp-config.php values until you have confirmed the correct database name, username, password, and host. See how to fix a WordPress database connection error.
An “Allowed Memory Size Exhausted” message means a PHP process reached its configured memory limit. Check the hosting PHP settings, but also identify the plugin, import, request, or scheduled task using excessive memory before simply raising the limit. The Allowed Memory Size guide explains the diagnostic steps.
Enable Logging Without Exposing Errors to Visitors
Temporary WordPress debugging can reveal PHP notices, warnings, and fatal errors. In wp-config.php, add these settings before the line stating that WordPress has stopped editing the file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );With display disabled, visitors should not see file paths or other technical details. Reproduce the problem once, then review wp-content/debug.log. Turn debugging off after testing on a public production site. Keep log contents private because they can reveal usernames, paths, queries, and other sensitive information.
Check REST API, Cron, and WooCommerce Processes
The block editor, forms, analytics integrations, and many plugins rely on the REST API. If the editor will not save or a plugin reports an API error, check Site Health, permalinks, authentication, firewall rules, and security plugins. This guide covers fixing “The REST API encountered an error”.
Scheduled tasks can fail without producing an obvious front-end error. WordPress normally relies on site visits for its pseudo-cron system, while busy or low-traffic sites may benefit from a real server cron job. Review scheduled actions and configure a cPanel cron job when appropriate. See how to set up a real WordPress cron job.
For WooCommerce, review the order status, payment gateway logs, stock records, and scheduled actions before making bulk product changes. If inventory is inaccurate, use the WooCommerce stock management troubleshooting guide.
Improve Performance After Functionality Is Restored
Performance work is easier once the original error has been resolved. Measure the slow page first, then examine image sizes, page caching, database queries, plugin loading, external requests, and hosting resource usage. Installing several optimization plugins with overlapping features can introduce new conflicts and make the original problem harder to trace.
For a controlled optimization process, follow this guide to speed up WordPress without breaking the site. If slow requests involve custom code or WooCommerce processes, hire me for WordPress performance and troubleshooting work.
Complete Security Checks Before Closing the Issue
Unexpected administrator accounts, redirects, modified files, unfamiliar content, or injected links may indicate a security incident. Change passwords from trusted devices, preserve a backup for investigation, review administrator accounts, update WordPress and its extensions, and ask your host about access logs and malware scanning.
Avoid overwriting evidence or installing several cleanup plugins without a plan. Identifying the entry point matters because removing visible malware may not prevent reinfection. Hire me to audit and harden your WordPress site when the problem involves compromised files, custom code, or a complex hosting environment.
When to Hire a WordPress Developer
DIY troubleshooting is appropriate for isolated plugin settings and routine maintenance. Bring in a developer when the site is losing orders, the database may need repair, production code must be changed, the site may be compromised, or several systems fail at once. A full-stack developer can trace a request from the browser through WordPress, PHP, MySQL, APIs, cron jobs, and the hosting layer.
If you need a diagnosis tailored to the site rather than a general checklist, contact me to hire a full-stack WordPress developer. Include the error message, affected URL, recent changes, hosting details, and steps already tested.
Frequently Asked Questions
What should I check first when a WordPress site breaks?
Create a backup, record the exact error, test the site privately, and identify recent changes. Avoid deleting plugins or restoring an old backup before understanding what changed.
Can I disable plugins if I cannot access wp-admin?
Yes. Rename the plugins directory through cPanel File Manager or SFTP, test the site, and restore the original directory name afterward. Reactivate plugins individually to locate the conflict.
Should WordPress debugging remain enabled?
No. Debug logging is useful during controlled testing, but error display should remain disabled for visitors. Turn debugging off after the investigation is complete.
When might a WordPress error indicate a security problem?
Unexpected redirects, unknown administrator accounts, altered files, injected links, and unexplained login activity are warning signs. Preserve evidence and seek professional help before making extensive changes.
Conclusion
Effective WordPress troubleshooting follows a clear sequence: back up the site, reproduce the problem, isolate plugins and themes, inspect logs, check the database and server, and test the complete user journey before considering the issue resolved. When revenue, security, or custom integrations are involved, hire me to diagnose and fix your WordPress site based on its actual hosting environment and codebase.