A website can look perfectly healthy while quietly losing enquiries. A useful maintenance plan checks what customers need to do, as well as the software that keeps the site running.
Open your site on your phone, find a service and send a test enquiry. Does the message arrive in the right inbox? Does the visitor receive a sensible confirmation? Can someone on your team find the enquiry and reply? A green uptime indicator cannot answer any of those questions.
That is the difference between a site being online and a site doing its job. When you compare website maintenance plans, use the customer journey as the starting point.
Check the important journey from beginning to end
Choose the actions that matter to the business: submitting a form, booking a call, asking for a quote or completing a purchase. After changes, test those actions on a phone and a desktop. Check the resulting email or record, rather than stopping at a success message on the page.
Use clearly labelled test data and agree how it will be removed. For an online shop, use the payment provider’s supported testing process; avoid creating accidental real orders or charges. The aim is a repeatable check that someone can own.
Treat updates as changes worth checking
On WordPress, maintenance normally involves core software, plugins and themes. Keeping them current matters, but “all updates installed” says little about whether the site still works. Ask what is checked before and after an update, what happens if a plugin is no longer supported, and how a failed change would be reversed.
WordPress’s security guidance explains that security is risk reduction, and that hosting and website application responsibilities are distinct. A hosting bill alone should not be taken as proof that someone is maintaining your plugins, forms or user accounts.
A separate test environment is useful for changes with a meaningful risk of breaking the site. Urgent security fixes also need a timely route to production. The agreement should explain that balance, rather than promising that every update is either instant or postponed until a monthly visit.
Ask for a restore, not just a backup badge
WordPress separates a site’s files from its database; its backup documentation explains why both matter. Confirm what is included, how far back copies go, where they are stored and who can access them if the main site or hosting account becomes unavailable.
The frequency should reflect how much changes. A largely static brochure site and a busy shop have different exposure to lost data. A restore to a safe test location gives you more useful evidence than a screenshot saying a backup job ran. It also helps establish the time and steps involved.
Make the monthly report easy to understand
You should be able to read the report and know whether anything needs a decision. A long list of technical events is less helpful than a clear account of changes, checks, failures and unresolved work.
| Area | Useful evidence |
|---|---|
| Forms and key journeys | What was tested, when, and whether the result arrived. |
| Software and access | Updates made, unsupported components and unnecessary accounts found. |
| Recovery | Backup coverage and the result of the last agreed restore test. |
| Availability and speed | Meaningful incidents, affected pages and the action taken. |
| Open work | What needs approval, its cost and who owns the next step. |
Be clear about what maintenance does not include
Content edits, redesigns, new features, paid plugin licences and emergency incident recovery may be priced separately. Ask whether unused editing time carries over and whether the provider can support a site they did not build. For South African quotes, compare the same scope and VAT basis before comparing the totals.
Maintenance can support a reliable, usable site. It does not guarantee search rankings, sales or freedom from every security incident. If the real problem is an unclear offer or an awkward enquiry journey, that needs design and content work too.
A useful check for this week
Send a test enquiry from your phone and follow it all the way to a reply. If nobody knows who should do that test—or fix what it finds—you have identified a responsibility to add to your maintenance plan.