Journal · Essentials

WordPress backup strategy: how to back up your site and recover it fast

A simple WordPress backup strategy for UK small businesses: what to back up, how often, where to keep it, and how to make sure you can actually restore it.

By Alleo Gordon, founder of WonderlandSites

Picture a personal trainer whose site breaks after an update. “No problem,” they think, “my host does backups.” They ask the host to restore. The host does. The site comes back, but it’s the version from a while ago: the new class timetable is gone, the new testimonials are gone, and the last fortnight’s blog posts are gone.

(An example, not a real client. But “I thought I had backups” is one of the most common sentences in website trouble.)

Having a backup isn’t the same as having a backup strategy. A strategy answers four questions: what’s backed up, how often, where it’s kept, and whether you can actually get it back. Here’s each one, in plain English.

What a WordPress backup needs to include

A WordPress site is two things, and you need both to restore it (WordPress backups guide):

  1. The files: WordPress itself, your theme, your plugins, and everything you’ve uploaded, such as photos and PDFs.
  2. The database: your pages, posts, settings and much of what your forms and plugins store. It lives in a separate system, so downloading your website’s folder does not back it up.

A backup that only includes one of these is a half-backup. WordPress’s guidance suggests treating files and database as one set, made around the same time: back up the database first, then the files.

How often to back up

WordPress’s own suggestion is weekly for smaller sites with fewer changes, and daily for busier sites with lots of activity (WordPress backups guide).

For a service business, I’d think about it this way: how much would you mind losing? If your site takes bookings, enquiries or orders, or you post often, daily is sensible. On my hosting, every care plan includes daily backups, kept separately from the website.

And whatever your regular rhythm, always take a fresh backup before you update anything. That’s the backup you’ll reach for if an update goes wrong.

Where to keep your backups

This is where many backup plans fall over. A backup stored only on the same server as your website can disappear in exactly the situations you need it: a server problem, a hacked account, a lapsed hosting bill.

WordPress’s guidance is to keep at least 3 to 5 recent backups, with copies in different places: for example, one on your hosting server, one in cloud storage and one on your own computer (WordPress backups guide).

A simple version for a small business:

  • Automatic backups from your host or a backup plugin.
  • A copy sent off the server, to cloud storage you control.
  • An occasional download to your own computer, say once a month.

How long to keep them

Keep backups going back a few weeks, not just the latest one or two. Here’s why. If your site is hacked, it may be days before anyone notices. WordPress’s hardening guide gives exactly this example: a site compromised on 1 May but not discovered until 12 May. Only backups from before 1 May are clean (WordPress: Hardening WordPress). If you only keep the last three days, every copy you have may include the problem.

More on what to do in that situation in WordPress site hacked? What to do first.

The step everyone skips: test a restore

A backup you’ve never restored is a hope, not a plan. Files can be incomplete. A plugin may have stopped backing up months ago without saying so. A restore may need a password nobody remembers.

WordPress recommends backing up your automatic backups with a manual one now and then, to make sure the process is actually working. I’d go one step further: every few months, check that a backup can be restored. Many hosts can restore a copy to a test area (often called “staging”), so you can see it works without touching the live site.

What you’re checking:

  • The backup opens and isn’t empty.
  • It includes both files and database.
  • The restored site loads, with your recent pages and photos.
  • You know the steps, and where the logins are.

How to recover fast when something goes wrong

When you need a backup, you’ll be stressed. Decide the plan now, while things are calm.

  1. Pick the right backup. The most recent one from before the problem started, not simply the newest.
  2. Check what you’ll lose. Restoring takes the whole site back in time. Enquiries, bookings or posts made since that backup may vanish from the site. Check your inbox and note anything recent first.
  3. Take a copy of the broken site. Even broken, it may hold something you need, and it helps work out what went wrong.
  4. Restore, files first, then database, as WordPress suggests (most host tools and backup plugins do this for you).
  5. Test properly. Key pages on your phone, your contact form, your booking link.
  6. Fix the cause. If an update broke it, don’t run the same update again without a fix. If it was a hack, close the hole before you go live again.

If it’s an update that went wrong, my guide WordPress update broke my site: what to do in the first hour walks through the first hour.

A one-page backup plan

Write this down and keep it somewhere you’ll find it on a bad day:

  • What’s backed up: files and database.
  • How often: daily (or weekly if the site rarely changes), plus before every update.
  • Where: host or plugin backups, plus an off-server copy, plus a monthly download.
  • How long: at least a few weeks of copies.
  • Last restore test: date.
  • Who restores it: you, your host, or whoever looks after your site.
  • Where the logins live: your password manager.

Backups are one of 12 things worth looking at each month. The full list is in my monthly website health check, and how often to update is in my WordPress update schedule.

If you’d rather backups simply happened, kept safely away from the site, with someone who knows how to restore them, that’s part of website care.

Not sure your backups would save you? Start with a free Website Check

Send me your link and I’ll look it over.

Your free Website Check I look over your website and tell you in plain words what’s working and what’s holding it back, with your top 3 fixes, most important first. It arrives within 24 to 48 hours, Monday to Friday. No jargon, nothing to sign, and nothing changed on your site. Get your free Website Check

When did you last check that your backup actually works?


Frequently asked questions

How often should I back up my WordPress site? WordPress suggests weekly for smaller sites and daily for busier ones. If your site takes enquiries or bookings, daily is sensible, plus a fresh backup before every update.

Doesn’t my host already back up my site? Many hosts do, but it’s worth asking how often, how long they keep backups, where they’re stored, and how quickly they can restore one. WordPress’s guidance still recommends keeping your own copies in more than one place.

Where should I store WordPress backups? Somewhere other than the website itself. WordPress recommends at least 3 to 5 recent backups in different places, such as your host, cloud storage and your own computer.


About the author Alleo Gordon, founder of WonderlandSites. IT technician at a sixth form college in Bethnal Green for 3 years; looking after websites since 2018.

Whenever you’re ready, I’m here.

Tell me a little about where you are and where you’d like to be. I’ll reply personally.

Get in touch