What Website Maintenance Does Each Month and Where It Stops

The most expensive website problems are the ones you never see coming. A contact form that quietly stops delivering messages. A booking flow that fails for a week before anyone notices. A TLS certificate that expires on a Sunday morning. None of these announce themselves; they simply stop working, and the first you hear of it is a customer telling you they tried to get in touch and never heard back.

That is what a monthly website maintenance plan exists to address. But as more businesses buy care plans, the more important it becomes to understand exactly what is included, how often each check runs, and, just as crucially, where the plan stops. A care plan is not insurance against everything that can go wrong, and it is not a retainer for new work. It is a defined list of checks on the things that fail silently.

In this post, we walk through a care plan line by line: platform and plugin updates, backups and restore tests, form and booking deliverability, certificate and renewal dates, speed and broken-link checks. By the end you should be able to weigh the monthly fee against doing the work yourself, and ask the right questions before you buy.

What Website Maintenance Actually Means in Practice

Maintenance of a website is a recurring schedule of checks and small fixes, not a project, redesign, or guarantee that nothing will ever break. It is preventive upkeep, aimed at the failures that guard nothing so obviously that they only surface when a customer notices. A fixed-scope build delivers the site once; a monthly care plan keeps that same site running and does not add pages, copy, or campaigns. The phrase “website in maintenance” is used loosely, so ask whether it means a scheduled update window, a status page, or ongoing monthly checks. The useful question is not whether maintenance sounds valuable in general but which specific checks run, how often, and what you are told afterwards. Compare the scope on the services page with the website build page to see where launch work ends and monthly care begins.

The Monthly Update Cycle: Platform, Core and Plugins

From that checklist, the update cycle is usually the first recurring task. This is the core of website maintenance. The cycle runs in a fixed order. Read release notes first to see what each update changes and whether it touches forms or booking logic. Take a fresh backup, apply updates on a staging copy where one exists, test the pages and flows that matter, then push to live. Patching is preventive maintenance, not an emergency response. The risk is concrete: an update can break a contact form, a booking widget or a layout. Version pinning is a decision point: if a plugin stops receiving updates, a good plan flags it rather than leaving old code in place. Sites that change quickly or take payments may need more frequent updates, so confirm the schedule. Afterwards you should receive a short note covering what was updated, what was held back, and what needs a decision or an extra quote, consistent with the written scope and terms. Next, backups get tested.

Backups and the Restore Test Nobody Sees

The update cycle depends on a rollback point, and that is where backups earn their place.

A proper backup captures files and database together, because plugin settings usually live in both, and stores the copy away from the hosting account. Retention should reach back far enough to cover a fault you only notice weeks after it started, not just last night.

The restore test is the part nobody sees and the part that matters. A backup that has never been restored is an untested assumption, so the monthly routine should confirm a copy actually reinstalls and the site works once it does.

Keep the purpose narrow. This recovers you from a failed update, a deleted page or a compromised account. It is not a content editing workflow and not an email archive. If copies sit only on the same host as the site, they disappear with it, so ask where they live and who can retrieve them.

Finally, the boundary: restoring a site does not restore lost bookings, sent email, or payments processed elsewhere. If a fault keeps returning rather than resolving, that is when a repair or rebuild decision becomes the real question.

Forms, Bookings and Email Deliverability: The Checks That Catch Silent Failures

Backups restore what existed; they cannot tell you a form stopped delivering six weeks ago. The monthly test is a real submission sent from an outside address, with confirmation that it arrived in the destination inbox, not merely that a thank-you screen appeared, and that the notification reached the right person rather than a former employee's address.

Booking flows need the same end-to-end treatment: selection, availability, any deposit step, confirmation email, calendar entry, and the reminder that follows days later. Deliverability sits behind all of it. Sender authentication records need to be present and aligned, reply-to addresses must be correct, and a form can report success while its email is filtered as spam. Yahoo's sender standards, for instance, treat SPF or DKIM as a baseline for all senders.

These flows break quietly during an update, a DNS or email provider migration, a change of booking software, or a staff departure. A plan should state whether you get a recorded pass each month or hear nothing until failure. Monthly testing should confirm those form and booking flows actually feed the wider analytics setup you rely on.

Certificates, Domains and Provider Renewal Dates

Deliverability tests catch failures hidden inside an inbox. Renewals fail in public: once a TLS certificate lapses, the browsers that trust the certificates expire alongside it stop accepting the site, on every device that shares that trust.

