Let’s cut the fluff. If your WordPress site is down right now, you don’t need a lecture about best practices—you need to know how to repair WordPress fast, without breaking what’s left. I’ve been through this more times than I care to admit, and the truth is that most «broken WordPress» situations fall into a handful of predictable buckets. Once you identify which bucket you’re in, the fix is usually 20 minutes of work, not a weekend of panic.
The first thing I do when WordPress is broken is check whether I can still log into wp-admin. If I can’t, the problem is almost always PHP, the database, or a fatal plugin error. If I can, the issue is likely a theme conflict or a misconfigured setting. That single distinction saves me hours every time.
Fix broken themes and plugins without losing your mind
Plugins cause the vast majority of WordPress problems. A single badly coded plugin can white-screen your entire site, tank your database, or expose you to malware. The tricky part is that the plugin causing the damage isn’t always the one you suspect.
Here’s the method that actually works: rename the plugins folder via FTP or your hosting file manager. That instantly deactivates every plugin at once. If your site comes back, you know a plugin is the culprit. Then rename the folder back and deactivate plugins one by one until the site breaks again. The last one you turned off is your problem child.
For themes, switch to a default theme like Twenty Twenty-Four by renaming your active theme folder. If the site loads, your theme is the issue—likely a PHP compatibility error after a WordPress update. Don’t just reinstall blindly; check the theme’s changelog and the developer’s support forum first. Half the time there’s a known bug with a patch already released.
When updating a plugin breaks your site
Roll back to the previous version using a plugin like WP Rollback. Then update WordPress core first, and only then update the plugin. Order matters far more than most tutorials admit.
Repair the WordPress database: the silent killer
If you’re seeing Error establishing a database connection or your site loads but pages are blank, your database is probably the problem. This is the most common symptom of a corrupted wp_options or wp_posts table.
Log into phpMyAdmin through your hosting panel. Select your WordPress database, select all tables, and choose «Check» from the dropdown. If any table shows as corrupted, select it and hit «Repair.» This fixes most database errors in under a minute.
If phpMyAdmin isn’t enough, SSH into your server and run wp db check followed by wp db repair using WP-CLI. These commands dig deeper than the GUI and often repair tables that phpMyAdmin can’t touch. I’ve recovered sites this way that hosting support told me were unsalvageable.
One more thing: verify your wp-config.php credentials. A single wrong character in the database name or password will throw the same connection error, and no amount of table repair will help. It sounds dumb, but I’ve seen it happen after a hosting migration.
Remove malware and infections before they spread
If Google is flagging your site or your hosting provider sent a malware warning, act fast. The longer you wait, the more your SEO and reputation suffer.
Start by changing every password: WordPress admin, hosting, FTP, database. Then update every plugin, theme, and WordPress core to the latest version. Old software is how attackers get in most of the time.
Install Wordfence or Sucuri and run a full scan. These tools catch backdoors that manual inspection misses. Then manually check your wp-content/uploads, wp-includes, and wp-content/plugins folders for suspicious PHP files—usually with random names or obfuscated code at the top.
If you don’t have a clean backup from before the infection, restoring is your only safe reset. Cleaning malware manually without a backup is risky because you can’t be 100% sure you removed every backdoor.
Troubleshoot 404 and 500 errors the right way
A 404 error means WordPress can’t find a page or file. Nine times out of ten it’s a broken permalink structure after a migration or a plugin conflict with your .htaccess file. Go to Settings > Permalinks and click Save Changes without modifying anything—this regenerates the rewrite rules and fixes most 404s instantly.
A 500 internal server error is scarier but equally fixable. It’s usually a PHP fatal error, a corrupted .htaccess, or a plugin conflict. Rename your .htaccess file to .htaccess.bak and reload the site. If it comes back, regenerate a fresh .htaccess through Settings > Permalinks. If that doesn’t work, increase your PHP memory limit in wp-config.php to 256M or 512M—many hosts default too low for modern plugins.
Check your PHP version compatibility
After a hosting PHP update, old plugins often throw fatal errors. Check your PHP version in your hosting panel and temporarily downgrade if needed, then update your plugins to versions that support the new PHP. This is the single m
