WordPress Troubleshooting Tool
Select the problem you can see to get suggested checks and next steps. This tool does not scan, access or change your website. Back up before making changes.
What this WordPress troubleshooter can help you do
A WordPress troubleshooting tool helps you narrow a problem by asking about the symptoms you can observe. This guided tool covers blank pages, database connection errors, server errors, login trouble and slow loading. Its suggestions are starting points, not a confirmed diagnosis: it does not inspect your files, logs or hosting account.
Record the error message and the last change made before the problem began. A recent plugin update, migration or configuration change can help you decide which check to try first. If the site handles orders or important submissions, involve your host before making changes you cannot confidently reverse.
Start with these checks
- Check whether the issue affects one page, the whole site or only the administration area.
- Note when it started and whether it followed an update or hosting change.
- Confirm that a usable backup and recovery route are available.
- Follow one relevant check at a time, recording the result.
- Stop when the instructions do not match your server or level of access.
The official WordPress error handbook provides further explanations. Your hosting provider can inspect server-side logs and service failures that this tool cannot see.
Match the symptom to the next investigation
| Symptom | Useful next investigation |
|---|---|
| Blank page or critical error | Recent changes, recovery access and the relevant PHP error log |
| Database connection error | Database availability and configuration after a migration or credential change |
| 500 server error | Server logs and configuration appropriate to that hosting stack |
| Login problem | The exact login message, account recovery route and recent security changes |
| Slow site | A measured performance report, recent additions and hosting resource information |
Do not buy a new hosting plan solely because a page loads slowly. Start with evidence. Our WordPress caching guide explains caching layers and a sensible setup order. Read what a CDN does before expecting it to fix an application error or an overloaded database.
Problems after moving hosts
A migration can introduce more than one symptom. The site files may be on the new server while the domain still resolves elsewhere, or email settings may not match the new arrangement. Use the DNS record checker to inspect the relevant hostname, then compare the result with the values your provider supplied.
Our WordPress migration checklist covers the broader move. If you are struggling to find the right settings, the cPanel vs hPanel explanation clarifies the control-panel differences.
What to send to hosting support
Provide the affected URL, exact error text, approximate start time, recent changes and the checks already attempted. Share a redacted error excerpt through the provider’s support channel if requested. Do not post passwords, database credentials, security tokens or full private logs in public comments.
Common questions
Does the tool repair my site automatically?
No. It provides a guided set of suggestions. You or your hosting support team decide which steps apply.
Can I use it without wp-admin access?
Yes, you can select the symptom. Some suggested checks require hosting access; contact your host if that access is unavailable.
Will disabling a plugin delete my posts?
Disabling a plugin normally leaves posts in place, but it can change site functionality. Back up and understand what the plugin controls before changing a live site.
When should I stop?
Stop if a step does not match your setup, if you lack a recovery path, or if a business-critical or compromised site needs qualified support.