Emergency WordPress Repair for Broken or Offline Sites

When WordPress is offline, throwing server errors or returning a blank page, the goal is to restore service without losing the ability to go back. The same visible outage can come from very different causes, so the safe path is to read the evidence before disabling or replacing anything.

Step 1 — Classify the outage

What exactly do you see? A 500 or 502, a database-connection error, a critical-error screen, a blank page, or a hosting suspension notice each lead down a different path. Note the exact message, the time it started, and whether it hits the whole site or one route. Check whether /wp-admin/ still loads — a working admin narrows the problem dramatically.

Step 2 — Read the logs before touching files

Enable logging in wp-config.php (WP_DEBUG_LOG on, WP_DEBUG_DISPLAY off) and read /wp-content/debug.log, plus your host’s PHP and server error logs. The log usually names a file and line, reports exhausted memory, or shows a timeout — which is far more reliable than guessing from the visible symptom.

Step 3 — The standard isolation sequence

1. Plugins: rename /wp-content/plugins to plugins_off over SFTP. If the site returns, re-enable one by one to find the culprit.
2. Theme: rename the active theme’s folder so WordPress falls back to a default theme.
3. .htaccess (Apache): rename it to .htaccess_old and reload; if that fixes a 500, regenerate clean rules by re-saving permalinks rather than leaving the site without them.
4. Core files: reinstall WordPress core over itself — it replaces core files without touching your content — if the log points at missing or corrupt core files.

Step 4 — When it is infrastructure, not WordPress

If every site on the server is down, or the host’s status page shows an incident, the fastest route is the provider — not your files. A database-connection error across all sites, a disk-quota message, or a suspended account are infrastructure problems that no amount of plugin renaming will fix.

Preserve first, always

Back up the current broken state before you change anything. If there is no recent backup, that is the single most important thing to fix once service is restored.

When to escalate

Call a specialist if the outage touches a store, there is no viable backup, the logs point at core or database corruption, or the site is also behaving strangely (redirects, unknown users) which suggests a compromise. Send the exact error, the start time and the recent changes and the incident can be assessed before any access is granted.