Start with the journeys that matter
Write down the small number of things the website must do reliably. For a service business, that may be finding a service and sending an enquiry. For a shop, it includes finding a product and completing a purchase.
Use that list to guide maintenance checks. The work is easier to prioritise when it connects to how the business uses the website.
Connect updates with recovery
Before a meaningful change, know what is backed up and how the previous state can be restored. A backup that has never been checked is a weaker foundation than a documented recovery process.
Use staging for changes that affect key functionality. Review what an update changes and check the important customer journeys after it is applied.
Check the information customers rely on
A technically working website can still be unhelpful if the information is wrong. Review opening hours, contact details, delivery information, service descriptions, and product pricing as part of ongoing care.
- Are important links and forms still working?
- Are prices, availability, and promotions current?
- Do confirmation messages tell customers what happens next?
- Can the main tasks be completed comfortably on a phone?
Keep a short change record
Record significant changes, the reason for them, and what was checked afterwards. Note unresolved issues and who is responsible for the next step.
A maintenance relationship works best when the website owner can understand what has been done and why. A concise, useful record supports that conversation.
Explore the related website service
