A redesign can improve a website, but it can also remove useful content, break search visibility or recreate the same structural problems with a new visual style. The first step should be understanding what needs to change and what should be protected.
Define what the redesign needs to change
Write down the business reasons for the project. Common goals include explaining services more clearly, improving lead quality, supporting a repositioning, making mobile use easier, improving performance or giving internal teams a better way to maintain content.
These goals create a basis for decisions later. Without them, design preferences can take over and the project becomes difficult to evaluate.
Review evidence before opinions
Look at analytics, Search Console data, enquiry patterns and feedback from sales or customer-facing teams. Which pages attract useful traffic? Where do people enter the site? Which pages lead to enquiries? Which questions keep appearing in sales conversations?
Even a basic evidence review can reveal pages that deserve to be preserved or improved rather than removed.
Audit content and message hierarchy
List the existing pages and decide whether each one should be kept, combined, rewritten or removed. Check whether the important services have dedicated pages and whether the navigation reflects how clients actually think about the business.
Review headings and page introductions. Can someone understand what the company does without reading the whole page? Are proof, process and next steps placed near the questions they answer?
Protect existing search value
Before changing URLs, identify pages that already receive organic traffic or external links. If a URL must change, plan a permanent redirect to the closest relevant replacement. Keep useful page topics and internal links where they still support the new structure.
A visually better site can still be a worse business asset if the redesign discards search visibility that took years to earn.
Make sure the new version has unique titles and descriptions, crawlable links, canonical URLs, a current sitemap and content that remains visible without relying on fragile interactions.
Review mobile UX and performance
Test the current site on real mobile widths. Look for long menus, small tap targets, oversized text blocks, slow images, layout shifts and forms that are difficult to complete. These are practical issues that should inform the new component system.
Performance should be considered during design, not only at the end. Image choices, animation, font loading and JavaScript all affect how quickly the page becomes usable.
Turn the audit into a page plan
Once the review is complete, create a page map that shows the purpose of every important page, the primary user question it needs to answer and the next action it should support. That becomes the bridge between strategy, content and interface design.
The redesign is then solving a defined set of problems rather than simply making the existing site look newer.