B
Backup
Definition
A backup is a complete, restorable copy of your website — files and database together — stored somewhere your website isn't.
In plain English
A backup is not a copy of your homepage. A WordPress site is two things at once: files (theme, plugins, uploads) and a database (posts, pages, settings, orders). Lose either one and the site is gone.
A real backup captures both at the same moment, so restoring puts you back exactly where you were — not “mostly” where you were.
Why it matters
Sites break. A plugin update conflicts, a migration goes sideways, someone pastes bad code into a theme file, or a login gets compromised.
With a tested backup, that's a bad twenty minutes. Without one, it can be a bad month — or the end of the site.
How it works
- Back up both halvesFiles and database, captured together. Every time, no exceptions.
- Match the schedule to the riskA shop taking daily orders needs daily backups. A five-page brochure site can live with weekly.
- Store it somewhere elseGoogle Drive, Dropbox, S3. A backup sitting on the same server as the site dies with the server.
- Restore one on purposeAn untested backup isn't a backup. It's a hope.
Take a manual backup before anything scary
Theme swap, PHP version bump, major WooCommerce update — take a fresh backup first. Thirty seconds of work, and the update stops being frightening.
Watch it in a real build
Related terms
Tip: use ← and → to move between entries.
The Friday email
One email a week. The thing I'd tell you over coffee.
What changed in WordPress and AI that week, what I'd actually use, and what I'd ignore. Written by me, not summarised by a tool.
- New tutorials the moment they're published
- Honest verdicts on tools — including the ones I dropped
- No sequences, no upsells, one click to leave
Free, forever, no signup
Pick a starting point. Have something real by tonight.
Every tutorial is free, complete, and built in real time — including the bits that break. Start where you are, not where a course thinks you should be.