WordPress sites change often — themes, plugins, content. A restore path matters as much as the live design.
Layers of backup
- Account backup — full or partial copy from cPanel / the client area Backup shortcut. Includes files and databases for the whole hosting account. See How to Back Up Your Hosting Account.
- WordPress-aware backup — a plugin or the cPanel installer‘s backup feature that understands WP files + database together. Useful before theme experiments.
- Off-site copy — download archives to your computer or remote storage. A backup that only lives in
public_htmlis not a separate safety net.
When to take one
- Before core, plugin or theme updates
- Before redesigns, migration or turning on a new builder
- After a stretch of heavy publishing (export content if needed)
Testing changes without breaking the live site
Options on typical shared/reseller plans:
- Staging / clone (if shown in your installer) — Softaculous and WordPress Toolkit sometimes offer a staging or clone button. If you see it, use it to copy the site to a subdomain, test there, then push back only when happy. If you do not see staging, do not assume it is missing forever — open a ticket and ask what is available on your plan.
- Subdomain copy — install a second WordPress on
staging.yourdomain.com, import content, test, then plan a careful cutover. - Maintenance window — for small sites, backup → change → verify quickly can be enough.
Restore mindset
Restoring overwrites the live site. Know whether you are restoring files only, database only, or both. When in doubt, describe what went wrong and which backup date you have — support can help you choose a safe path.
Keep one recent backup you have already downloaded. That habit alone prevents most late-night panics.
