Website Maintenance After Launch: What a Support Plan Should Include
By Parker Gawryletz · Local Cochrane Web Design · Last updated: · 8 min read
A website maintenance plan should include managed hosting or monitoring, automatic backups with tested restores, security and software updates, performance and broken-link checks, a content-change allowance, stated response times, plain reporting, and written portability terms. If a plan cannot list these, you are buying a monthly fee, not a service.
A website goes live, the invoices stop, and a quiet question arrives: what should a website maintenance plan include, and is the monthly fee actually buying it? Two plans at the same price can describe very different services — one is real care, the other a hosting bill with a new name.
This guide lists what belongs in a plan, what is optional, and the two things that separate good from bad: tested restores, and the written right to leave with your site. It is the standard behind our own website care and hosting in Cochrane plans.
The short answer
- Hosting keeps a site online; maintenance keeps it healthy — different services.
- Backups only count once a restore has actually been tested.
- A real plan states response times, update cadence, and an emergency process.
- You should be able to leave with your complete site at any time.
- Compare plans line by line on scope, never on monthly price alone.
Hosting and maintenance are not the same service
Hosting is the server your website lives on. Maintenance is the human work that keeps the site healthy: updates, backups, monitoring, fixes, and changes. Many plans bundle both, which is fine — but a quote should price them separately, because a hosting bill relabelled as a care plan is the oldest trick in this market.
One question separates them: if I stopped paying, what would stop happening? If the answer is only that the site goes offline, you are paying for hosting. If nobody would watch, update, back up, or fix anything, you are paying for maintenance. A good plan answers both parts clearly.
Essential infrastructure and monitoring
The baseline layer is quiet: reliable hosting with an SSL certificate, uptime monitoring that alerts the provider before customers notice, and someone accountable when the site goes down. None of this is glamorous, and all of it should be named in the plan rather than assumed.
The test question is simple: how would you find out my site is down, and how fast? A provider with real monitoring answers in one sentence; one without it changes the subject.
Backups and tested restoration
Backups should run automatically, be stored somewhere other than the live server, and — the part most plans skip — be tested with a real restore. An untested backup is a hope, not a safeguard. Ask when the last restore test happened; the answer tells you everything about the plan.
- Frequency — daily for sites that change often; weekly is a floor, not a target.
- Location — copies kept off the live server, so one failure cannot take both.
- Retention — how far back you can go, stated in days or weeks.
- Proof — a restore has been performed, and the plan says how often it repeats.
Security and software updates
Every website runs software, and software ages. A maintenance plan should state what gets updated — platform, plugins, themes, dependencies — how often, and what happens when an update breaks something. Sites running outdated software are the ones that get compromised, usually by automated attacks that never cared who you are.
A backup should run before updates, so a bad update can be rolled back instead of debugged live. A fair question for any provider: what happened the last time an update broke a client site?
Performance and broken-link checks
Websites degrade quietly: images bloat, links break, forms fail after a browser update. A good plan includes periodic speed checks against Google's Core Web Vitals thresholds — LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 — plus broken-link scans and a test of every form.
Speed is a property the site keeps or loses over time. The targets worth writing into a plan are covered in website speed requirements — the same numbers apply after launch as before.
Content changes and improvement allowance
Most plans include a monthly time allowance for small changes: updating hours, swapping photos, adding a testimonial, adjusting copy. The plan should state how much time is included, what counts as a small change versus a project, and whether unused time rolls over or disappears.
A plan with no change allowance is workable — every request just becomes a new invoice. That is fine to accept knowingly, and frustrating to discover at your first request.
Response times and emergency process
A plan should state two numbers in writing: how quickly the provider responds to a normal request, and how quickly they act when the site is down. It should also name the emergency channel. "We are usually pretty fast" is not a response time; it is a mood.
A same-business-day acknowledgement for normal requests is a healthy standard to ask for, and emergencies should have their own defined path rather than a general inbox. Whatever the numbers are, they belong in the plan document.
Ownership, portability and cancellation
The most important line in any maintenance plan is the exit. You should own your domain, your content, and your site, hold admin access to every account, and be able to leave with a complete copy of the website without penalty. A plan that locks you in is not a plan; it is leverage.
Get the exit terms in writing before the first invoice — the full breakdown is in who owns your website and accounts. Our own written guarantee includes documented ownership, so the site leaves with you if you cancel.
Reporting that explains what changed
A maintenance report should read like plain language, not a server log: what was updated, what was backed up and tested, what broke and was fixed, how the site is performing, and what is recommended next. If a monthly fee produces no report, you cannot tell maintenance from silence.
A short honest report beats a long automated one. A month where nothing happened is fine — as long as the report says so, and what was checked to know it.
How to compare plans on equivalent scope
Compare maintenance plans the way you compare quotes: line by line against the same list, marking each item included, excluded, or not stated. Price only means something between plans covering the same scope. The table below is the list — the essentials, the useful extras, and the red flags.
| Inclusion | Essential | Useful | Red flag if missing |
|---|---|---|---|
| Uptime monitoring | Yes | — | You learn about outages from customers |
| Automatic off-server backups | Yes | — | One failure can erase the site and its copies |
| Tested restores | Yes | — | Backups exist but have never been proven |
| Security and software updates | Yes | — | The site quietly becomes an easy target |
| Speed and broken-link checks | — | Yes | The site degrades and nobody notices |
| Content-change allowance | — | Yes | Every small edit becomes a new invoice |
| Written response times | Yes | — | Emergencies wait in a general inbox |
| Plain-language reporting | — | Yes | You cannot tell maintenance from silence |
| Written exit and portability terms | Yes | — | Leaving means losing the website |
For local context: our own care and hosting plans run $59–$249 per month, with hosting at cost from $59 — and this table applies to us too. Reading providers against one list is also how you shortlist a builder; the best web design companies in Cochrane comparison uses the same method.
Frequently asked questions
What is included in website maintenance?
A complete plan covers hosting or hosting oversight, uptime monitoring, automatic backups with tested restores, security and software updates, performance and broken-link checks, a small monthly change allowance, stated response times, and plain-language reporting. The exact mix varies — what matters is that every inclusion is written down.
How much maintenance does a website need?
It depends on the platform and how often the site changes. A simple brochure site may need monthly updates, backups, and checks. A busy site with forms, bookings, or e-commerce needs weekly attention or better. The honest answer comes from asking each provider what they would do in a typical month.
Are hosting and maintenance the same?
No. Hosting is the server space that keeps your website online. Maintenance is the ongoing human work — updates, backups, monitoring, fixes, and small changes. Many providers bundle them into one monthly fee, which is fine, as long as the plan states clearly what each part includes and costs.
How often should backups run?
Daily backups are a healthy standard for most business websites; weekly is a reasonable floor for a site that rarely changes. Frequency matters less than two details: backups stored away from the live server, and restores actually tested, so you know the backups work when you need them.
Who updates website content?
The plan should say. Most plans include a monthly time allowance for small content changes made on request — updated hours, new photos, a fresh testimonial. Larger content work is usually quoted separately. If you prefer to edit pages yourself, confirm the plan includes access and training.
Can I move hosts later?
You should be able to, and the plan should say so in writing. Ask three questions before signing: do I own the site, can I get a complete copy on request, and is there any cancellation penalty. If any answer is vague, treat it as a no and keep shopping.
Sources
Compare website care and hosting — monthly care and hosting from $59 to $249, with hosting at cost — read the tiers against this guide's checklist.