A reliable website backup strategy protects more than your page files. This practical checklist explains what to back up, how often to capture each component, how to store copies safely, and how to test a restore before an outage or failed update turns into a larger business problem.
Overview
A website backup is a recoverable copy of the information and settings needed to restore your site. Depending on your setup, that may include WordPress files, databases, uploaded media, email, DNS records, server configuration, application settings, and customer data.
The right schedule depends on how quickly your content changes and how much data you can afford to lose. A brochure site that changes once a month has different requirements from an ecommerce website that receives orders throughout the day. Rather than choosing a schedule based only on the hosting plan, start with two recovery questions:
- Recovery point objective (RPO): How much recent data could you recreate or accept losing?
- Recovery time objective (RTO): How long can the website or application remain unavailable?
Backups should be automatic where possible, stored separately from the live website, protected from unauthorized changes, and tested regularly. A hosting provider’s backup feature can be useful, but it should not automatically be treated as your only recovery plan. Check what it includes, how long copies are retained, whether you can download them, and how restoration works.
If you are changing infrastructure, review your recovery requirements alongside your hosting choice. The guides on managed WordPress versus cloud hosting and migrating a website to cloud hosting can help frame that decision.
Checklist by scenario
Use this table as a starting point, then adjust the frequency to match your publishing, transaction, and operational workflows.
| What to back up | What it includes | Starting schedule | Important check |
|---|---|---|---|
| WordPress files | Core files, themes, plugins, and uploads | Weekly; more often after frequent changes | Confirm that uploads and custom theme files are included |
| WordPress database | Posts, pages, settings, users, comments, and form records | Daily for active sites; before major changes | Make sure the database copy can be downloaded and restored |
| Media and digital assets | Images, video, documents, product files, and downloads | After additions or on a regular weekly schedule | Open sample files from the backup, not just the backup folder |
| Mailbox messages, contacts, calendars, or provider exports | Based on business importance and provider options | Website backups may not include hosted email | |
| DNS records | A, AAAA, CNAME, MX, TXT, and verification records | Before DNS or hosting changes; review quarterly | Record the purpose of each non-obvious record |
| Configuration files | Environment settings, web server rules, scheduled jobs, and integrations | Before edits and after confirmed changes | Remove or securely protect passwords and API keys |
| Customer and order data | Accounts, orders, submissions, invoices, and related records | As close to real time as practical for active systems | Limit access and define how long copies should be retained |
For a low-change brochure website
Back up files and the database at least before publishing a redesign, updating plugins, changing themes, or modifying server settings. A weekly or monthly recurring copy may be sufficient for a site with little change, provided you also keep a pre-change backup and verify that contact forms still work after restoration.
For WordPress publishing sites
Capture the database more frequently than the files if posts, comments, user accounts, or form submissions change often. Keep a separate copy before WordPress core, theme, or plugin updates. After an update, check the homepage, key templates, forms, login, media library, and any connected services.
For ecommerce and customer-facing applications
Prioritize transaction records and customer data. A backup plan should cover the application database, uploaded assets, configuration, and any external systems needed to process orders or communicate with customers. Coordinate backups with your payment, email, analytics, and inventory workflows rather than assuming all data lives on the web server. For additional infrastructure considerations, see this hosting comparison for ecommerce websites.
What to double-check
Use more than one location
Keep at least one copy separate from the production hosting account. A practical arrangement may include the hosting provider’s backup system, a downloaded or synchronized copy in independent storage, and an offline or otherwise protected archival copy for important sites. Avoid making every copy writable by the same administrator account.
Review retention, not just frequency
Daily backups with only a short retention period may not help if a problem goes unnoticed. Consider a rolling schedule that includes recent daily copies, older weekly copies, and periodic monthly or milestone copies. Retain copies long enough to cover delayed discovery of broken content, compromised accounts, or accidental deletion, while respecting your data-handling requirements.
Test restoration in a safe environment
A successful backup job only proves that a process ran. It does not prove that the files are complete or that the application can start. At least monthly for important sites, restore a copy to a staging environment and check:
- The archive can be accessed with the required credentials.
- The database imports without errors.
- Files, media, themes, plugins, and configuration are present.
- The site loads without redirect loops, missing assets, or database errors.
- Forms, logins, search, checkout, and other critical workflows function.
- The restored copy is not publicly exposed during testing.
- The team knows who approves and performs a production restoration.
Document the date, backup version, test result, errors, and corrective action. This creates a usable disaster recovery plan instead of a collection of unverified files.
Common mistakes
- Keeping backups on the same server only: A server issue, compromised account, or accidental deletion may affect both the website and its copies.
- Backing up files but not the database: For WordPress and other database-driven applications, files alone may not contain current content or customer records.
- Assuming replication equals backup: A synchronized copy can reproduce deletions, corrupted files, or encrypted data. Preserve versioned copies as well.
- Ignoring email and DNS: A restored website can still fail to receive messages or load correctly if MX, verification, redirect, or domain records are missing.
- Exposing sensitive archives: Backup files may contain personal information, configuration details, or credentials. Keep them private, encrypt them where appropriate, and remove secrets from archives when feasible.
- Never practicing a restore: An unfamiliar recovery process is most difficult when the live site is already unavailable.
- Taking a backup after the change: Create a known-good pre-change copy before redesigns, migrations, bulk imports, updates, or DNS changes.
When to revisit
Review this website backup strategy before seasonal planning cycles, when workflows or tools change, and whenever the cost of lost data changes. A quarterly review is a practical baseline for many small businesses. Perform an additional review when you:
- Launch an online store, membership area, booking system, or customer portal.
- Move to new web hosting, managed WordPress hosting, or VPS hosting.
- Change backup software, storage providers, domains, email systems, or DNS management.
- Install a major application, plugin, theme, or server update.
- Increase publishing frequency, transaction volume, or the number of administrators.
- Experience a security incident, failed update, data loss event, or failed restore test.
Use this action list for your next review:
- List every system that creates or stores website data.
- Assign a backup frequency and retention period to each item.
- Confirm that at least one copy is separate from production.
- Create a pre-change backup before your next update or redesign.
- Restore the latest copy in staging and record the result.
- Update the recovery contacts, access details, and step-by-step procedure.
Revisit the checklist after major platform or security changes, and schedule a recurring restore test so recovery remains a practiced process rather than an assumption.