Guide
Website maintenance: what it involves and what to budget for
What ongoing website maintenance really covers, a monthly and quarterly checklist, what is worth paying for, and how to tell if your current maintenance plan is doing anything.
VAULT 33|27 · Updated 12 November 2026 · Reviewed 12 November 2026 · 1 min read
What maintenance should cover
| Area | Monthly | Quarterly |
|---|---|---|
| Security and updates | Updates applied, unused plugins removed, alerts checked | Access review: who still has logins? |
| Backups | Confirm they run | Test a restore |
| Enquiry paths | Test every form, call link, chat and booking | Review response times |
| Tracking | Key events still firing, CRM receiving sources | Audit tags and consent setup |
| Speed | Spot-check key pages | Full Core Web Vitals review |
| Content | Fix errors, update prices, hours and team | Refresh top pages; check facts with dates |
| Search | Search Console errors | Indexing and performance review |
| Legal | Notices accurate | Privacy, cookie and accessibility statements reviewed |
What is worth paying for
- Monitoring and fixes, so problems are found in hours, not months.
- Monthly enquiry path tests: broken forms are among the most expensive website problems.
- Small content changes done quickly.
- A monthly report that says what was checked, what was fixed and what moved.
Signs your maintenance plan is doing nothing
- No report, or a report with only "updates applied".
- Forms broke and you found out from a client.
- Nobody can tell you when backups were last tested.
- The site is slower than a year ago and nobody mentioned it.
Budgeting
Maintenance costs depend on the platform, the number of plugins or integrations, and how much content changes. A lean site with few moving parts costs less to maintain. When comparing plans, compare what is checked and reported, not just the monthly fee.
Open your vault.
A free systems audit of your business: where enquiries leak and exactly what we would build.
Book your free audit