A redesign should make the website easier to understand and maintain. Before changing colours or layouts, identify which pages help customers and where the current experience creates uncertainty. Existing URLs and useful content are assets that need a deliberate migration plan.
Audit what the site already does
Inventory the pages and their purposes. Keep useful explanations, identify outdated material and flag duplicate pages. Talk to the people answering enquiries: they often know which information customers cannot find. Use that evidence to decide what should be rewritten, combined or removed.
Improve the route to an enquiry
Organise navigation around recognisable customer needs. Write page headings that explain the offer and place supporting information close to the next action. A redesign should work for someone entering through an article or service page, not only for visitors who start on the homepage.
Protect links during migration
Create a map from old URLs to their new destinations. Preserve valuable URLs where possible and use redirects where a page moves. Test forms, downloadable files and mobile navigation on the new build. Keep a copy of the previous site until the replacement has been checked.
Treat the content migration as a separate deliverable
Keep a record of which old page maps to which new page and why. A removed article should lead to a genuinely relevant destination, not automatically to the homepage. Review image references, document downloads and links in navigation or footer sections. Update the sitemap to match the final canonical pages. If the old site has useful descriptions, revise them with a clear editorial purpose instead of replacing them with generic marketing language. The final review should confirm both the new presentation and the continuity of the information visitors already use.
What to prepare
For website owners and marketing teams, preparation starts with existing URLs, current content, enquiry paths and approved replacement copy. Choose a small, representative sample that includes a normal case and an exception. Identify the person who can approve each part of that sample. If two colleagues interpret the same record differently, resolve the definition before treating it as an implementation requirement.
- Page inventory with keep, revise or retire decisions
Collect the relevant information and check it with the person who maintains it. Use an agreed example so the team can identify omissions before the work moves into a larger rollout.
- Old-to-new URL mapping
Write down the expected result and who is responsible for it. Include any dependency on another person, device or service, so the requirement can be demonstrated rather than left as an assumption.
- Approved content and navigation labels
Include this in the walkthrough with an ordinary user. Record what worked, what needed clarification and what requires a separate decision before the organisation relies on the workflow.
- Tested forms, downloads and mobile layouts
Assign an owner for the follow-up and keep the outcome with the project notes. Make the information available to the people responsible for operating and supporting the agreed process.
A practical walkthrough
Follow an old link shared in an email, reach its replacement page and submit an enquiry. This checks the migration and the customer journey together instead of treating launch as a visual comparison.
Run the example using the role that would perform the work in practice. Compare the result with the expected outcome and retain the relevant reference or review note. Then repeat the part affected by a correction or handover. A successful walkthrough should leave another authorised colleague able to understand the result without reconstructing a separate conversation.
Questions to discuss
Do all existing pages need new URLs?
Usually not. Keeping a useful existing URL reduces migration work and preserves links already shared with customers. Change it when there is a clear structural reason.
What should we confirm before moving forward?
Confirm the scope for a website redesign, the required records and roles, and any setup or integration work. Keep demonstrated functionality separate from requested additions, and agree how unresolved questions will be answered before implementation.
Discuss your next step
Tell us about your team, current process and the outcome you need. We can help you identify the relevant demonstration or service scope.



