Start with the journeys that matter
List the tasks customers and staff rely on: enquiries, checkout, login, search, downloads or content updates. A website maintenance checklist should verify these tasks, not only whether the homepage opens.
Assign responsibility for each check and record where a failure should be reported. A small service website and a store processing orders throughout the day need different priorities and schedules.
Know what your backup contains
Identify the files, database and uploaded media needed to restore the site. Check backup frequency, retention and access. A copy stored only beside the live website may not protect against every type of failure.
Restoration testing matters because a file labelled backup is not proof that the application can recover. Agree who performs recovery and what information might be lost between the last backup and an incident.
Review updates before applying them
Track software versions and supported dependencies. Where possible, test changes on staging and keep a rollback path. After an update, revisit the functions most likely to be affected, such as forms, payments or admin screens.
Record the change and any follow-up work. Avoid making several unrelated production changes at once if that makes a new fault difficult to isolate.

Check forms beyond browser validation
Submit a test enquiry and verify the record reaches the intended destination. Review required fields, invalid email handling, duplicate clicks and error messages. The message shown to the visitor should reflect the server result.
If email delivery is used, test the actual mailbox route as well as the application’s send request. A successful handoff to a mail service is not always proof that someone received the message.
Keep access and renewals organised
Review who has admin, hosting and registrar access. Remove unnecessary access through the appropriate account controls and maintain recovery details the business can reach. Track domain, hosting and relevant licence renewals separately.
Confirm that payment methods and contact details are current. A renewal reminder sent to an abandoned inbox offers little protection against an expired service.
Finish with a useful work record
A maintenance report should show what was checked, what changed, which issues remain and which decisions need approval. Separate routine work from new development requests and from provider incidents outside the maintenance scope.
Review the plan when the site gains a store, a portal or a new integration. Maintenance should follow the current business workload rather than remain fixed to the website as it existed several years ago.


