What monthly website maintenance actually covers
A website decays the moment you stop touching it. Software ages into vulnerabilities, content drifts away from reality, links die, and forms fail without a sound. Monthly maintenance is a scheduled pass that applies updates, tests the things that break silently, and keeps the site telling the truth about your business. We run this pass on the client sites we maintain, and this article lists what belongs in it.
Why it matters operationally
Website failures are almost never loud. The contact form stops delivering while the thank-you page keeps working, so neither the visitor nor the owner sees a problem. The owner finds out from a customer, weeks later, if the customer bothers to mention it. The real cost is not the repair; it is the leads and trust lost during the weeks nobody knew.
What decays on an untouched website
- Software updates and security patches. Every site runs on components (plugins, themes, code libraries) that ship fixes constantly. Unapplied patches are the most common way small-business sites get hacked.
- Content drift. Hours change, staff leave, prices move, services get dropped. The site keeps saying whatever it said at launch.
- Link rot. Pages you link to move or disappear, and every dead link costs you a visitor and a little search credibility.
- Forms. A form depends on a chain: the page, the delivery service, the destination inbox. Any link in that chain can break with no visible error.
- Backups. A backup nobody has ever restored is a hope, not a backup.
- Performance. Sites slow down as images pile up and third-party scripts accumulate, and speed affects both visitors and search ranking.
Common failure modes
Set it and forget it. The site launches, everyone celebrates, and nobody owns it afterward. A year later the phone number is old, the software is many versions behind, and the form quit at some unknown point in between.
Confusing hosting with maintenance. Hosting keeps the server powered on. It does not update your site's software, test your form, or fix your content. "Our hosting plan covers it" usually means nobody is doing it.
Update fear. An update broke the site once, so now nobody updates anything. The answer is working backups and a way to roll back, not abstinence. Frozen software is exactly what attackers scan for.
Maintenance theater. A monthly line item on an invoice with no record of work behind it. If nobody can say what they did in March, they did nothing in March.
A real monthly pass, as a checklist
- Apply software updates, then load the key pages to confirm nothing broke
- Submit the contact form and confirm the notification arrives where it should
- Click through the main pages for dead links and stale content
- Confirm backups ran, and actually restore one on a recurring schedule to prove they work
- Compare the site to reality: hours, staff, prices, services offered
- Read the performance numbers against last month's
- Write down everything done, with dates
The pass takes discipline more than genius. Any competent provider can run it. The difference between providers is whether it happens every month and leaves a record.
What maintenance is not
Maintenance is not redesigns, new pages, new features, or marketing campaigns. Those are projects with their own scope and price. Maintenance keeps what already exists working and true. A plan that promises "unlimited changes" for a small monthly fee is selling something, but it is not this.
How to judge whether your maintenance plan is real
Ask for the log. A real provider keeps a dated record of what they did each month and hands it over without flinching. Then ask 3 specifics: when someone last tested the form with a real submission, when they last restored a backup, and what they updated last month. Vague answers to all 3 mean you are paying for standby, not maintenance.
When professional help is warranted
An owner can run parts of this pass alone: submitting the form, reading the site against reality, clicking the main pages. Hand the rest to a professional when the site runs on software you do not understand, when it produces real revenue, or when an update has ever broken it and nobody knew how to roll back. The stakes, not the difficulty, are what justify paying for it.
Red Eye's recommendation
Put a name on it. Every site should have one person or one vendor who owns the monthly pass and produces a dated log, no exceptions. If you keep it in-house, use the checklist above and date every entry. If you pay someone, the log is the deliverable: ask to see it before you sign, and every quarter after.