A restore needs both website files and a compatible database backup, plus a plan for what newer data may be lost.
Start with the checks below. Each step explains what to look for and what to try next.
Choose the right recovery point
Confirm the backup date, website domain, file archive and database export. A restore can replace newer posts, orders, form submissions or emails, so identify what must be preserved.
Restore in a controlled sequence
- Create a current backup before overwriting anything.
- Prefer testing on staging first.
- Restore the appropriate website files and database using your backup tool or hosting support workflow.
- Verify database credentials and domain URLs where necessary.
- Test the homepage, admin login, forms and checkout.
Troubleshoot after recovery
Clear caches, regenerate permalinks if appropriate and inspect error logs. Never publish backup archives under a publicly accessible web directory.
Prevent future incidents
Keep periodic off-server backups and test restoration. A backup that has never been restored should not be assumed to work.
Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.