Website maintenance
Website maintenance is the ongoing work that keeps a site secure, current and functioning after launch: software and plugin updates, backups, uptime and error monitoring, security patching, and small content or layout changes.
In practice
The word covers three different things that get billed as one, and most disputes between a company and its vendor come from that blur. Hosting is renting the machine your site runs on. Maintenance is keeping the software on that machine patched and the site working. Improvement is making the site better than it was. A plan that quietly includes only the first two while the invoice implies all three is the single most common complaint we hear from established companies.
A maintenance plan worth paying for names its scope in writing. That means the update cadence, whether backups are tested rather than merely taken, what monitoring runs and who it alerts, how many hours of content changes are included, and what falls outside and gets quoted separately. Vague plans are not usually dishonest. They are just written so that any month's work can be described as covered, which means no month's work can be checked.
Here is a test you can run this week. Ask your vendor for a log of everything they changed on your site last month, with dates. A team doing real maintenance produces it in a day, because the log already exists in their ticketing or version control. A team that has been quietly collecting a retainer will produce a summary written after you asked, or will describe the work in categories rather than events. The difference in the reply tells you more than the invoice does.
The second thing to check is what accumulates when maintenance is skipped. Deferred updates are technical debt with a security dimension: every unpatched month widens the gap between your site's software and the current release, and closing a two-year gap is a project, not a task. Companies that stop paying for maintenance rarely notice for a year and then discover the upgrade costs more than the maintenance would have.
Maintenance is also where ownership quietly gets decided. If the plan includes hosting on infrastructure you cannot access, a content system you have no login to, and a domain registered to the vendor, then cancelling maintenance means losing the site. That is a different arrangement from the one most owners think they bought, and it is worth confirming before renewal rather than during a dispute. See vendor lock-in for the wider pattern.
None of this argues against paying for maintenance. A B2B site running current software, with tested backups and someone watching the error log, is worth the monthly cost and cheaper than the alternative. The argument is for knowing what the line item buys, because the same price buys wildly different work depending on who wrote the scope.
Common questions
What does website maintenance actually include?
At minimum: software, plugin and dependency updates, tested backups, uptime and error monitoring, security patching, and a defined allowance of small content changes. Hosting and new feature work are usually separate, and a plan worth paying for says so in writing rather than leaving it to interpretation.
Is website maintenance the same as hosting?
No. Hosting is renting the server your site runs on. Maintenance is the work of keeping the software on it patched, backed up and functioning. They are often sold together on one invoice, which is why many owners believe they are paying for maintenance when they are only paying for hosting.
How do I tell whether my maintenance plan is doing anything?
Ask for a dated log of every change made to your site last month. A team doing the work produces it quickly because the record already exists in their ticketing or version control. A summary written in response to your question, rather than exported from a system, is the answer.
What happens if we stop paying for website maintenance?
Nothing visible for months, then a compounding problem. Unpatched software drifts further from current releases until updating becomes a project rather than a task, and unmonitored errors go unnoticed until a buyer reports them. Check first whether cancelling also ends your access to the hosting, content system or domain.
What should a maintenance agreement specify?
Scope of included work, update cadence, backup frequency and whether restores are tested, monitoring and who gets alerted, included hours for changes, response times, and what is explicitly excluded. See our entry on the service level agreement for how response and resolution times should be written.