Begin with the visitor’s decision
List the people the website serves and what each needs to understand or do. A prospective customer comparing services needs different information from an existing customer looking for support. The page structure should make those journeys clear rather than mirror the organisation chart.
Audit what you already have
Review existing pages, useful search traffic, enquiry paths and content that remains accurate. Identify what should be kept, rewritten or retired. Record important URLs and plan redirects so a rebuild does not discard working routes into the business.
Agree how content will be maintained
A website needs an editing process as well as a content management system. Decide who owns each section, what needs review before publication and which changes should be possible without a developer. Test that workflow with a realistic example.
Define acceptance before launch
Include the main visitor journeys, responsive layouts, keyboard access and performance in the acceptance plan. Check contact destinations and analytics events with test data. Make source code, account access and maintenance responsibilities part of the handover rather than a task left until the end.
Bring it back to your business
Choose one workflow, establish the current situation and identify who needs to be involved. A small, observable improvement gives a better foundation for the next decision than an ambitious plan with no baseline.
Discuss your challenge


