source on Google
A website backup turns a disaster into an afternoon of restoring. Without one, a failed update or a hacked login can mean losing the whole business. This guide covers what to back up, how often, where to store copies and the security habits that help prevent the problem.
\n\n
\n\n
What a website backup must contain
\n
A complete website backup has two parts. The first is the files: your theme, plugins, uploads and custom code. The second is the database, which holds pages, posts, products, orders and settings.
\n
A copy of only one part cannot restore a working site. Check that your tool includes both. The WordPress documentation on backups explains each part in detail.
\n\n
How often to run a website backup
\n
- \n
- A brochure site that changes a few times a year can back up weekly.
- A blog that publishes often should back up daily.
- A store taking orders should back up daily, and before every update.
\n
\n
\n
\n
Always make a fresh copy before you update WordPress, a theme or a plugin. That one habit prevents most update problems.
\n\n
Store every website backup in two places
\n
A copy kept only on the same server is not a real safeguard. If the server fails or the account is compromised, the copy goes too. Keep at least one copy in a separate account, and keep a few older versions so you can roll back before a problem started.
\n\n
Test that a website backup restores
\n
A backup you have never restored is a hope, not a plan. Once a quarter, restore a copy to a test site and check that pages, forms and settings work. This shows you the real steps before an emergency.
\n\n
Security habits that protect your site
\n
- \n
- Keep WordPress, themes and plugins updated, and remove any you no longer use.
- Use a strong, unique password for every admin account, with two-factor sign-in where available.
- Limit failed login attempts so bots cannot guess passwords.
- Give each user only the access they need, and remove accounts for people who have left.
- Download plugins only from trusted sources.
\n
\n
\n
\n
\n
\n\n
Signs your website may have been hacked
\n
Watch for unexpected admin users, pages or links you did not add, slow pages with no clear cause, or search results showing strange text for your site. If you see these, take the site offline, restore a clean copy, change all passwords and find the entry point before reopening. Our malware glossary entry explains the common types.
\n\n
Check your website backup setup this week
\n
- \n
- Confirm backups run automatically and include files and the database.
- Find out where the copies are stored, and whether one is off the server.
- Restore one copy to a test environment this month.
- Review admin users and remove anyone who should not have access.
\n
\n
\n
\n
\n
If you would rather not manage this yourself, our maintenance plans include updates, backups and security checks from $25 a month.
\n\n
Checks to run after a website backup restore
\n
A restore is not finished until the site works end to end. After you restore a copy, check the contact form and confirm that notification emails arrive. Test a checkout if you sell online, confirm the security certificate is valid and check that the homepage and main service pages load correctly.
\n
Write these checks down once, so the next restore follows the same steps. A short written checklist saves time during a stressful incident.
\n\n
Mistakes that make a website backup useless
\n
- \n
- Backing up only the files and forgetting the database
- Storing every copy on the same hosting account
- Never checking that the copies open or restore
- Letting old backups delete before new ones are saved
\n
\n
\n
\n
\n
Each of these mistakes is easy to avoid once you know to look for it.
\n\n
Frequently asked questions
\n
How often should I make a website backup?
\n
A brochure site that changes rarely can back up weekly. A blog should back up daily, and a store taking orders should back up daily and before every update.
\n
Should a website backup include the database?
\n
Yes. A website backup needs both the files and the database. Files alone cannot restore pages, orders or settings.
\n
Where should I store a website backup?
\n
Store at least one copy in a separate account, away from the server that hosts your site. Keep a few older versions so you can roll back before a problem started.
\n\n
Ready to plan your next step?
\n
If you want a clear plan for your site, our team can review your current setup and suggest the next steps. Request a free proposal and we reply within 24 hours.