WordPress powers over 40% of the web, and every site that runs it will, sooner or later, break. A white screen an hour before a launch. A cryptic “critical error” email. A site that loads for you but not your client. After six-plus years of fixing WordPress sites for a living, I can tell you the reassuring part: the errors that feel like disasters almost always trace back to a short, familiar list of causes — and each one has a reliable fix.
This is the hub that ties them together. Below is a symptom-based map of the most common WordPress errors, each linking to a complete step-by-step guide. Start with the diagnostic table, jump to your error, and work the fix. Bookmark this page — it’s the one to come back to the next time something breaks.
Quick answer: Most WordPress errors fall into three families — fatal PHP errors (500 error, critical error), database problems (connection failures, corrupted tables), and performance issues (slow site, slow admin). The fastest way to diagnose any of them is to enable the WordPress debug log, which names the exact file and line at fault. Match your symptom in the table below and follow the linked guide.
Diagnose It First: Match Your Symptom
What are you actually seeing on screen? Find the closest match and jump to the fix.
| What you see | Most likely cause | Go to |
|---|---|---|
| “Error establishing a database connection” | Wrong DB credentials, crashed database, or corrupted tables | Database connection error |
| “HTTP ERROR 500” or a blank white page | A fatal PHP error — plugin/theme conflict, .htaccess, or memory | HTTP 500 error |
| “There has been a critical error on this website” | The same family as a 500, with WordPress’s friendlier wording | Critical error |
| Scheduled post stuck on “Missed schedule” | wp-cron didn’t fire — no visitors, caching, or a disabled cron | Missed schedule error |
| Site loads, but slowly for everyone | No caching, heavy images/scripts, or weak hosting | Slow-loading site |
| The site is fine but wp-admin crawls | Heavy plugins, autoload bloat, or an old PHP version | Slow admin |
| Changes you made aren’t showing up | A cache layer is serving an old copy | Clearing the cache |
Not sure which applies, or want the real cause rather than a guess? Skip straight to the diagnostic step every professional starts with, below.
Start Here: Read the Error Log
Before you change a single setting, make WordPress tell you what’s wrong. Enabling the debug log takes three lines in wp-config.php and turns “the site is broken” into “this exact plugin file, on this exact line, is broken.” It’s the first thing I do on every emergency call, and it turns most of the guides below from trial-and-error into a targeted fix.
→ Full guide: How to Find & Read Your WordPress Error Log
Fatal Errors: When the Site Won’t Load at All
These are the heart-stopping ones — the site is completely down. The good news is they’re almost always a plugin or theme conflict, a corrupted .htaccess, or an exhausted memory limit, and the debug log usually names the culprit in seconds.
The 500 Internal Server Error
A generic “something crashed on the server” message that tells you nothing by itself. The fix is a methodical process: read the log, reset .htaccess, raise the PHP memory limit, then isolate plugins and theme one at a time.
→ Full guide: How to Fix HTTP Error 500 in WordPress
“There Has Been a Critical Error on This Website”
WordPress’s modern, gentler wording for the same underlying fatal PHP error — often with a recovery-mode email that links you straight to the offending plugin. Start with that email, then work the same isolation steps.
→ Full guide: How to Fix the WordPress Critical Error
Database Errors: When WordPress Can’t Reach Your Content
Your posts, pages, and orders live in a MySQL database. When WordPress can’t connect to it, you get the infamous “Error establishing a database connection” — and while it looks catastrophic, your data is almost always safe and still sitting there. The usual causes are wrong credentials after a migration, an overloaded database server, or corrupted tables.
→ Full guide: How to Fix “Error Establishing a Database Connection”
Performance Problems: When Slow Feels Broken
A slow site isn’t technically an error, but it costs you more than most errors do — in lost visitors, abandoned carts, and rankings. And because the causes overlap with genuine failures (weak hosting, bloated databases, old PHP), performance belongs in any complete troubleshooting map.
The Whole Site Is Slow
Diagnose before you optimize: five minutes in PageSpeed Insights tells you whether the drag is your server, your assets, or your code — then you fix the right bucket instead of guessing.
→ Full guide: WordPress Site Loading Slowly? How to Diagnose & Fix It
Only the Dashboard Is Slow
When the public site is fine but wp-admin crawls, caching can’t help you — the admin is never cached. This one is about heavy plugins, autoloaded database bloat, the Heartbeat API, and your PHP version.
→ Full guide: Why Is My WordPress Admin So Slow? 12 Fixes
Publishing & Caching Gotchas
Not every problem is a crash. Two of the most common support questions I get aren’t errors at all — they’re WordPress behaving exactly as designed, in a way that surprises you.
Scheduled Posts That Never Publish
The “Missed schedule” error happens because WordPress has no real clock — scheduled publishing depends on visitors triggering wp-cron. The permanent fix is a real server cron job.
→ Full guide: How to Fix the WordPress Missed Schedule Error
Changes That Won’t Show Up
You edited a page, but the old version keeps loading. That’s almost never a bug — it’s one of up to five cache layers serving a saved copy. The fix is knowing which layer, and the right order to clear them in.
→ Full guide: How to Clear Your WordPress Cache the Right Way
The Universal First Moves
Whatever the error, these four habits resolve or de-risk the majority of situations before you even reach for a specific guide:
- Back up first. Files over FTP, database from your hosting panel — both still work even with the site down. Every fix becomes reversible.
- Ask what changed. A new plugin, an update, a migration, a PHP version bump — an error that appeared just after a change is pointing straight at its cause.
- Read the debug log. Three lines in
wp-config.phpturn guesswork into the exact file and line at fault. - Deactivate plugins to isolate. Rename the
pluginsfolder over FTP to disable everything at once; if the site returns, reactivate one at a time to find the culprit.
Frequently Asked Questions
What causes most WordPress errors?
The large majority trace to a short list: plugin and theme conflicts (especially right after an update), exhausted PHP memory, a corrupted .htaccess file, wrong database credentials after a migration, and overloaded or underpowered hosting. Because the list is short, methodical troubleshooting — read the log, isolate plugins, check the server — resolves most errors quickly.
How do I find out what’s causing a WordPress error?
Enable the debug log by adding WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY (false) to wp-config.php, then reproduce the problem and read wp-content/debug.log. Fatal errors are recorded with the exact file and line responsible, which usually names the offending plugin or theme directly.
Will I lose my content when WordPress shows an error?
Almost never. Errors like the 500, the critical error, and the database connection error are failures of connection or code execution, not data loss — your posts, pages, and orders remain in the database. Genuine data loss is rare and is exactly what backups and the built-in database repair tool exist to handle.
Can I fix WordPress errors without a developer?
Most common errors, yes. If you can use FTP or your host’s File Manager and edit wp-config.php, you can work through credential fixes, plugin isolation, .htaccess resets, and cache clearing. A developer becomes worth it when the log points somewhere you can’t interpret, the site is business-critical, or the problem resists the standard steps.
How do I prevent WordPress errors from happening?
Update plugins one at a time and test after each, use a staging site for major changes, run automated off-server backups, keep PHP current, and choose hosting with real headroom. Most recurring errors trace back to batch updates gone wrong or overloaded budget hosting — fixing those two habits prevents the majority.
When to Call in Help
Work the guide that matches your symptom and you’ll resolve the overwhelming majority of WordPress errors yourself, usually within the hour. But some situations are worth handing over: a business-critical site losing money by the minute, an error the log points at but you can’t interpret, or a problem that survives every standard step and hints at something deeper in the server or the code.
That’s the work I do every week — emergency fixes, and making sure the error doesn’t come back. Get in touch and I’ll take a look.
Shahbaz Ali is a senior WordPress developer with 6+ years of agency experience, specializing in WordPress development, speed optimization, and emergency fixes.