What to Do When Your WordPress Site Breaks
A calm emergency plan for downtime, white screens, broken checkout, missing forms, malware warnings, and urgent customer impact.
/ Direct answer
When a WordPress site breaks, protect evidence, identify customer impact, avoid random live changes, check recent updates, restore if needed, and move investigation to staging once the business is stable.
First five minutes
The first job is to understand the business impact.
- Is the whole site down or one path broken?
- Are customers blocked from paying, booking, logging in, or submitting forms?
- What changed recently: updates, plugins, content, hosting, DNS, payments?
- Do you have a fresh backup and staging access?
Stabilize before investigating deeply
If customers are blocked, restoring service matters more than perfect diagnosis. Use a backup, rollback, or temporary workaround when that is the safest business move.
After the fire is out
Once the site is stable, document the cause, update the maintenance process, and add monitoring or testing so the same issue is caught earlier next time.
Frequently asked questions
Should I update plugins during an emergency?
Only if evidence points to that fix. Random live updates can make recovery harder.
What is the safest emergency fallback?
A recent tested backup and a support team that can restore quickly.
Quick answer summary
/ Short answer
When a WordPress site breaks, protect evidence, identify customer impact, avoid random live changes, check recent updates, restore if needed, and move investigation to staging once the business is stable.
/ What matters most
- First decide whether customers are blocked right now.
- Do not make random changes on the live site.
- Restore service first, then diagnose the root cause.
/ Best next step
Match the support level to the real customer impact: leads, sales, bookings, logins, security, recovery, and trust. If the site creates money or customer confidence, choose ongoing care over occasional fixes.