What Good Website Maintenance Actually Includes

"Maintenance" is one of the vaguest words in technology contracts. It can mean a genuine, ongoing commitment to your product — or a monthly line item that quietly does very little. Here is what a maintenance plan should actually cover.

Updates and dependency management

Software you depend on changes constantly. Frameworks, libraries, plugins and server packages release security and stability updates that need to be applied carefully and tested, not blindly. Skipping updates is the single most common reason sites drift into a vulnerable, hard-to-fix state.

Backups you have actually tested

A backup you have never restored is a hope, not a safeguard. Good maintenance includes regular backups and periodic restore tests, so that when you need them, they work.

Security checks and monitoring

Ongoing security review — file integrity, user accounts, exposed endpoints — catches problems before they become incidents. Uptime and error monitoring tells you something is wrong before your customers do.

Performance work

Sites get slower over time as content and traffic grow. Maintenance should include periodic performance review: caching, image sizes, database queries, and anything causing layout shifts or slow first loads.

Honest response times

This is where plans differ most. A trustworthy plan tells you clearly what response time to expect, distinguishes standard requests from emergencies, and does not promise that everything is instant. Vague promises usually mean vague delivery.

What to ask for

• A written list of what is included each month
• A monthly report of what was actually done
• Clear response windows for standard vs urgent work
• Who to contact, and how, when something breaks

If you would like a plan scoped to your systems, take a look at our support plans or send us the details and we will recommend the right level of care.