Website maintenance is the easiest line item to cancel and the one most likely to be regretted. Nothing visibly happens when you pay it, and nothing visibly happens when you stop — until something does, usually at the worst possible time.
This guide sets out what maintenance actually covers, what it reasonably costs, and how to tell whether a monthly plan is doing real work or simply arriving every month.
Why Websites Need Maintaining At All
A website is not a printed brochure. It sits on a server, runs software, connects to other services, and is continuously visited by both people and automated systems looking for weaknesses.
Things change around it whether you touch it or not:
- Browsers update and occasionally break older code
- Platform, plugin and library updates fix security flaws
- Hosting environments change PHP or database versions
- SSL certificates expire
- Payment providers and APIs change their requirements
- Automated scanners probe every site on the internet, constantly
Left alone for long enough, a site does not stay the same. It degrades.
What a Maintenance Plan Should Include
The genuine essentials
- Software updates. Core platform, themes, plugins and dependencies, applied and then checked rather than applied and hoped for.
- Backups. Automated, stored somewhere other than the same server, and periodically restored to prove they work. An untested backup is a guess.
- Uptime monitoring. Automatic alerts when the site goes down, so you learn from a monitor rather than a customer.
- Security monitoring. Malware scanning, login protection, and a defined response if something is found.
- SSL certificate management. Renewal before expiry, because an expired certificate shows visitors a browser warning that stops traffic dead.
- Form testing. Periodic confirmation that enquiries still arrive. This one is skipped constantly and it is the one that costs money directly.
Commonly included, reasonably
- A set allowance of content edits each month
- Broken link checks
- Performance monitoring
- A short report describing what was actually done
- Defined support hours and response times
Usually separate, and fairly so
- New pages or sections
- Design changes
- New functionality or integrations
- SEO campaigns and content writing
- Hosting itself, unless explicitly bundled
Maintenance keeps what exists working. Improving it is a different service, and treating them as one thing is how expectations get mismatched.
What It Reasonably Costs
Prices vary widely by market, site complexity and how much human time is involved. Rather than quoting figures that will be wrong for someone, it is more useful to understand what drives the number:
| Driver | Effect on price |
|---|---|
| Static brochure site, few pages | Lowest — little can break |
| CMS site with plugins | Higher — regular updates and compatibility testing |
| eCommerce | Higher again — payments, stock, orders, greater downtime cost |
| Custom application | Highest — specialist knowledge, bespoke code |
| Included edit allowance | Direct human time, the largest variable |
| Response time guarantee | Faster commitments cost more to staff |
The useful comparison is not one plan against another by price, but each plan against what it contains. A cheaper plan covering updates only, versus a dearer one including two hours of edits and same-day response, are different products.
How to Tell If You Are Paying for Nothing
Ask for four things. A supplier doing the work will answer easily.
- A record of what was done last month. Which updates, which checks, any issues found.
- Evidence of a restored backup. When was a restore last tested?
- Your uptime figure for the last quarter.
- Confirmation your forms were tested, and when.
If the answers are vague, you may be paying for availability rather than activity. That is not automatically fraud — being on call has real value — but you should know which one you are buying.
What Happens Without It
Not a dramatic failure. A slow accumulation:
- An outdated plugin becomes a known vulnerability, then an entry point
- A hosting PHP upgrade takes the site offline with no backup to fall back on
- A certificate expires and browsers start warning visitors away
- A form silently stops delivering and nobody notices for months
- A compromised site starts serving spam and gets flagged in search results
The last one is the expensive scenario. Cleaning a compromised site, restoring it, and recovering search visibility costs considerably more than years of maintenance would have — and unlike maintenance, it happens on an emergency timetable.
Can You Do It Yourself?
Some of it, yes. If you are comfortable in the admin area, you can apply updates, run a backup plugin and check your forms.
What is harder to do yourself is the part that matters when something goes wrong: knowing how to roll back a broken update, recognising a compromise, and having a tested restore path. If the site generates meaningful revenue, that capability is worth paying for.
A reasonable middle position is to handle content edits yourself and pay for the technical layer.
Questions to Ask Before Signing
- What exactly is included, and what is billed separately?
- How often are backups taken, where are they stored, and how long are they kept?
- When was a restore last tested?
- What is the response time for a site that is down, including out of hours?
- Do I receive a report, and what does it contain?
- If a site I maintain elsewhere gets hacked, is remediation included or extra?
- Can I cancel monthly, and do I keep access to everything if I leave?
That last question matters as much as the price. Maintenance should not be the mechanism that makes leaving difficult.
Summary
Maintenance buys updates, tested backups, monitoring, security and someone who answers when something breaks. Judge a plan by what it contains and what evidence of work you receive, not by the monthly figure alone. And ask when a backup was last actually restored — the answer tells you most of what you need to know.
If you want to know what your site realistically needs, ask us and we will tell you plainly, including if the answer is very little.
Ask About Support Compare Plans
Frequently asked questions
Do I really need a website maintenance plan?
If the site generates revenue, yes. Without updates, tested backups and monitoring, problems accumulate quietly: an outdated plugin becomes an entry point, a certificate expires, a form stops delivering. Cleaning up a compromised site costs far more than years of maintenance.
What should a maintenance plan include?
Software updates applied and checked, backups stored off-server and periodically restored, uptime and security monitoring, SSL renewal, and regular form testing. Content edits and new functionality are normally separate.
How do I know my maintenance provider is doing anything?
Ask for last month's record of work, your uptime figure, when a backup was last actually restored, and when your forms were last tested. A provider doing the work answers easily.
