Website Maintenance: What Should a Monthly Plan Include?
A useful monthly maintenance plan covers five things: applying security fixes when they are actually needed, making backups you have actually tested, watching for security and availability problems, checking that the site still does its job – forms, search visibility, speed, tracking – and handling small content changes. Some tasks belong in a quarterly or yearly rhythm instead, and new features are a separate budget. Below is what each part involves, so you can judge a maintenance offer or organise the work yourself.
Why a website needs regular maintenance
A site that nobody touches still changes underneath. The software it runs on receives security fixes and eventually stops being supported; certificates expire; forms stop delivering emails after a mail server change; prices and opening hours go out of date. Most of these problems are cheap to catch early and expensive to discover when a customer tells you about them.
Two examples of the timelines involved:
- Server software – PHP, the database, the web server – has published support periods (php.net lists them for PHP), after which a version receives no more security fixes. That is no reason to upgrade a working site every time a new version appears. It is a reason to know which version the site runs on and what is exposed to the internet, and to upgrade when there is a real reason: a vulnerability that actually affects the site, a hosting provider dropping the old version, or a feature you need.
- TLS certificates – the padlock in the browser – are getting shorter lives. Let's Encrypt, a widely used free certificate authority, plans to move its default certificates from 90 to 64 days on 10 February 2027 and to 45 days on 16 February 2028, following CA/Browser Forum requirements. It says manual renewal is not recommended and advises monitoring that alerts you if a certificate is not renewed when expected.
The monthly core
1. Updates
- security fixes applied where they fix something that affects the site – tested on a copy first; no upgrades just for a newer version number;
- unused plugins and themes deleted, not just deactivated;
- server software (PHP, database, web server) checked: which versions run and whether a known vulnerability concerns the site;
- a short check after each update: home page, a key service or product page, the forms, the admin panel.
WordPress's own security guidance says to keep WordPress up to date because older versions are not maintained with security updates, to keep plugins updated, and to delete plugins you are not using. A custom-built site with few external libraries is a different case: if it works and no known vulnerability affects it, the right move is usually to leave it alone.
2. Backups – and a restore test
A backup you have never restored is a hope, not a backup. CISA, the US Cybersecurity and Infrastructure Security Agency, recommends the 3-2-1 rule: three copies of important files, on two different types of storage media, with one copy stored off-site. It also advises a backup solution that runs automatically, testing that data can be restored both fully and partially, and being able to roll back at least seven days. For a website that means:
- files and database backed up automatically, as often as the content changes;
- at least one copy stored outside the hosting account;
- an occasional restore to a test environment – and someone who knows how long a restore takes.
3. Security and uptime
- uptime monitoring with alerts that reach a person, not an unread mailbox;
- certificate expiry and domain renewal dates checked;
- the Security issues report in Google Search Console reviewed – Google reports hacked content, malware and social engineering there, and affected pages can appear with a warning in search results or behind a warning page in the browser;
- admin accounts reviewed: former employees and contractors removed, two-factor authentication switched on where available;
- server and application error logs scanned for new or repeated errors.
4. Does the site still do its job?
- Forms: send a real test enquiry and confirm that it arrives where it should. Forms that silently stop delivering are among the most expensive failures, because nobody notices them.
- Search visibility: in Search Console, check the page indexing report and any new errors, and watch for 404 pages that need a redirect. When we moved our own site to two domains, we set up around 45 permanent (301) redirects; old links and bookmarks keep arriving for years, so this check never quite ends.
- Speed: look at Core Web Vitals for the main page types and investigate sudden changes – the cause is often a new plugin, a large image or a third-party script. Our article on what to check on a slow website before changing hosting explains how.
- Tracking and consent: confirm that analytics still records visits and key events, and that the cookie banner still works as intended after updates. Our own site uses cookie consent with Google Consent Mode v2, and it is worth re-checking whenever scripts change.
5. Small content changes
Prices, opening hours, team members, a new reference, a seasonal offer, an outdated news item. Many plans include a set number of hours for such changes; agree in writing what counts as a small change and what happens to unused hours.
Monthly, quarterly, yearly
| Rhythm | Tasks |
|---|---|
| Monthly | Updates, backup check, uptime and security review, form test, Search Console review, tracking check, small content changes, a short report |
| Quarterly | Restore test, review of user accounts and access, accessibility spot check of key pages and forms, review of content that dates quickly |
| Yearly | Domain and hosting renewal, server software versions and end-of-support dates, licences for paid plugins, fonts and services, legal pages, a broader look at whether the site still fits the business |
For the accessibility spot check, our article on practical accessibility checks for forms and navigation gives a list you can work through.
What maintenance is not
New sections, a booking system, an integration with your accounting software or a redesign are development work. Mixing them into a maintenance budget hides the real cost of both. A good maintenance agreement states what is included, what is charged separately and how different kinds of problems are handled – a site that is down is not the same as a typo. Those response times should be agreed in writing with whoever maintains your site.
How much maintenance does your site need?
It depends on what the site is made of and what depends on it:
- A simple static or custom-built brochure site with no plugins and few changes may need little more than monitoring, backups, a yearly server check and occasional content edits.
- A WordPress site with many plugins needs regular updates and testing, because every plugin is a separate piece of software with its own update cycle. Our comparison of WordPress and custom development looks at this difference in running costs.
- An online shop, or a site with customer accounts and integrations, needs the most attention: payments, stock feeds, emails and personal data all have to keep working.
A large plan for a small site is wasted money; skipping maintenance on a shop is a risk. Match the plan to the site.
What a monthly report should tell you
- what was updated, and anything that was postponed and why;
- whether backups ran, and when a restore was last tested;
- incidents: downtime, security warnings, errors found and fixed;
- the result of the form test and any Search Console issues;
- content changes made and hours used;
- upcoming dates: certificate, domain, hosting, software end of support;
- recommendations, with an honest note on what can wait.
Even if you do the maintenance yourself, writing this one-page report every month keeps the work from quietly stopping.
If you are planning a new site, ask about maintenance before development starts – it affects technical choices such as which plugins or libraries are used and how updates are deployed. We build websites and maintain the sites we build. Contact us if you want to discuss a new project and how it will be looked after once it is live.