Backup frequency is not retention
A backup schedule says how often copies are made. Retention says how many restore points remain and for how long.
Backups help recovery; security controls reduce risk. Neither replaces the other. Understand restore points, account access, updates, malware response and the limits of shared responsibility.

A backup schedule says how often copies are made. Retention says how many restore points remain and for how long.
A backup is not a recovery plan until you know what it contains, where it is stored and how restoration is requested or performed.
Use unique passwords, multi-factor authentication where available and individual accounts instead of sharing one administrator login.
WordPress core, themes, plugins and custom code need compatibility-aware updates. Hosting security cannot patch vulnerable application code for you automatically.
Remove unused accounts and software, restrict privileges, protect secrets and avoid leaving development copies publicly accessible.
When a compromise is suspected, preserve evidence, contain access, identify the affected scope and restore only from a trustworthy point.
Backups, DNS, email, testing and rollback.
Read the guide →Find the cause before changing everything.
Read the guide →Updates, access, monitoring and recovery planning.
Read the guide →Product pages, categories, technical SEO and measurement.
Read the guide →Build costs, running costs and extras.
Read the guide →Choose the right amount of work.
Read the guide →Find the cause before choosing a fix.
Read the guide →Use the Hosting Plan Finder → · Open the customer help centre →
No. Backups support recovery. Security controls, updates, access management and monitoring reduce the likelihood and impact of compromise.
A single copy can fail or already contain the problem you are trying to recover from. Appropriate retention and independent copies depend on the importance and change rate of the site.
Responsibility is shared. The host secures the hosting layer within its scope, while website owners or maintainers are responsible for supported applications, credentials and updates unless a maintenance agreement says otherwise.
Check frequency, retention, what is included, restore process, exclusions and whether you need an additional independent backup for business-critical data.