Business Tech & Tools
How do I restore a WordPress website from a backup when something breaks?
The short answer
First preserve the broken site and any new customer data, then choose a backup from before the failure and restore it into a safe test location when possible. A complete WordPress recovery may require both files and the database. After restoration, test the cause of the incident and every critical customer function.
Do not automatically overwrite the live site with yesterday’s copy. You may erase orders, form entries, users, bookings, or content created since that backup.
Decide what kind of restore you need
| Problem | Possible recovery scope |
|---|---|
| One page was edited incorrectly | WordPress revision or page-level restore |
| One plugin update broke the layout | Plugin rollback, replacement, or file restore |
| Media files were deleted | Uploads-directory or file-level restore |
| Database is damaged | Database restore, possibly with file-version matching |
| Site was hacked | Incident response and clean recovery, not simply restoring and reopening |
| Whole hosting account failed | Full files, database, configuration, DNS, and service recovery |
Use the smallest safe recovery that fixes the problem and preserves good new data.
Protect evidence and current data first
Before changing the broken site:
- record the time and exact symptom.
- take screenshots and save error messages.
- note the last known good time.
- list changes made since then.
- preserve recent orders, leads, users, or content if accessible.
- create a snapshot of the current broken state when safe.
The broken copy may contain the logs or files needed to understand what happened. It may also contain valid data newer than the backup.
Verify the backup before relying on it
Confirm the archive date, database date, included files, site URL, and whether it completed successfully. Make sure encrypted backups can be opened and that you have the credentials and instructions needed.
WordPress’s backup handbook describes a typical restoration order of restoring files first and then the database, with wp-config.php updated if database credentials changed. Your host or backup product may automate this differently, so follow its current instructions. See WordPress’s backup and restore documentation.
Restore into staging when possible
A safe test restore answers four questions:
- Does the backup actually open?
- Does it contain the missing content or working code?
- Does the original problem disappear?
- What newer live data would be lost if this version replaced production?
Disable real payments, email, fulfillment, and webhooks in the test copy. Keep it private and clearly labeled.
Use a live recovery checklist
When a production restore is necessary:
- Put the site into an appropriate maintenance or transaction pause if needed.
- Preserve new data created after the backup.
- Confirm the restore point and rollback plan.
- Restore the required files and database using the provider’s documented process.
- Clear only the relevant caches.
- Verify the domain, HTTPS, and site URL.
- Test login, forms, email, checkout, access, booking, and scheduled tasks.
- Reconcile saved post-backup transactions or content carefully.
- Monitor logs and customer reports.
- document the cause and prevention step.
If the incident may involve malware or stolen credentials, restoring an older copy does not prove the threat is gone. Use qualified security help, rotate affected credentials, and identify the entry point before reopening sensitive functions.
Learn from the restore
After the site is stable, record how long recovery took, which data was lost or manually reconciled, whether the backup contained everything, and which step was confusing. Improve retention, offsite storage, alerts, documentation, or testing accordingly.
A recovery plan should get easier each time you rehearse it.
Sources and further reading
A free next step
You don't have to build this alone
Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.
Related Questions
- When should I use a WordPress staging site instead of making changes on the live site?
- How often should I back up a website, and where should backups be stored?
- Why am I getting a 404 error for a WordPress page that exists?
- How do I find and fix broken links without checking every page manually?
Related WAHMN resource
If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.