Website maintenance keeps an existing site usable as content, software and hosting conditions change. Zoha can discuss a care scope covering updates, backups, form checks, content changes and fault investigation. Coverage starts with a review of the website and access, followed by written responsibilities and a clear way to report problems.
Updated
On this page
Separate a fault from a change request
A broken enquiry form needs a different response from a request for a new page layout. The first restores an agreed function; the second adds or changes work. Distinguishing them helps staff report problems clearly and helps everyone understand what the support arrangement covers.
Prepare a short list of the website functions your organization depends on. Contact forms, downloads, staff editing and important landing pages are sensible starting points. Add the person who owns each function and who can approve a change.
Build a care plan around the site
| Activity | What to specify |
|---|---|
| Updates | Which software and extensions are covered, with review before release |
| Backups | What is copied, where it is kept and how restoration is checked |
| Content | The amount and kind of editing included |
| Checks | Forms, links, certificates and important pages |
| Support | Reporting route, coverage hours and escalation arrangements |
A custom website, a commerce installation and a small publishing CMS have different dependencies. Existing licenses, hosting restrictions and access problems should be identified before agreeing ongoing work. A maintenance plan does not automatically include redesign or major replacement.
A useful first review
We need to know who controls the domain, hosting, CMS and any external services used by the site. Review the current software, backup arrangements and known issues. If access is missing, resolve ownership before making changes that could be difficult to reverse.
For a hypothetical organization, this review might reveal that enquiry notifications work but go to a former employee. Correcting the destination and documenting who owns the inbox may be more valuable than adding another homepage feature.
Make routine work visible
- List the changes made and the date they reached the live site.
- Record checks performed and any issues still awaiting a decision.
- Distinguish supplier faults, content requests and external-service problems.
- Record renewals or access questions that the organization must handle.
A short report should help a nontechnical owner see what happened. It can include the backup status, completed updates, form test results and the next recommended action. Avoid treating a list of tools as evidence that the website's important functions were checked.
Know what happens when something breaks
Agree how to report an issue, what information to include and which hours are covered. A useful report gives the affected address, what was expected, what happened and when the problem began. Do not send passwords or sensitive visitor information in an ordinary message.
Some incidents require an external host or platform provider. The maintenance scope should explain who communicates with that provider and what access is available. Response arrangements, restoration priorities and work outside the agreed coverage need to be explicit rather than implied.