Website maintenance

What maintenance actually is

A website is not a brochure that gets printed once. It is running software — a CMS core, plugins or apps, a theme, a hosting stack underneath all of it — and running software accumulates small failures if nobody looks at it. Maintenance is the ongoing work of looking at it: applying updates, checking backups exist and restore, and watching that the site is actually up. It also means fixing the small breakages that follow a supplier’s own update, rather than anything you did.

“Website maintenance” measures 75 AI-assistant prompts a month in Australia against no measurable Google search volume at all — recorded 31 July 2026 in research/ai-vol-keywords.json. That gap is worth sitting with. People are not typing this into a search box; they are asking an assistant, in their own words, after they have already noticed something is wrong or after a supplier has mentioned it in passing. The market for this content is real and it looks nothing like a keyword chart.

What is here

What website maintenance actually covers — the actual task list behind the word, separated from the marketing language wrapped around it.

What happens if nothing is maintained — not a dramatic failure on day one, which is exactly why the risk gets underestimated.

Updates, and who is responsible when one breaks something — updates break things too, which is the argument for a schedule and a named owner, not either extreme.

The post-launch warranty period — what a supplier typically covers for free immediately after launch, and where that cover actually ends.

Retainer, hourly or ad hoc — three different commercial shapes for the same underlying work, and which businesses each one actually suits.

What a maintenance report should contain — a report full of green ticks is not the same thing as a plan that has ever been tested by a real failure.

Keeping content current after launch — a site can be technically perfect and still tell customers something that stopped being true a year ago.

Renewals: domain, hosting, licences and certificates — four separate things that lapse on four separate schedules, and the one list that tracks all of them.

The annual review a small business site needs — a fixed, once-a-year check that catches what a monthly task list is not built to.

When maintenance becomes a redesign — the point where patching an old site costs more than starting again, and how to actually tell.

Website insurance, warranties and what they cover — a genuinely narrow category, easily confused with an ordinary maintenance retainer.

Handing maintenance to a new supplier — what has to move, in what order, so nothing is dropped between one provider and the next.

Who holds the keys to your website — the accounts audit worth doing while nothing is wrong, not after.

What website maintenance services check monthly: regular uptime checks, monitoring, updates, security, broken links, accessibility and performance optimisation

A maintenance plan or maintenance service worth paying for runs a recurring checklist on a regular schedule, not just a vague promise to keep a site up-to-date. That means security updates and theme updates applied on a schedule, not left to accumulate. It means uptime and performance monitoring that catches the site being down or measurably slower before a customer reports it. It means a broken-links check, since links break quietly as other sites restructure their own URLs. And it means basic accessibility checks, so a site does not quietly drift out of compliance as content gets added. Performance optimisation — image compression, caching, removing what a plugin left behind after it was deactivated — is routine maintenance work, not a separate, occasional project.

Security, vulnerabilities, technical web development and why WordPress-specific maintenance looks different

WordPress maintenance specifically has to track plugin and theme vulnerabilities as they are disclosed, not just apply updates on a fixed monthly schedule regardless of urgency. A critical security patch for a widely used plugin needs applying within days, not at the next scheduled monthly check. Web development and technical maintenance overlap here. Fixing an outdated, vulnerable plugin is sometimes a five-minute update, and sometimes small development work if the site’s other components depend on the outdated behaviour being replaced.

What a maintenance report should actually show

Errors, issues and outdated components found and fixed, security updates applied, and uptime for the period and any downtime incidents. Add a plain-language note on anything that needs a decision above what the maintenance service can approve unilaterally, per month. We recommend treating a report with nothing in it, month after month, as a prompt to ask what is actually being checked, not as reassurance the site needs nothing.

The honest version of this section

A meaningful amount of what is sold as “maintenance” to small businesses is closer to a subscription for peace of mind than to an itemised set of tasks. A report full of green ticks is not the same thing as a plan that has ever actually been tested by a real failure. This section names which parts of the pitch are genuinely load-bearing and which are decoration. That distinction is what this site exists to make plainly, rather than leave to the sales conversation. What it costs to have properly done is a separate, priced question, answered on what website maintenance costs. For where maintenance sits inside web design as a whole, start with web design in Australia.