Website redesign: how to decide, plan and launch without losing what works

Short answer: a website redesign is worth it when the current site cannot support what the business needs: a new offer or brand, a structure visitors cannot navigate, a platform your team cannot update, or mobile and accessibility problems built into its foundations. If the problems are slow pages, weak calls to action or outdated content, targeted improvements are usually faster and less risky. Either way, protect what already works: URLs with traffic, content that ranks, conversion paths and tracking.

A redesign is one of the few website decisions that can make things worse as well as better. Done carefully it removes friction and makes the site easier to run. Done carelessly it can break redirects, lose tracking history and drop pages that were bringing in enquiries. This guide is about making that decision well and carrying it out safely.

Website redesign or targeted improvements?

Not every underperforming website needs to be rebuilt. Use the nature of the problem to decide.

Targeted improvements usually suffice when:

• The structure works but key pages are slow or heavy.
• Calls to action, forms or contact paths are weak.
• Content is outdated but the pages themselves are sound.
• A few templates look dated while the rest of the site is fine.

A redesign is usually justified when:

• Your services, audience or brand have changed and the site no longer reflects them.
• Visitors cannot find what they need because the information architecture is wrong, not just the wording.
• The platform or theme makes every change slow, expensive or risky.
• Mobile, accessibility or performance problems come from how the site is built, so fixing them page by page is not realistic.
• You need capabilities the current setup cannot support, such as a second language, integrations or a proper content model.

Many projects end up in between: a new design system and templates while keeping the URL structure and most of the content.

Signs the current site is holding the business back

Check evidence rather than impressions:

• Enquiries: are forms, calls and messages from the site flat or falling while traffic holds?
• Behaviour: in analytics, which key pages have high exits and short engagement?
• Mobile: can a visitor complete the main task on a phone without zooming or fighting the layout?
• Speed: Google's Core Web Vitals define a good experience as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1, measured at the 75th percentile of visits (web.dev). PageSpeed Insights and Search Console report these for real users.
• Editing: how long does it take your team to publish a simple update, and how often do they need a developer?
• Accessibility: can the site be used with a keyboard, with readable contrast and labelled forms? The WCAG guidelines are the reference.

Diagnose before you design

A useful redesign starts with a baseline you can compare against later:

1. Analytics: top landing pages, conversion paths and the pages that produce enquiries.
2. Search Console: pages and queries that currently earn impressions and clicks.
3. Content inventory: every URL, its purpose, traffic and whether to keep, update, merge or remove it.
4. Technical crawl: broken links, redirect chains, duplicate titles, missing metadata, page weight.
5. User input: sales or support teams know which questions visitors ask repeatedly.

Write down what the redesign must achieve in measurable terms before anyone opens a design tool.

What to preserve

• URLs that earn traffic or links. Keep them where possible; if they change, redirect each one to its closest equivalent.
• Content that ranks or converts. Improve it rather than replacing it with thinner copy.
• Conversion paths: forms, phone and messaging links, booking flows.
• Tracking: analytics properties, conversion events, tag configuration and consent settings.
• Structured data, metadata and legal pages that the current site depends on.

Content and CMS migration

Use the content inventory as the migration plan. For each page decide keep, update, merge or retire, and record the destination URL. Moving to a new CMS is also the moment to fix the content model: separate fields for titles, summaries, images and alt text make future editing easier and keep pages consistent. Migrate media with its alt text, and check that rich content such as tables, lists and embedded forms survives the move.

SEO migration: what actually happens

Be precise about expectations. Google's guidance on site moves with URL changes recommends permanent redirects, and notes that permanent redirects such as 301 and 308 do not cause a loss in PageRank. It also warns that rankings may fluctuate temporarily while Google recrawls and reindexes the site, and that for a medium-sized site it can take weeks before new URLs replace the old ones in results.

A redesign does not improve rankings by itself. It removes obstacles; results then depend on content quality, relevance and how well the migration was executed. To avoid avoidable losses:

• Map every old URL to one new URL and redirect it directly, with no chains.
• Keep redirects in place long term.
• Update internal links to point at final URLs rather than relying on redirects.
• Carry over titles, descriptions, headings and structured data for pages that rank, then improve them deliberately.
• Submit the new XML sitemap and monitor indexing in Search Console.

Keep analytics and tracking continuous

Record a baseline for the weeks before launch, keep the same analytics property where possible, recreate every conversion event on the new templates and test them on staging. Annotate the launch date so later comparisons account for it. Without this, you cannot tell whether the redesign helped.

Staging and QA

Build on a staging site that is blocked from search engines, and make sure that block is removed, and not copied, at launch. Before launch:

• Test every form and conversion event end to end.
• Test the redirect map, ideally with an automated list of old URLs.
• Check key templates on real phones and common browsers.
• Run accessibility checks (keyboard, contrast, labels) and performance checks on the templates that matter most.
• Review content for placeholders, broken media and missing translations.

Launch and the weeks after

On launch day confirm that the site is indexable, the sitemap is submitted and redirects respond as planned. In the following weeks watch Search Console for crawl errors and 404s, compare enquiries and key page engagement with the baseline, and fix issues quickly. Expect some movement in search while pages are reprocessed; judge the redesign on the trend over the following months, not the first days.

For the full build process see how to create a business website, and for budgeting a redesign the website cost guide. If you want a team to run the redesign, our website design and development service covers redesign projects.