Start with a map, not a moodboard
A website has more than a visual identity. It has addresses people have bookmarked, pages that answer questions, forms that collect enquiries and tools your team depends on. Before a rebuild, list those pieces and decide what each one does.
Include pages reached through search, campaign links and emails. Check which forms feed your inbox or CRM. A page that looks old may still have a useful job; a page that looks busy may not have one at all.
Walk the enquiry journey
Use a phone and follow a visitor’s path: find a service, understand the offer, ask a question and send an enquiry. Then follow it from the team’s side. Where does the message arrive? Who owns the next action? What does the visitor see after sending it?
A visual redesign is a good moment to remove friction in that journey. Give buttons clear labels, make forms understandable and keep confirmations consistent with what actually happened.
Treat URLs as part of the design
Keep useful existing URLs where possible. If an address must change, map it to the equivalent new page and use a direct permanent redirect. Sending every old page to the homepage hides the original intent and can frustrate visitors.
Update your own internal links to the destination. Check important external entry points and plan the search-engine migration separately from the visual review. A redesign is not a promise that rankings will stay unchanged.
Test the whole path before launch
Test menus, keyboard navigation, small screens, forms, chat and the team handoff. Use synthetic data in an isolated environment so development enquiries do not become real customer records.
Keep a rollback point and a clear launch checklist. Looking finished and working reliably are two different checks. A good rebuild earns both.