Fast. Simple. No meetings. No delays.
Home / Blog / Australia / What a Website Maintenance Plan Should Include

What a Website Maintenance Plan Should Include

Updates, backups, monitoring, security and small fixes: what a maintenance plan should cover and what to ask a provider.

Cover graphic for the article: What a Website Maintenance Plan Should Include

A good website maintenance plan covers six things: software updates, tested backups, uptime and error monitoring, security checks, small content or code fixes, and clear reporting. If a provider cannot tell you plainly how each one is done and who is responsible, you are buying a promise, not a service. Use this checklist to compare plans.

Why unmaintained sites fail

A website is not a printed brochure. It runs on software that depends on other software: a content system or framework, plugins or packages, a web server, a database, a certificate and a domain. Each piece changes over time, and when updates are ignored, three things tend to happen.

  • Security holes stay open. Known weaknesses in old versions are publicly documented and routinely probed by automated tools.
  • Things break quietly. A form stops sending, a payment step errors, a certificate expires, and nobody notices until a customer tells you.
  • Updates become risky. The longer you wait, the bigger and more disruptive the eventual jump, which is how a minor job becomes a rebuild.

Maintenance is mostly about preventing surprises. The sections below describe what to expect for each part.

Updates and patching

Ask what gets updated, how often, and how updates are tested before they reach your live site. A sensible plan includes:

  • The core platform or framework, themes, plugins and third-party libraries.
  • The server software and language runtime, if the provider also hosts the site.
  • Security updates promptly, and routine updates on a regular schedule.
  • A staging copy where updates are tried first, with a quick check of key journeys such as the contact form, checkout and login.
  • A way to roll back if an update causes a problem.

Be wary of anyone who applies updates straight to the live site with no testing, or who never updates for fear of breaking things. Both are signs of fragile work. If your site is built on an old platform, the guide to upgrading an old PHP application explains how to catch up safely.

Backups you have tested

A backup you have never restored is a hope, not a backup. Check these points:

  1. What is backed up. Both files and the database, plus uploaded media and configuration.
  2. How often. Frequency should match how often your site changes. A shop taking orders needs more frequent copies than a static brochure site.
  3. Where copies are stored. At least one copy should be somewhere separate from the live server, so a single failure cannot take both.
  4. How long they are kept. You may need to go back further than yesterday, for example after a slow-burning problem.
  5. Restore tests. Ask when a restore was last tried, and ask the provider to run one and show you the result.

Know also who can trigger a restore and how quickly, because that is what matters on a bad day.

Uptime and error monitoring

Monitoring tells you when something is wrong before your customers do. There are two layers worth asking about:

  • Uptime checks that request your site regularly from outside and alert someone if it does not respond.
  • Error and performance monitoring that records failures inside the application, such as a broken checkout step or a slow page, so they can be investigated.

Ask who receives the alerts, during which hours, and what the expected response is. An alert that goes to an unattended inbox does nothing. Also ask for monitoring of the things that expire: domain registration, security certificates and hosting renewals. Lapsed renewals are one of the most avoidable causes of an outage.

Security scanning

Security work in maintenance is mostly routine hygiene, not dramatic response. It should include:

  • Scanning for known vulnerable components and malware.
  • Reviewing user accounts, especially administrators, removing old ones and enforcing strong passwords and two-factor sign-in.
  • Checking that sensitive settings, such as file permissions and admin areas, are configured safely.
  • A plan for what happens if the site is compromised: who cleans it, how you are told, and whether affected customers need notifying.

The web application security checklist goes into more of the underlying practices. If you handle personal information, check your current legal obligations with the official regulator or a qualified adviser.

Content changes and small fixes

Plans differ most on this point, so read the wording closely. Clarify:

  • Whether small content edits, such as text changes, new staff photos or banner updates, are included or charged separately.
  • How you request changes: a ticket system, email, or a shared board, and the usual response time.
  • What counts as a small fix versus new work that needs a quote.
  • Whether any hours are included, whether unused hours roll over, and how extra work is billed.

If your site changes often, a plan that includes a pool of hours may be better value than a bare technical plan with hourly add-ons. The article on maintenance retainers discusses when that model pays off.

Questions to ask before you buy a website maintenance plan

  • What exactly is included, written down, and what is excluded?
  • Who does the work, and who covers when they are away?
  • Do I hold the hosting, domain and code accounts in my name?
  • Can you show a sample monthly report?
  • What is the notice period if I want to leave, and what hand-over do I get?
  • How are emergencies handled outside normal hours?

Pricing varies a lot with the size, platform and risk of the site, so ask providers to quote against the same written scope rather than comparing headline prices.

Putting it together

Match the plan to the site. A simple brochure site needs updates, backups and a monitored certificate. An online shop or booking system needs tighter monitoring and faster response. Whoever you choose, keep ownership of your accounts and insist on seeing proof the backups work. If you want a plan scoped for your site, start from our page on software development for Australian businesses or the contact page.

Frequently asked questions

How often should a website be updated?

Security updates should be applied promptly after testing, and routine updates on a regular schedule such as monthly. The right rhythm depends on the platform and how much of your business runs through the site. Avoid long gaps, because large catch-up updates are riskier than small frequent ones.

What does website maintenance usually cost?

It varies with the platform, the size of the site, how critical it is and how much support and content change you need. Rather than relying on a typical figure, ask providers to quote against one written scope covering updates, backups, monitoring, security and included hours.

Can I maintain it myself?

Sometimes. If you are comfortable with updates, backups and testing, a simple site can be self-managed. The risk is that tasks get skipped when you are busy. Set a calendar routine, keep a staging copy, test restores, and know when to ask a developer for help.

Related articles

🚀 Start Now