Maintain a website after launch

Estimated reading time : 2 min · Published September 24, 2026

Check key journeys each month

Open the main pages on mobile and desktop. Test navigation, filters and the contact form with a controlled enquiry; confirm delivery and visible feedback.

Inspect main images, cards, internal links and downloads. An empty listing can go unnoticed when nobody visits like a new customer.

Keep content accurate

Assign an owner to changing facts such as prices, hours, availability, service areas and terms. Update related pages together to prevent contradictions.

Review articles when a tool or recommendation changes. Change the public modified date only when an actual editorial update warrants it.

Plan for continuity

Document backup frequency and test restoration. Schedule component updates and check essential functions after each change.

Review page errors, enquiries and available search data. Record what changed and the outcome before choosing pages to improve, combine or retire.

Monitoring that leads to action

Separate regular checks, incident handling and editorial changes. Define an alert state, owner and action for each check. An unowned list does not ensure continuity.

Record changes and test the affected journey. Review scope and recovery when changing a dependency or supplier. Opening hours, seasonal copy and forms require monitoring alongside technical updates.

Reference documents

OWASP — Vulnerable Dependency Management

Content updated on October 5, 2026

Record checks and findings in the acceptance log

Acceptance matrix to adapt to your project

These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

Test cases, expected outcomes and useful evidence
Case	Expected outcome	Evidence to retain
A form extension is updated.	Repeat validation, confirmation and receipt; record the version and result.	Record URL, steps, result and dated evidence.
Alert	Owner and action defined	Handling procedure
Update	Affected journey still works	Version and result
Absence	Substitute and recovery documented	Handover

Frequently asked questions

Does a successful update guarantee a working site?

No. A technical success message does not verify visitor tasks. After a change, repeat the journeys using that component, such as login, enquiries, search or checkout. Keep results and the relevant version, and verify that a usable restore path exists.

Does maintenance include writing?

The contract determines this. Separate technical fixes, content updates, new pages and features before comparing offers.

How do we cover an owner’s absence?

Prepare service inventories, alert channels, authorised contacts and recovery procedures. Transfer access through the agreed mechanism, never through a public report.