What website maintenance includes and why it matters

Website maintenance covers the regular work that keeps a website secure, working and up to date after launch: updating its software, taking and testing backups, monitoring for downtime and errors, and making small content and design changes. Good website maintenance services are mostly invisible when they work. When maintenance is skipped, problems build up quietly until a site is hacked, breaks after an update or loses data with no way to recover it.

This guide explains what maintenance usually includes, so you can judge what you are paying for and what to ask a provider. It applies to most business websites, whether they run on WordPress or another content management system (CMS), or are custom-built. If you would like help looking after your site, our website service page explains how we work.

Updates to software, plugins and servers

A website is built from many pieces of software, and each receives updates for security, bug fixes and new features.

1. Core software. The CMS or framework the site is built on. For WordPress, the official hardening guide notes that older versions are not maintained with security updates.
2. Themes and plugins. Each adds its own code and its own updates. Unused ones should be removed rather than left to age.
3. Server software. The operating system, web server and PHP version on the hosting server. PHP publishes which versions still receive fixes on its supported versions page.
4. Third-party services. Payment gateways, email services and other integrations occasionally change how they work, and the site must keep up.

Updates should not be applied blindly. A careful maintenance process:

• Checks what each update changes.
• Tests important updates on a staging copy, a private copy of the site, before applying them to the live site.
• Takes a backup before updating.
• Checks key pages and forms afterwards.

WordPress also supports automatic updates for individual plugins and themes. These can be useful for lower-risk plugins, while critical ones, such as store or booking plugins, are often better updated manually after testing.

Who applies server updates depends on your type of hosting, as our comparison of shared hosting and a VPS explains.

Backups and restore tests

Backups are copies of the website's files and database, taken regularly and stored safely.

1. Back up both files and the database. Both are needed to restore a working site.
2. Store backups away from the website's server, so they survive if the server fails or is compromised.
3. Keep several versions, so you can restore from before a problem started, even if it went unnoticed for a while.
4. Match the frequency to how often the site changes. A store taking orders every day needs more frequent database backups than a brochure site updated once a month.
5. Test restores regularly. Restore a backup to a staging site to prove it works. A backup that has never been restored is only a hope.

Ask your provider how often backups run, where they are stored, how long they are kept and when a restore was last tested.

Uptime and error monitoring

Monitoring means finding out about problems before your customers do.

• Uptime monitoring checks the site regularly and alerts someone if it stops responding.
• Error monitoring records problems in the site's code, such as failed pages or broken forms, so they can be fixed.
• Security monitoring can alert you to suspicious activity, unexpected file changes or new admin accounts.
• Form and email checks confirm that enquiries and order emails are still being delivered.
• Certificate and domain monitoring warns before a security certificate or domain name expires.
• Performance checks spot pages that have become slower over time.

The value of monitoring depends on who receives the alerts and how quickly they respond. Agree response times, especially for urgent problems like the site going down.

Speed is worth checking too, and our guide to Core Web Vitals explains the three measurements to watch.

Small content and design changes

Many maintenance plans include a set amount of time for small changes each month.

• Updating text, prices, opening hours or team details.
• Adding or replacing images.
• Adding a new page based on an existing template.
• Small layout adjustments or fixes on particular devices.
• Adding a new form field or changing where form messages are sent.

Larger work, such as a new feature, a new section or a redesign, is usually quoted separately. Check how the plan defines "small" and what happens to unused time.

What happens when website maintenance is skipped

Skipping maintenance saves money in the short term, but the risks grow over time.

1. Security weaknesses stay open. Outdated software with known weaknesses is a common way into business websites.
2. Updates become harder. A site many versions behind is riskier to update than one kept current, and may need significant work.
3. Compatibility problems appear. Hosting providers upgrade server software, and old code can stop working without warning.
4. Data can be lost. Without tested backups, a server failure or attack can mean rebuilding from scratch.
5. Problems go unnoticed. Broken forms and failed emails can lose enquiries for weeks before anyone realises.
6. The site slows down. Unused plugins, growing databases and outdated software gradually reduce performance.

Our guides on why your website is slow and how to speed up a slow WooCommerce store explain how speed problems build up and how to fix them.

Questions to ask a maintenance provider

1. Which software do you update, how often, and do you test on staging first?
2. How often are backups taken, where are they stored and when was a restore last tested?
3. What do you monitor, who receives alerts and how quickly do you respond?
4. How much time for small changes is included, and how is larger work quoted?
5. Who owns the hosting, domain and admin accounts?

Summary

• Maintenance includes updates to core software, themes, plugins, server software and integrations.
• Backups should cover files and database, be stored off the server, kept in several versions and tested.
• Monitoring should cover uptime, errors, security, forms, certificates and performance, with clear response times.
• Many plans include small content and design changes, with larger work quoted separately.
• Skipping maintenance leaves security holes, makes updates harder and risks losing data and enquiries.

Regular maintenance keeps a website safe, fast and ready to do its job. If you'd like help looking after your website, you can tell us about it here.