Keep a renewal calendar: certificate expiry, domain registration, hosting and email plans, booking platform subscriptions, and the card that pays for them. Registrar and hosting logins should sit in an account you control, so a change of supplier never strands the domain. Monthly, confirm the next 90 days of expiry dates, check payment methods, and verify automatic renewals are actually switched on.

Speed, Broken Links and Search Visibility Checks

Once renewals are confirmed, the next layer looks at how the site performs for visitors and search engines. Speed is tracked as a trend, not a single score: page weight and load times are sampled on the pages that matter and compared month to month, so a regression after an update or a new plugin is caught early. A link and status sweep then flags internal and outward links that now return errors, redirects left behind after pages move, and 404s on paths search engines still point at.

Search visibility checks follow: sitemap and indexing health, titles and descriptions dropped during an update, and analytics that stop recording because a tag was overwritten. These are checks and small corrections, not an SEO campaign. Keyword strategy, new content and link building sit outside the plan as separate work.

See what monthly maintenance support covers.

Where the Plan Stops: Not Insurance, Not a Retainer

Everything above is the plan. What sits outside it matters just as much.

A care plan is not insurance. It does not underwrite lost revenue, compensate you for an outage, or warrant that your site stays online, ranks, or converts. Nor is it a retainer for new work: extra pages, rewritten copy, design changes, campaign landing pages, new integrations and email automation builds are quoted separately rather than absorbed into the monthly fee.

Buyers usually learn the rest of the exclusions late: content edits beyond a stated allowance, outages on a third-party platform, changes another contractor has made, and urgent help outside support hours. Response times and coverage windows are plan terms, not universal standards, so "within 24 hours" can mean very different things from one provider to the next.

That boundary is healthy. A plan promising everything is either priced for everything or quietly delivers less, and a defined list is easier to hold someone to. For the specifics of what is included, answers on plan scope are worth reading before you sign.

Doing It Yourself Versus Paying for a Care Plan

If you accept that boundary, the remaining question is whether to handle website maintenance yourself. Self-maintenance genuinely requires secure logins, a calendar with reminders, a staging environment or at least a tested backup, and the willingness to learn what a deliverability record or a certificate error means when one appears. It saves the monthly fee and costs owner attention. The usual failure is not incompetence but a skipped month during a busy season.

It holds up for a small brochure site on a stable stack, with someone technical in-house and a habit of running the same checks on the same day each month. It tends to slip on booking-driven sites, sites taking payments, a single owner-operator with no backup person, and any site nobody has logged into since launch. Rather than judging the fee alone, ask what a rebuild or a lost booking window would cost, then weigh that against the fee. You can also see what ongoing care covers before deciding.

What to Ask Before You Buy a Monthly Plan

If you have decided the monthly fee is easier than owning the checks, the next step is comparing providers on substance. Put these questions in writing before you sign.

Ask for the checklist

Request the full list of included items, the frequency of each, and which are conditional on your platform or site type. If a provider cannot supply it, nothing else matters.

Ask when and how you are told

Ask whether you receive a monthly written summary, alerts only when something breaks, or silence. Get the named contact and their direct details.

Ask what happens on failure

Confirm whether fixes are included, what counts as an incident rather than new work, and what response window the terms state.

Ask what is quoted separately, and what the exit looks like

Get the notice period, final backup handover, and written confirmation that domain, hosting, and platform accounts remain in your name.

Ask about reporting

If search visibility matters to you, ask how performance is reported. Formvant's optional monthly care plans include SEO and analytics reporting, alongside fixed-scope packages from $995 CAD; apply the same questions to any provider.

With answers in hand, you can compare any plan against another, and against doing it yourself.

Conclusion: The Checklist You Should Be Able to See

The Checklist Is the Product

If you cannot see which checks run and how often, you cannot compare one plan against another, or against doing the work yourself. Judge each line by its failure mode: updates, backups, form and booking tests, deliverability, certificate and renewal dates, speed and broken links all guard something you would not notice breaking until a customer told you.

Know the edge of the plan before you sign. A care plan is monthly checks on silent failures, not insurance against loss and not a retainer for new pages, copy, or campaigns.

Then decide with five questions in hand: what is included, how often it runs, what you are told afterwards, and what gets quoted separately. A plan that answers all four is one you can hold to account.