A practical website maintenance checklist
Keep your website useful with checks for enquiries, orders, content, access, updates and recovery, organised around the work your business relies on.
Start reading
A website maintenance checklist should help you keep doing business through the website. Start with the tasks people rely on: making an enquiry, finding the right information, paying for an order or reaching a booking service. Then organise the technical and editorial checks around those tasks.
The schedule depends on the platform, how often the content changes and what a failure would affect. Agree who owns each check and what happens when it fails. A checklist nobody is responsible for is easy to forget.
Check the customer journey
Visit as a customer using a phone and a computer. Find a service or product, follow the main action and check the information along the way. Look for unavailable pages, incorrect contact details, confusing delivery information and links to systems that have changed.
For a store, include product selection, cart changes, delivery options and the payment handoff. Arrange any production transaction or enquiry test with the business first so it does not become an accidental order or a misleading sales lead.
Cloudfusion’s ongoing Shopify work for Wonki Ware includes improvements to product discovery and the shopping journey. It is a useful reminder that looking after a store includes how people use it, alongside the platform’s technical upkeep.
Review content that affects a decision
Check your services, team details, opening arrangements and policy links when the business changes. Confirm that examples and offers still describe what you provide. Update a guide when its advice changes and show a meaningful review date.
Check the pages people arrive on directly from search as well as the homepage. An older article can still be someone’s first introduction to your business. Keep its important address working while correcting inaccurate claims and outdated next steps.
Look after accounts and access
Keep a current list of the domain, hosting, CMS, payment, booking and email accounts involved. Record the responsible person and the agreed recovery process. Use individual access where the platform supports it and review access when people or providers change.
Check renewals before they become urgent. A website can remain intact while a domain expires or a connected service stops working. Keep recovery information secure and available to the people responsible for the business.
Plan updates and recovery together
The platform determines which updates your team or provider must handle. For a self-managed site, agree how application, theme and extension updates are assessed and tested. Use an appropriate staging or recovery plan for changes that could affect live work.
Check what your backups contain, where they are stored and how restoration is tested. WordPress separates site files from the database; its backup guidance explains why both matter. Having a backup file and proving that you can restore the needed website are different checks.
Respond to problems with a clear owner
Agree how faults are reported, which problems are urgent and who can investigate them. Keep enough information to reproduce a fault, such as the affected page and the step that failed, without sending passwords or unnecessary customer data.
GoLegal’s relationship with Cloudfusion has included feature development, SEO and website support since 2019, followed by a complete rebuild in 2025. It illustrates how ongoing maintenance and larger improvements can form part of a lasting working relationship.
Turn the checks into routine work
- Assign an owner to important customer journeys and connected services.
- Check key actions after a deployment, platform update or integration change.
- Review current business information and follow up on broken links.
- Confirm access, renewals and recovery responsibilities.
- Record failed checks, the action taken and anything still waiting for review.
Our website and software improvement service can assess an existing site. Bring its platform details, the problems people experience and the support arrangements already in place so we can agree a useful scope.
