What Should a Small Business Website Maintenance Plan Include?
A maintenance agreement should make responsibility clear when something changes or stops working. Compare the actual checks, recovery arrangements and support process, then match them to the way your business uses its website.
By Menerai · Published
Define what the business needs maintained
List the parts of the site your business relies on: public pages, inquiry delivery, booking, payments or a customer portal. Identify which supplier controls each part. A service called ‘website maintenance’ can describe very different work unless the agreement makes the responsibilities explicit.
Start with the customer journey and the consequence of failure. A brochure page with an email link and a site taking paid bookings have different operational needs. Record the important tasks and ask how the proposed arrangement checks them.
If you are commissioning a new site, include this discussion in the website brief. For platform choices, our WordPress and custom website comparison explains why editing and technical care belong in the same buying decision.
Compare the work behind each plan
| Area | Question to resolve |
|---|---|
| Updates | Which application, theme, plugin or dependency updates are included? |
| Recovery | What is backed up, where is it stored and how is restoration checked? |
| Customer tasks | Who verifies forms, booking and other important journeys? |
| Content | Which routine changes are included and how are they requested? |
| Accounts | Who controls the domain, hosting and paid integrations? |
| Support | How are faults reported, prioritized and acknowledged? |
Ask for a reporting example that shows work performed, a problem found and an outstanding decision. A recurring invoice alone does not explain whether the agreed checks happened. Keep enough detail to distinguish completed work from recommendations awaiting approval.
For an integration maintained by another vendor, identify the handoff. Your website supplier may be able to diagnose a failure without controlling the external service that needs repair.
Ask how recovery would work
WordPress’s backup documentation distinguishes the database and files needed to restore a site. Use that as a prompt to ask what your own implementation needs for recovery, including content and configuration outside the code repository.
Agree a backup approach based on how much recent work the business could afford to lose and how quickly recovery is needed. Ask who can access the copies and how a restoration is verified. The right answer depends on the site’s activity and the responsibilities of its host and suppliers.
Treat ‘we have a backup’ as the beginning of the discussion. A useful handover identifies the recovery process and the person responsible for carrying it out. Keep the account ownership and documentation available to the business.
Check important journeys after changes
WordPress’s update guidance recommends backing up, reviewing compatibility and visiting the site afterwards to check it works. Other implementations need an appropriate review process for their own dependencies and deployment method.
- Review the changed pages and shared navigation.
- Check important forms and the outcome shown to the visitor.
- Confirm message routing or integration behaviour in an authorized test.
- Keep the previous working version or another agreed recovery route available.
Use the contact-form checklist for the inquiry journey. A maintenance check should follow the task far enough to establish the outcome the business needs, such as successful message delivery.
Agree support before a fault occurs
Clarify when support is available, how to report an issue, how urgency is assessed and what work needs separate approval. Keep response expectations distinct from a promise to resolve every fault within a fixed time. The supplier may first need to investigate an external dependency.
When comparing costs, separate hosting and subscriptions from technical care and content work. No universal monthly figure describes all of those arrangements. Ask for the included scope and how additional work is quoted.
For a new website or redesign, discuss handover and ongoing responsibilities as part of Menerai’s website service. Share your current site and the tasks it supports so the project conversation can include how it will be maintained after launch.
Sources & further reading
Have a website project in mind? Talk with the people who will design and build it.
Start a Project ↗