What a full backup includes
A website usually has two parts: files (themes, plugins, uploads, code) and a database (pages, posts, settings, orders and form entries). Backing up only one will not rebuild the site. For hosted builders, the platform keeps the data, but you may still be able to export content and should check what the provider actually retains.
Do not forget related pieces: DNS records, email settings and any third-party accounts. Write those down too.
How often to back up
The right frequency depends on how often content changes. A brochure site edited monthly can use weekly backups. A store that takes orders or a site with daily form entries needs daily or even real-time database backups, because losing a day of orders is costly.
Take an extra backup immediately before updates, redesigns or plugin changes, so you have a clean point to return to.
Keep copies in separate places
A backup stored on the same server as the site disappears if that server fails or is compromised. Follow the idea of several copies in different locations: one with your host, one in cloud storage under your own account, and ideally one you control offline. Protect those storage accounts with two-step verification.
Check the retention period. If malware sits unnoticed for three weeks, you need backups older than that.
Test a restore
Once or twice a year, restore a backup to a staging site or test location and open the pages. Check images, forms, logins and checkout. Time how long the process takes and write down the steps. Knowing it takes an hour, not a day, helps you decide what to do during an outage.
Look for silent failures: backups that run but are empty, truncated or blocked by size limits. A file size that looks too small is a clue.
Your host's backups are not a plan by themselves
Hosting plans often include backups, but the terms vary. Some keep only a few days, charge for restores, or exclude databases. Read the policy and ask support how to request a restore. Treat the host copy as one layer and keep your own as well.
Document where everything lives and who has access, so a restore does not depend on one person's memory.
A simple schedule you can copy
For a small brochure site: weekly automatic backup kept for a month, one copy sent to cloud storage you own, a manual backup before any big edit, and a restore test each spring and fall. For a store: daily database backups, file backups weekly, and thirty days of history.
Put the schedule in writing along with login locations. If a freelancer or agency manages the site, ask them to confirm it matches what they actually run.
If you ever change hosts, redo your backup setup immediately. Schedules, storage locations and plugin settings rarely carry over, and many owners go months without realizing the old plan stopped running when the account closed.
Common questions
Is a plugin backup enough?
It can be, if it sends copies off the server and you have tested a restore.
How long should I keep old backups?
Long enough to recover from an unnoticed problem, commonly several weeks of history, plus a few older monthly copies.
Do website builders need backups?
The platform usually runs the infrastructure, but export your content and keep copies of images and text yourself.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.