WordPress Emergency Support: What to Do When Your Site Goes Down

Your WordPress site just went down. Your phone is ringing. A customer is emailing asking why they can't checkout. You have no idea what happened.

This is a WordPress emergency — and how you handle the next 60 minutes matters more than most people realise.

Here's exactly what to do, step by step.

Step 1: Confirm the Site Is Actually Down

Before panicking, confirm the issue is real and not just your browser or local network.

Go to isitdownrightnow.com or downforeveryoneorjustme.com and paste your URL. If it shows as up for everyone else but down for you, the issue is local — clear your cache, try a different browser, or check your internet connection.

If it confirms your site is down for everyone, move to Step 2.

Step 2: Check Your Hosting Provider's Status Page

Most hosting providers have a status page showing real-time outages. Check yours immediately:

• WP Engine: status.wpengine.com

• Kinsta: kinstastatus.com

• SiteGround: status.siteground.com

• Cloudways: status.cloudways.com

If your host is showing an active incident, your site is down because of their infrastructure — not something you did. All you can do is wait and monitor their updates.

If their status page shows all systems normal, the problem is on your site specifically.

Step 3: Try to Access Your WordPress Admin

Go to yoursite.com/wp-admin. Three possible outcomes:

• White screen of death — A PHP error, plugin conflict, or theme issue. Usually caused by a recent update that went wrong.

• Error establishing database connection — Your database credentials are wrong or your database server is down. Check your hosting panel.

• Login page loads but you can't log in — Your credentials may have changed or your site may have been hacked.

Step 4: Check What Changed Recently

Think back — what happened in the last 24–48 hours?

• Did you update a plugin or theme?

• Did you install something new?

• Did your hosting provider migrate your server?

• Did you change any settings?

Most WordPress emergencies are caused by a plugin update conflict. If you updated plugins recently, that's almost certainly the cause.

Step 5: Restore a Backup

If you have a recent backup and can't quickly identify the cause, restoring is often the fastest path to getting back online.

How to restore depends on where your backup lives:

• Hosting panel backup restore (WP Engine, Kinsta, SiteGround all have one-click restore)

• UpdraftPlus or similar backup plugin restore from wp-admin

• Manual FTP restore if you have a full site backup

Critical question: when was your last backup taken? If it was 7 days ago, you'll lose 7 days of content and orders. This is why daily backups matter more than most people realise.

Step 6: Deactivate All Plugins via FTP

If you can't access wp-admin and restoring a backup isn't an option, this is your emergency override.

• Connect to your site via FTP (FileZilla is free)

• Navigate to wp-content/plugins/

• Rename the plugins folder to plugins-disabled

• WordPress will deactivate all plugins automatically

• Try to access wp-admin again

If the site comes back, a plugin was the cause. Rename the folder back to plugins, then reactivate plugins one by one until you find the culprit.

Step 7: Check for Hacking

If restoring and disabling plugins doesn't fix it, check for signs of compromise:

• Unexpected redirects to other sites

• Strange content appearing on pages

• Google Search Console showing a security warning

• Your hosting provider flagging malware

Run a scan using Wordfence (free plugin) or Sucuri SiteCheck (sucuri.net/website-scanner). If malware is found, do not try to clean it yourself — the risk of missing something is too high.

Step 8: Contact Your Hosting Support

If you've worked through Steps 1–7 and still can't resolve it, call or chat your hosting support. Have these details ready:

• When the site went down (approximate time)

• What changed recently

• What error messages you're seeing

• Whether you've already tried restoring a backup

Most quality hosts have 24/7 live chat — use it.

How to Prevent WordPress Emergencies

The steps above will help you recover. But the goal is to avoid getting here in the first place.

• Daily backups — if something goes wrong, your worst case is losing one day of data, not a week.

• Staging before updates — every plugin update should be tested on a staging copy of your site before going live. One plugin conflict can take down a WooCommerce store during a peak sales period.

• Uptime monitoring — you shouldn't find out your site is down when a customer tells you. Uptime monitoring alerts you within minutes of downtime so you can act immediately.

• Security hardening — regular malware scans, login protection, and firewall rules significantly reduce the risk of a hack taking your site offline.

Sites on a WordPress care plan get all of this automatically — daily backups, staged updates, uptime monitoring, and security hardening included from $49/month. If your site going down costs you more than $49 in lost revenue or stress, a care plan pays for itself the first time it prevents an emergency.

What WPOPS Does When a Client Site Goes Down

Every WPOPS client has uptime monitoring running 24/7. When a site goes down, we get the alert before you do.

Our response process:

• Immediate triage — identify whether it's hosting, plugin, theme, or security

• Restore from the most recent daily backup if needed

• Fix the root cause — not just the symptom

• Post-incident report — what happened, what we fixed, how we've prevented it recurring

Emergency support is included on all plans. No extra fees, no "that's outside your plan" conversations. View WPOPS plans from $49/month →

Frequently Asked Questions

What is WordPress emergency support?

WordPress emergency support covers urgent issues that take your site offline or significantly impact its function — including site downtime, hacking, plugin conflicts, white screen of death, and database errors. Quality WordPress care plans include emergency support as standard.

How long does it take to fix a WordPress site that's down?

It depends on the cause. A plugin conflict can be resolved in minutes by deactivating plugins. A hack cleanup takes 2–4 hours for a thorough job. A full site restore from backup typically takes 30–60 minutes depending on site size.

What causes most WordPress sites to go down?

The most common causes are plugin update conflicts (most common), hosting server outages, hacking or malware, PHP version incompatibilities after a host upgrade, and database connection errors.

Do I need emergency support on my WordPress care plan?

Yes — if your site going down would cost you money, stress, or lost customers, emergency support should be included in your plan. WPOPS includes emergency support on all plans from $49/month.

What's the difference between WordPress maintenance and emergency support?

Maintenance is proactive — regular updates, backups, monitoring, and security. Emergency support is reactive — fixing things when they break. The best WordPress care plans include both.

How can I prevent my WordPress site from going down?

Daily backups, staging verification before updates, uptime monitoring, and security hardening are the four essentials. Sites managed by WPOPS have all four included from $49/month.