Website maintenance: what it actually involves
See what website maintenance covers in practice, from updates and backups to routine checks and content changes, and why sites need ongoing care.
"Maintenance" is one of those words on an invoice that makes people suspicious. The site is built. It works. What exactly is being maintained?
Fair question. A website looks like a finished object, but it behaves more like a vehicle. It runs on parts made by other people, on roads that keep changing, and it needs regular attention to stay roadworthy. Here is what that attention consists of.
Why a finished website does not stay finished
Nothing about your site changes on its own, yet everything around it does.
- Browsers and phones update constantly, and something that displayed perfectly two years ago can look slightly off on a new device.
- The software your site runs on gets security fixes. Skip them and you are running a version with known holes.
- Add ons made by third parties get abandoned, bought out or changed.
- Services your site connects to (maps, booking tools, payment providers, social feeds) alter how they work, and the connection breaks.
- Your own business moves on. Prices rise, staff leave, the opening hours shift for winter.
A site left alone for three years is rarely broken in one dramatic way. It is worn in a dozen small ones.
The four parts of maintenance
Updates
If your site runs on a content management system such as WordPress, it is made of layers: the core software, a theme that controls the look, and plugins that add features. Each layer is updated separately, sometimes weekly.
Applying updates sounds like pressing a button, and often it is. The skill is in what happens around the button. A careful maintainer takes a backup first, applies updates in a sensible order, then checks the site still works, because now and then an update to one part clashes with another and a form stops sending or a page layout falls over.
Sites built as simple static pages, or on hosted builders, need far less of this. That is worth knowing when you compare the cost of looking after different kinds of sites.
Backups
A backup is a full copy of the site, taken regularly and kept somewhere separate. Maintenance means making sure backups are happening, checking they are complete, and now and then confirming that one can actually be restored. A backup nobody has tested is a hope, not a plan.
Checks
This is the unglamorous part, and the part most often skipped. Someone should regularly confirm that:
- The site is up, and somebody gets alerted if it goes down.
- The contact form delivers to the right inbox. Forms fail silently, and a silent form means lost enquiries you never hear about.
- The security certificate is valid.
- Pages load at a reasonable speed on a phone.
- Links and buttons go where they should.
- The domain and any paid licences are not about to expire.
Content changes
The small edits that keep the site true: a new team member, a changed phone number, a public holiday notice, a service you no longer offer, fresh photos of the last job. Some businesses do these themselves. Others send a quick email to whoever looks after the site. Either is fine, as long as it happens.
What a normal year looks like
To make this concrete, say you run a small accounting practice with a ten page site. Over twelve months, decent maintenance might look like this:
- Every week or so: software updates applied and checked, backups running in the background, uptime monitored automatically.
- Every month: a test enquiry through the form, a quick look over the main pages on a phone, a glance at the visitor numbers.
- A few times a year: content tweaks as things change, such as new tax time hours or an updated staff page.
- Once a year: a proper review. Is everything still accurate? Are any add ons no longer needed? Are the domain, hosting and certificate all in order? Has a backup restore been tested?
None of that is dramatic. That is the point. Good maintenance is a string of boring months.
What happens when nobody does it
The usual story goes like this. A site is launched and left. Updates pile up. After a couple of years an outdated plugin with a known weakness gets found by an automated attack, and the site starts redirecting visitors to somewhere unpleasant. The owner finds out when a customer rings to mention it. There is no recent backup. The clean up costs more than several years of maintenance would have.
The quieter version is more common. Nothing is hacked. The form simply stopped delivering eight months ago after an email setting changed, and the business has been wondering why the phone is quiet.
Who should do it
You have three realistic options.
- Do it yourself. Workable if you are comfortable with the software and will actually set aside time each month. Be honest about the second part.
- Pay as you go. Call someone when something breaks. Cheapest in a good year, expensive in a bad one, and nothing gets prevented.
- A regular care arrangement. Someone is responsible, on a schedule, for a known fee.
Whichever you choose, make sure one question has a clear reply: if the site goes down or a form stops working, whose job is it to notice? If you find yourself saying "nobody, really", that is the first thing to fix.