Website maintenance should identify the work that keeps the agreed customer journeys usable. “Keep it updated” needs an owner, a change process and evidence beyond a successful update notification.
Frequently asked maintenance questions
Does installing updates complete maintenance?
No. Updates are one activity. The agreement should also identify backup and recovery responsibilities, important journey checks, licence ownership and how failures are handled.
Does hosting include every maintenance task?
Only if the provider’s actual scope says so. Hosting, application maintenance, content editing and business support can be separate services.
Should every update be applied directly to the live site?
The appropriate change process depends on the site and consequence. Plan backups, compatibility review, suitable testing and authorised timing for important changes.
Can a backup-job success prove recovery?
It shows the reported job outcome. A usable restore requires separate evidence from a suitable recovery test.
Define the recurring work
| Work area | What to agree |
|---|---|
| Software | Which components are maintained and who approves significant changes. |
| Recovery | What is copied, where it is controlled and how restoration is tested. |
| Forms | Which enquiry journeys and delivery paths are checked. |
| Commerce | Which authorised test methods cover important order states where applicable. |
| Licences | Who owns renewals and supported versions. |
| Content | Who updates services, hours, products and policy inputs. |
| Security | Which monitoring or review activities are actually included. |
Keep a change record people can use
Record what changed, why, the relevant environment and the checks performed afterward. Include known limitations and a recovery reference where appropriate. A concise log is more useful than a series of unexplained plugin screenshots.
When a form or store depends on an external provider, separate the site change from provider availability or account approval. A local interface test cannot establish that every external service remains healthy.
Review backups as a recovery dependency
WordPress’s administration guidance treats files and database content as relevant backup components. The actual plan should cover the site’s configuration and external dependencies as well as the material required to restore the agreed function.
Keep recovery access controlled and avoid destructive testing on the live site without explicit authority. A representative restore in an appropriate environment can produce useful evidence; record what was restored and which business journey was checked.
Know what remains outside the agreement
New pages, article writing, redesign, complex integrations and major migrations may require separate scope. Ask how those requests are estimated and approved. Keep a clear contact and escalation route for failures, with human hours and response commitments that match the actual service.
The maintenance review should end with completed work, unresolved issues and the owner of each next action. It should not promise permanent uptime or absolute security from a routine update schedule.
Sources and further reading
Put the decision into practice
List the website journeys and maintenance responsibilities that need a clear owner.
Explore Website Design Discuss the requirement by email