This guide is for business owners and marketing leads who need a clear sequence before developers arrive. Follow the steps in order. Skip nothing in the first block even if you plan to call for help.
step 1: confirm what is actually down
Check four URLs in an incognito browser: homepage, a inner page, wp-admin login, and checkout or lead form if you run eCommerce. Note the exact error: white screen, 500 Internal Server Error, 502 Bad Gateway, maintenance page, or SSL warning.
Ask a colleague in another network (mobile data works) to load the same URLs. If it works for them but not you, suspect DNS cache or local ISP issues before deeper changes.
If a plugin update matches the outage start time, roll back that plugin first via FTP or host file manager by renaming its folder to plugin-name.
step 2: check hosting and DNS before WordPress
Log into your hosting panel (Cloudways, WP Engine, SiteGround, Kinsta, AWS, etc.). Confirm server status, disk usage, and database connectivity. Many outages are disk-full, expired SSL, or database connection limits, not WordPress core.
Run a DNS lookup on your domain. The A record should point to your production server IP. A wrong record after a migration is a common post-launch failure.
step 3: read error logs, not forums
Enable or locate PHP error logs. On many hosts: wp-content/debug.log when WP_DEBUG_LOG is true, or the host error log viewer. Look for fatal errors naming a plugin file or theme function. Copy the last 20 lines before changing anything.
For WooCommerce checkout failures, also check WooCommerce → Status → Logs. Payment gateway timeouts show up here even when the homepage still loads.
Common HTTP errors and what they usually mean on WordPress.
| Code | What visitors see | First check |
|---|---|---|
| 500 | Generic server error | PHP fatal error in plugin or theme |
| 502 / 503 | Bad gateway / unavailable | Hosting overload, PHP-FPM crash, deploy in progress |
| 404 sitewide | Page not found everywhere | Permalink flush, wrong document root, staging DNS |
| SSL warning | Browser blocks site | Expired certificate, mixed content after migration |
| White screen | Blank page | PHP memory limit or fatal error with display off |
step 4: rollback recent changes safely
List changes in the last 24 hours: plugin updates, theme edits, code deploy, marketing pixel, DNS or SSL change. If a plugin update matches the outage start time, roll back that plugin first via FTP or host file manager by renaming its folder to plugin-name.disabled.
Do not update more plugins while the site is down. Stabilize, then schedule updates on staging. If you use a deployment pipeline, check whether the last build introduced a bad environment variable or missing extension.
Site down right now?
Talk to us →what downtime costs while you wait
Downtime math is simple and painful. If your site converts 2% of 10,000 daily visitors at $50 average order value, one full day offline costs roughly $10,000 in lost revenue, plus ad spend still running to a broken page.
Google research and multiple retail studies cite conversion dropping roughly 7% for each additional second of load time on commerce flows. A hard outage is worse than slow: every second is a 100% loss for affected journeys.
What nobody tells you: partial outages hurt more than full outages because analytics still shows traffic while revenue quietly stops. Always test checkout, not only the homepage.
when to stop DIY and call for help
Call for emergency support if checkout or payment is broken during active campaigns, if you see signs of compromise (unknown admin users, defaced pages), if the database will not connect and the host confirms infrastructure is healthy, or if rollback attempts fail after two controlled tries.
When you call, send: live URL, error screenshot, when it started (with timezone), recent changes, hosting provider, and whether wp-admin loads. That short list cuts triage time in half.
your first-30-minutes checklist
- Confirm front, admin, and checkout status from two networks.
- Check hosting panel for server, disk, and database health.
- Capture PHP and WooCommerce error log excerpts.
- List changes in the last 24 hours.
- Roll back one suspect plugin or deploy at a time.
- Pause paid traffic to broken URLs if checkout is down.
- Document timeline for post-incident review.
what professional recovery looks like
This takes specific expertise. Here is what it looks like when we do it: we stabilize revenue paths first (checkout, forms, APIs), then isolate root cause with correlated logs, then apply a documented fix with rollback ready. You get a short written summary of cause, fix, and what to monitor so the same failure does not repeat quietly.
If you are past the 30-minute window and still offline, emergency website support is the fastest path. For prevention after recovery, a maintenance plan adds monitoring, update discipline, and response SLAs.
