Back up your WordPress website often enough that losing everything since the last successful copy would be manageable. For a quiet brochure site, daily automated copies plus a fresh backup before substantial changes can be a sensible starting point. A shop taking orders throughout the day may need hourly or more frequent protection. Choose the interval from the work you could lose, then check that the backup service can actually deliver it.
If you want backups and staging handled within your hosting platform, I recommend considering Krystal’s managed WordPress hosting. Confirm the backup interval and retention for the exact plan before buying: its current plan cards, general page text and older help article give differing descriptions of the frequency. If your existing host already meets your recovery needs, changing host may add little; first establish who checks the backups and handles a restore.
For the wider division of work between your host, designer and business, use the WordPress maintenance-plan guide.
Start with what changes while you are away
A website can collect valuable information even when nobody is editing its pages. Orders, customer accounts, bookings and stored form submissions may change throughout the day. List those alongside new photographs, page edits and configuration changes before choosing a schedule.
Check where each item actually lives. An appointment held in a separate booking service, a message delivered to your mailbox and an enquiry stored only in WordPress have different recovery routes. A website backup will not automatically protect all three. Ask your maintainer to identify the systems that hold the original records.
Then answer a concrete question: if the site failed now, how far back could you return without losing information you cannot reconstruct? In recovery planning this is often called the recovery point objective. You can write it in ordinary language: “We could re-enter yesterday’s page changes, but we cannot afford to lose a working day of orders.”
The time needed to get the site working again is a separate requirement. An hourly backup may preserve recent information while still taking several hours to retrieve, restore and check. Put both needs in the brief.
Choose an interval for the way your site is used
A brochure site with occasional edits
Daily automated backups are a practical starting point when the important changes are modest and can be recreated. Also take a recoverable copy before a significant update, import or redesign change. If enquiries are stored in WordPress, include their potential loss in the decision even when the public pages rarely change.
A site taking regular enquiries or bookings
Follow the records rather than the page-editing schedule. If losing an afternoon’s submissions would mean losing customers, a nightly copy leaves too large a gap. Consider a shorter interval and confirm that the form or booking data is included. Keep the separate mailbox or booking provider’s recovery arrangements documented as well.
A shop accepting orders throughout the day
Choose protection around the order activity you could safely reconcile after an incident. Hourly copies still leave a possible gap; a busy shop may need a service that captures changes more frequently. Ask what the advertised interval means, how failed jobs are detected and whether the restore preserves a consistent set of order, stock and customer records.
For example, suppose a shop’s latest usable backup is from 09:00 and a fault happens at 09:50. Orders accepted during those fifty minutes may be absent from that copy. Payment records might help an authorised administrator reconcile them, but restoring an older database does not itself reverse payments or recreate every order detail.
Ask the maintainer to explain the reconciliation process before relying on it. A plan that requires somebody to reconstruct dozens of orders manually may be unsuitable even if the hosting fee is low.
Keep older recovery points as well as recent ones
Frequency tells you how often a copy is made. Retention tells you how long those copies remain available. You need both: frequent backups can still leave you with no usable earlier version if a problem goes unnoticed until all the older copies have expired.
Imagine that a product import damages descriptions on Monday, but nobody spots it until the following Monday. A rolling three-day history would contain only copies made after the mistake. More frequent copies within those three days would not recover the earlier descriptions. Keeping a known-good copy before the import would give the maintainer another route.
Choose retention around how quickly you would notice a problem and how often you check important pages and transactions. Ask for the oldest available recovery point, how many versions are kept and whether manual copies expire under the same rules. “Thirty backups” could mean thirty hours, thirty days or another pattern.
A mixture of recent frequent copies and less frequent older snapshots can suit some businesses. Confirm how that arrangement works with the provider, including storage limits and whether older copies depend on an intact chain of earlier backups. Keep the retention policy consistent with the way your business handles the customer information in those copies.
Protect a complete, retrievable copy
WordPress recovery normally needs both the database and the relevant site files. The database holds content and settings; the files include uploads, themes and plugins. A copy that leaves out one of those parts may not rebuild the website you expect. The WordPress backup handbook explains the components and the importance of backing up before upgrades.
Ask how you would retrieve a copy if the normal hosting login were unavailable. An off-site copy managed through the same account may be useful, but access to it still needs a documented route. Record the responsible person, recovery contact and any software needed to open or restore the archive.
If a separately stored local archive belongs in that plan, the portable SSD comparison for website backups covers the drive choice, capacity and handling. Budget for retained versions as well as today’s site. Encrypt sensitive copies, keep the recovery credential separately accessible to authorised people, and disconnect the drive after the verified copy is complete.
Before a risky change, confirm that the fresh backup has finished successfully and is retrievable. Use a staging check before WordPress updates where the change warrants it. A staging copy is a place to test; establish its own backup and expiry arrangements before treating it as a recovery archive.
Put these details in the backup agreement
A useful supplier brief should answer the following questions in terms your business can act on:
- Coverage: which databases, uploads and other files are included, and which external services need separate protection?
- Frequency: how often should a usable copy be completed, and how much recent activity could be missing?
- Retention: what are the oldest available versions and the expiry rules for manual backups?
- Failure handling: who sees an unsuccessful job, investigates it and confirms the next usable copy?
- Recovery: who can request a restore, what support is available and what work or charges sit outside the agreement?
- Acceptance: who checks the restored enquiry, booking or order journey before the site returns to normal use?
Have the maintainer show the latest successful backup time and the available recovery points. A scheduled job that never completes cannot meet the interval you agreed. After a change of host, backup service or major website function, review the brief against the new setup.
Finish by rehearsing recovery safely. Our WordPress backup restore-test checklist explains how to check an isolated copy without overwriting the live site or accidentally sending customer messages.
If you run a business in Formby, Freshfield or L37, send Formby Web Design your website address and the way you use it. That gives us a useful starting point for discussing the website work and maintenance scope you need.
Provider information checked 19 October 2026 against Krystal’s Onyx backup guidance and its managed WordPress plan page. The frequency examples above are planning guidance; the actual service and restore arrangements need to match your site.
