Blog / How the internet works /

Website maintenance plans: what they should include

A website is not a poster you put up once. It’s closer to a shop that needs the lights on, the shelves tidy and the locks working. Left alone, it slowly breaks: a plugin goes out of date, a certificate expires, a form stops sending, and nobody notices until a customer does.

A maintenance plan is the agreement that someone will stop that from happening. But plans vary wildly. Some are a monthly invoice for very little. Others are exactly what a business needs. Here is what a good plan should include, and how to read one before you sign.

What maintenance is for

It has four jobs:

  1. Keep the site working. Pages load, forms send, checkout completes.
  2. Keep it safe. Updates applied, access controlled, threats watched.
  3. Keep it recoverable. If something goes wrong, you can restore it.
  4. Keep it healthy over time. Speed, search visibility and content don’t quietly decay.

Everything in a plan should serve one of these.

The core items

1. Backups, and tested restores

Automatic backups, stored away from the web server, and kept for a reasonable period. The part cheap plans skip: someone actually tests a restore now and then. A backup you’ve never restored is a hope, not a backup.

Ask: how often, where are they stored, how long are they kept, and who restores them?

2. Updates

For WordPress, that means core, themes and plugins. For other platforms, theme updates and app or extension updates. Updates should be applied on a schedule, ideally tested on a staging copy first for anything that touches checkout or forms, and with a backup beforehand.

Shopify handles the platform itself, but themes and apps still need attention.

3. Security

  • Firewall or security tool where it makes sense
  • Malware scanning
  • Strong passwords and two-factor login
  • Review of user accounts and permissions
  • Removal of unused plugins, themes and users
  • Clear steps if the site is hacked

4. Uptime monitoring

A tool that checks your site every few minutes and alerts someone if it goes down. A plan should say who gets the alert and how fast they respond. The details of one setup are in the uptime monitoring setup I use for client sites.

5. SSL, domain and DNS

SSL certificates renewing, domain renewal dates tracked, and DNS records documented. A lapsed domain or certificate takes a whole site down.

6. Performance checks

Regular speed tests on key pages, image sizes, caching, and a look at heavy scripts. Sites slow down gradually as plugins, tracking scripts and large images pile up.

7. Functional checks

A routine check that the things that earn money still work: contact forms, newsletter sign-ups, checkout, booking forms, login. This is the one that catches problems before customers do.

8. Basic search health

Search Console checked for indexing errors, security issues and manual actions. Sitemap still valid. Broken links and obvious redirect problems fixed. This doesn’t mean ongoing SEO strategy, which is separate work, but it catches technical damage.

9. Reporting

A short, plain report each month or quarter: what was updated, what was fixed, what needs a decision. If you can’t tell what you’re paying for, you can’t judge it.

10. Support and response times

How do you contact them, and how quickly do they reply? Is there a difference between an emergency (site down) and a normal request?

Things that are often missing

Look for these gaps in cheap plans:

  • No restore testing.
  • No staging. Updates applied directly to the live site.
  • No monitoring, so the first alert is a customer.
  • No clear scope. “Minor changes” with no definition leads to arguments later. I wrote about how to define a sensible website maintenance scope.
  • No documentation of what’s on the site and who has access.
  • Plugins and accounts held in the provider’s name, not yours.
  • No exit plan. If you leave, can you take everything?

What’s usually not included

It’s reasonable for a standard plan to exclude:

  • New features or redesigns
  • Writing and publishing content
  • Ongoing SEO campaigns
  • Recovery from a serious hack caused by neglect before the plan began
  • Third-party service problems outside the provider’s control

That’s fine, as long as it’s written down and you know what each costs. If you want to understand how work is structured, retainers or projects explains the two models.

Questions to ask before you sign

  1. What exactly is included each month? Ask for the list.
  2. How are backups handled, and when were they last tested?
  3. Do you use a staging site for updates?
  4. What’s your response time for an emergency?
  5. Who owns the accounts? Hosting, domain and platform accounts should be in your name.
  6. What happens if the site is hacked or goes down? Is recovery included or extra?
  7. Will you send regular reports?
  8. Can I cancel, and can I take my site and documentation?
  9. Who actually does the work, and who covers when they’re away?
  10. What’s not covered?

A good provider answers these without fuss. A vague answer is information too.

Matching the plan to the site

Not every site needs the same plan.

  • A simple brochure site may only need backups, updates, monitoring and annual renewals.
  • A site with forms, bookings or memberships needs functional checks and tighter security.
  • An online shop needs everything above plus careful handling of updates around checkout, stock and payments, and extra attention before busy trading periods.
  • A content site benefits from performance checks, plugin audits and regular search health reviews.

If you run a shop, avoid scheduling big changes just before a sale or holiday. Tell your provider your peak dates in advance.

If you do it yourself

A plan doesn’t have to be a paid service. If you maintain your own site, write the same list down and put it on a calendar: weekly checks, monthly updates and reports, quarterly access and restore tests. A WordPress maintenance checklist for site owners is a good starting point, and a useful maintenance log will save you hours the first time something breaks.

Key takeaways

  • A good plan covers backups with tested restores, updates, security, monitoring, domain and SSL, performance, functional checks, light search health and reporting.
  • The common gaps are restore testing, staging, scope and ownership.
  • Match the plan to the site: a shop needs more than a brochure site.
  • Own your accounts and keep documentation.

If you already pay for maintenance, can you list what you get each month? If not, ask for it this week.