What Website Maintenance Actually Includes
Maintenance may include software updates, backups and checks; content changes, hosting and emergency work may be separate.
- Define the system being maintained
- Make updates a tested process
- Check real delivery and recovery, not green dashboards
- Separate maintenance from content and new features
- What a useful maintenance report should show
- Questions about this guide
- Further reading
- Related help
- Terms in this area
- Read next
- Tell us about your own situation.
- Services
- Resources
- Company
- Get in touch
Maintenance may include software updates, backups and checks; content changes, hosting and emergency work may be separate. Website maintenance is not simply installing updates once a month. A maintained site should keep important customer tasks working, retain recoverable copies and have clear responsibility when something fails. The exact agreement depends on the platform, integrations and business process. This guide helps you compare maintenance proposals, understand the difference between operational care and new development, and ask for evidence of completed work. It does not assume that a particular response time, price or service is included by Marina IT. Those details must be agreed for the actual website. Define the system being maintained An agreement should identify the CMS, hosting, domain, DNS, certificate, forms and external booking or payment systems. Some providers maintain only the application and others also manage hosting. A failed domain renewal can take a healthy site offline; an external form integration can fail while every page remains reachable. List the functions customers depend on and who controls each account. Clarify renewal costs and licences as well as labour. A plugin licence that expires may stop updates without immediately breaking the site, creating a problem later. Keep business ownership of essential accounts and provide the maintainer only the access required. If responsibilities are shared between companies, define a fault handover route so the owner is not left mediating blame. Make updates a tested process Updates should account for compatibility and recovery. For significant changes, a staging copy can help check the combination of theme, plugins and integrations before the live site is changed. A useful test covers navigation, login where applicable, forms, booking or checkout and the languages customers use. Installing an update and seeing the homepage is only a partial check. Agree how security fixes are prioritised and what happens if an update breaks something. A recoverable backup should exist before an operation that may require rollback. However, restoring an old vulnerable version indefinitely is not a solution: the conflict needs resolution or an alternative component. Document what changed, which tests passed and any remaining limitation rather than marking everything complete automatically. Check real delivery and recovery, not green dashboards Uptime monitoring shows whether a page responds, but not w
What should a maintenance agreement specify?
List the sites, updates, backup checks and support that are included, together with any exclusions and the response arrangements you agree on. Please do not assume redesigns or content changes are covered unless the scope says so in writing.
How should completed maintenance be reported?
Ask for a short record of what changed, which checks were done and anything that still needs attention. That makes it easy to tell a finished update from a fault that is still open.
Does maintenance include new pages?
Only if your agreement says so. Routine updates and fault checks are different from designing new pages, writing content or translating a new service. Ask for a clear scope and an approval process before assuming a maintenance fee covers extra development.