
Summary: Website maintenance includes security updates, tested backups, uptime monitoring, security checks, performance tuning, small content changes and support. The price depends on the platform, site size, how often things change and the response time you contract. Not doing it usually costs more: a hacked, offline or outdated site.
A website runs on a server, uses software that receives updates and is constantly exposed to automated scans. Without care, it ages badly: it gets slow, vulnerable and full of stale information. Maintenance is the ongoing work that prevents this.
What a maintenance plan includes
| Activity | What it is | Common frequency |
|---|---|---|
| Updates | CMS core, plugins, themes, libraries and PHP version, tested before applying | Weekly or whenever a security fix is released |
| Backup | Files and database, stored off the server | Daily, keeping several versions |
| Restore test | Restoring a backup in a test environment | Periodic |
| Monitoring | Alerts when the site goes down, slows or the SSL is about to expire | Continuous |
| Security | Checking changed files, admin users, access logs | Monthly |
| Performance | Core Web Vitals, image weight, caching | Monthly |
| Technical SEO | Search Console errors, broken links, sitemap | Monthly |
| Content | Changing text, photos, prices, adding pages | On demand |
Backups done right: the 3-2-1 rule
A widespread disaster recovery practice is keeping 3 copies of the data, on 2 types of storage, with 1 copy off-site (off the website's server). A backup on the same server doesn't protect against server failure or an attack that wipes everything. And a backup that has never been restored is an assumption, not a guarantee.
Why updating matters so much
Most attacks on small business websites exploit known, already-fixed vulnerabilities in software nobody updated. For WordPress, the project itself advises keeping core, themes and plugins updated and removing anything unused (hardening guide). The PHP version matters too: unsupported versions no longer receive security fixes (supported PHP versions).
What changes the price
- Platform: WordPress with many plugins needs more attention than a static site.
- Size and type: online stores and web applications need more than an institutional site (payments, inventory, customer data).
- Volume of changes: those who change content weekly need more hours.
- Response time: same-day service costs more than a few business days.
- Staging environment: updating a copy first is safer, and more work.
What happens when nobody takes care of it
- An outdated plugin becomes the door for hacking, spam or malicious redirects.
- The site goes down and nobody notices for days. See website down.
- The SSL certificate expires and the browser shows "Not secure". With the gradual reduction of maximum certificate validity (200 days since March 2026), automatic renewal is no longer optional.
- With no backup, a failure means rebuilding everything.
- An old phone number and discontinued services stay online.
Monthly checklist to evaluate the service
- Do I receive a report of what was updated?
- Are backups off the server, and when was the last restore test?
- Is there monitoring of uptime and of SSL and domain expiry?
- Who has access to the admin and hosting? Are passwords strong, with 2FA?
- Does Search Console have pending errors?
On demand or monthly plan?
On demand works for simple static sites that barely change. For WordPress, stores and lead-generating sites, a monthly plan costs less than firefighting. See our website maintenance, which can come together with hosting. For security basics, read website security.
Sources and references
- WordPress: hardening
- WordPress: backups
- PHP: supported versions
- CA/Browser Forum: Ballot SC-081v3 (certificate validity)
- OWASP Top 10
Frequently asked questions
Does a static site need maintenance?
Less than a CMS, but yes: updated server and PHP (if any), backups, SSL and domain renewal, and fixing links and content.
How often should I back up?
For sites that change little, weekly may be enough; for stores and sites with forms or sign-ups, daily. Keep copies off the server and test restores.
My host already backs up. Do I need another?
It's recommended. Check where the host's backup lives, for how long and how to restore it. An independent off-server copy protects against provider failures.
Can updating plugins break the site?
It can, which is why it's best to test on a copy first and have a recent backup. Not updating, though, is the bigger risk.
Want your website always up to date and secure?
We handle updates, backups, monitoring and changes so you can focus on your business.
Read also
- Website security: the basics every business should have
- Website down: what to do and how to find the cause
- A slow website loses customers: how to make your site faster
Written by Mário Moreno, founder of Agência hetsi, which has been building websites and handling digital marketing for businesses in Brazil and abroad since 2000. Mário Moreno on LinkedIn