Australian Website Design Measured figures. Named sources.
Menu Close

Maintenance

The annual review a small business site needs

An annual website review checklist catches exactly what a monthly maintenance task list is not built to notice — because nothing on it breaks visibly.

Routine monthly maintenance is built to catch things that break — a failed update, a lapsed backup, an outage. It is not built to notice things that were never broken in the technical sense, and simply drifted slowly out of date over a year of small, individually unremarkable changes. A fixed, once-a-year review exists specifically to catch that second category, which monthly tasks routinely miss by design.

Why a monthly checklist misses this by construction

A monthly task list checks the same specific things every month — did the update apply, did the backup run, is the site up. None of those questions surface a team page listing someone who left eight months ago, a design that has quietly aged against current visitor expectations, or a competitor who has moved meaningfully ahead on a feature the site does not offer. These are not failures a monthly technical checklist is designed to detect, because they are not technical failures at all.

What an annual website review checklist should actually cover

Content accuracy across the whole site, not just recently touched pages — every service description, every price, every team member, checked against current reality rather than assumed correct because nobody has complained. A visual and competitive check, comparing the site honestly against current visitor expectations and against what competitors are now doing, without assuming a design that looked current at launch still does. A full renewals audit, cross-checked against the consolidated list covered in renewals: domain, hosting, licences and certificates, catching anything that has quietly drifted since the list was last updated. A genuine backup restore test, not merely a confirmation that backups exist — see website backups that actually work for why this specific check matters more than almost anything else on the list. An access review, confirming which accounts still have any level of access to the site and removing anything no longer needed, covered in passwords, accounts and who has access. A live contact-form test, actually filling in and submitting the enquiry form to confirm it still arrives somewhere someone reads, since a form that has silently stopped delivering fails with no visible symptom on the page itself. A website analytics check, confirming tracking is still firing correctly rather than assuming a dashboard showing months of near-zero traffic reflects the site’s real performance rather than a broken tracking code nobody noticed.

Why once a year is the right cadence for this, specifically

More frequently than annually and the review becomes indistinguishable from routine maintenance, losing the specific value of stepping back and looking at the whole site freshly rather than task by task. Less frequently, and genuine drift accumulates for long enough to become materially harder to fix — a site reviewed only every three or four years often needs something closer to a redesign than a review by the time anyone looks properly.

Whose job this actually is

Unlike routine technical maintenance, an annual review benefits from a perspective genuinely willing to say a design has aged or a section is no longer working, which can be harder for a party embedded in routine month-to-month upkeep to raise unprompted. Whether this is done by the existing maintenance provider or brought in separately, it should be a deliberate, calendared event rather than something that happens only if someone happens to remember.

What to do if a site has never had one

Book it now, regardless of how long it has been running. The purpose is not to find fault with what exists — it is to surface the accumulated small things nobody has been specifically looking for, and the earlier that happens relative to how long the site has been live, the less there typically is to fix.

Timing the review around the business’s own calendar

Scheduling the annual review at a genuinely quiet point in the business’s own year, rather than during its busiest trading period, gives whoever conducts it the attention needed to do it properly, and makes it more likely to actually happen on schedule rather than be deferred indefinitely by more pressing seasonal demands.

A simple review template beats starting from scratch each year

Keeping a consistent checklist from one year’s review to the next makes each subsequent review faster and more comparable — a business can see not just the specific areas for improvement flagged this year, but how the site has changed since the previous review, which is useful information in its own right.

Who should conduct it

Either the existing maintenance provider or an independent reviewer can perform this check competently, provided whoever does it is genuinely willing to flag problems rather than simply reassure — a review conducted by someone with an incentive to avoid identifying their own past shortcomings is worth treating with proportionate scepticism.

What “genuinely fresh eyes” catches that routine attention misses

Someone reviewing a site for the first time notices things a person who looks at it every week has stopped seeing entirely — an outdated photo, an awkward sentence, a design element that felt current three years ago and now reads as dated. This is precisely why the review benefits from a perspective outside routine day-to-day maintenance, even where the same provider ultimately performs both.

A short way to measure whether the review is working

Comparing this year’s findings against last year’s is itself informative — a shrinking list of issues each year suggests the underlying maintenance between reviews is genuinely effective, while a list that stays constant or grows suggests something in the routine process between reviews is not catching what it should.

Where to go from here

Where an annual review reveals the site has drifted far enough that patching is no longer the right answer, when maintenance becomes a redesign sets out how to tell the difference. And what a small business’s overall build and upkeep should look like is set out on small business website design.

Evidence for this page

This page exists because the demand below was measured, not assumed. The figures are search-market data about the topic — they are not prices.

Entity this page targets
annual website review checklist
Measured Google volume
no data
Keyword difficulty
no data
Advertiser cost per click
no data
AI assistant volume
no data
Advertiser competition
no data
Measured on
3 August 2026
Search results inspected for intent
No

Source: research/outer-volume-au.json · DataForSEO Google Ads search_volume and Labs bulk_keyword_difficulty, location_code 2036 (Australia), language en · pulled 3 August 2026.

Provenance

Written by Australian Website Design. Published 2026-08-03, last updated 2026-08-03.

Sources

  • Outer-cluster demand measurement (this site) — research/outer-volume-au.json