A new website is exciting, and that excitement is exactly where redesigns go wrong. Teams focus on how the new site will look and forget to protect what the old one already does well: the pages that rank, the forms that bring enquiries and the content customers rely on.
Start with what is working
Before anyone opens a design tool, look at your analytics. Which pages get the most visits? Which ones lead to enquiries or sales? Which search terms bring people in? These pages are assets. The redesign should make them stronger, not replace them by accident.
- List your top pages by traffic and by conversions.
- Note the search terms each important page ranks for.
- Record every URL, so nothing disappears without a redirect.
Define the job of each page
Every page should have one main purpose: explain a service, answer a question, or move a visitor to the next step. Write that purpose down before designing. It keeps the layout focused and makes review meetings shorter, because you can ask whether a design does its job instead of whether everyone likes it.
Plan content before design
Designing around placeholder text produces pages that look good empty and awkward with real words. Draft the key messages first, even roughly, then design around them. You will spot gaps early and avoid long pages that say very little.
The best redesigns feel new to visitors and familiar to search engines.
Keep search engines in the loop
If URLs change, set up permanent redirects from every old address to its closest new page. Keep titles and headings for important pages close to what already ranks, and resubmit your sitemap after launch. These steps take an afternoon and protect years of search history.
Measure after launch
Set up tracking before go-live so you can compare the new site with the old one. Watch enquiries, key page traffic and search visibility for the first few weeks, and fix anything that dips. A redesign is not finished at launch; it is finished when it performs better than what it replaced.



