How often does a website actually need updating?
Separating the updates that matter from the ones that do not: security patches, content, design refreshes, and how often each genuinely needs doing.
“How often should we update the website?” gets answered badly in both directions. Agencies say constantly, because that is a retainer. Owners say never, because the site looks fine.
The honest answer is that four different things are being called “updating” and they run on completely different clocks.
Security updates: monthly, and urgently when told
This is the one with an actual deadline, and it is not negotiable.
On a platform with plugins, monthly is the right rhythm, with same-week action on anything flagged as actively exploited. The overwhelming majority of compromised small business sites were running a known vulnerable plugin with a patch available. Not a clever attack. A patch nobody applied.
On a static site there is far less to do, because there is no server-side code executing on request. That is most of the security argument in static versus WordPress, and it is why the maintenance cost differs so much between the two.
Either way this happens on a schedule, on staging first, whether or not anything looks wrong.
Content: whenever it stops being true
Not on a schedule at all. The trigger is reality changing.
Prices, hours, staff, services, the phone number. Wrong content on a website costs you more than an old design does, and it is the cheapest thing on this list to fix. A quarterly ten-minute read of your own site catches almost all of it.
The one genuinely scheduled piece here is anything with a date in it. Copyright years, “serving Alberta since,” seasonal notices. These age visibly and make an otherwise current site look abandoned.
Publishing: only if you have something to say
Somewhere between “post weekly for SEO” and never, the truthful position is that publishing helps when the articles answer questions your customers actually ask, and does nothing when they exist to hit a cadence.
Four genuinely useful articles a year beat twenty thin ones. Thin content does not just fail to help; it gives search engines more pages of nothing to associate with you.
If you cannot think of anything to write, that is a sign to stop, not a sign to outsource it.
Design: every four to six years, and only for a reason
Design refreshes are the most over-sold and the least urgent item here. A site that loads fast, works on a phone and says the right things is doing its job, whatever year it looks like.
The reasons that genuinely justify a rebuild:
- It does not work properly on a phone. This is a real problem, not a taste one.
- It is slow enough that people leave before it loads.
- The business has changed and the site describes the old one.
- Nobody can update it without a developer, so it has gone stale.
- It is on software that no longer gets security updates.
“It looks a bit dated” is on nobody’s list of reasons a customer went elsewhere.
The schedule, in one place
| What | How often |
|---|---|
| Security patches | Monthly, urgent when flagged |
| Backup restore test | Quarterly |
| Contact form test | Quarterly |
| Content accuracy read | Quarterly |
| Dependency and licence review | Yearly |
| Design and structure review | Every four to six years |
The quarterly form test is on that list for a reason. It is fifteen seconds of work and it is the item that most often turns out to have been silently broken.
What this means for what you pay
A static marketing site genuinely needs very little: monitoring, a quarterly check, and someone available when you want a change. A plugin-heavy site needs real monthly attention and costs accordingly. Neither of those is a scandal, but you should know which one you are buying.
The failure to avoid is paying a monthly fee for the first thing and receiving nothing, which is common enough that it is worth knowing what a plan should contain.
If you are not sure which category your site is in or what it needs, tell us what it runs on and you will get a straight answer, including “yours is fine, leave it alone” when that is true.
Related: inheriting a site nobody maintained, what hosting actually costs, and our maintenance and support work.
Further reading
Topics in this article
Get new articles by email
One email when something new goes up, roughly twice a month. Plain writing on what software costs and what is worth building. No sequences, no sales calls, and one click to leave.
Keep reading on the same subject
-
Inheriting a website nobody has maintained
A first-week checklist for a site you just became responsible for: what to secure, what to back up, and what to leave alone until you understand it.
Work through week one -
What a website maintenance plan should actually include
Most maintenance retainers bill for watching a dashboard. What a plan should cover, what it should cost, and the clauses worth refusing to sign.
See what to insist on -
Your developer disappeared. Here is what to do first
A practical recovery order when the person who built your software stops replying: what to secure, what to prove you own, and what to rebuild.
Start the recovery