Website Redesign: How to Plan It Without Losing What Works

A website redesign replaces the design, structure and often the underlying build of an existing website and the quality of the planning decides whether the new version improves on the old one or loses the rankings, enquiries and content that were working. The safest redesigns start from evidence about what the current website does well, then change what is holding it back. Priority Pixels provides web design for B2B and public sector organisations and the planning approach below reflects how a redesign can protect existing performance at every stage.

Most traffic losses after a redesign trace back to decisions made early in the project, such as changing URLs without a redirect plan or removing pages that attracted search visits and links. A clear plan avoids those problems and gives everyone involved the same view of what the project needs to achieve. The website redesign checklist below summarises the main stages and each one is covered in more detail further down.

1. Agree the business goals and how success will be measured.
2. Record a baseline of traffic, rankings, conversions and backlinks.
3. Audit existing content and decide what to keep, improve, merge or retire.
4. Map every current URL to its new destination with permanent redirects.
5. Set accessibility, performance and mobile requirements before design starts.
6. Structure pages and templates for search engines and AI answers.
7. Test across browsers and devices, then launch with a rollback plan.
8. Monitor Search Console, analytics and redirects for several months after launch.

The order matters more than it might first appear. Goals and baseline data shape every later decision and redirects are far easier to plan when the new structure is still on paper than after the build is finished.

Signs a Website Needs a Redesign

A website usually needs a redesign when its structure or build stops supporting what the organisation needs, rather than when the visual style starts to feel dated. A refresh of colours, imagery and copy can deal with a tired appearance, but it rarely fixes problems with navigation, performance, accessibility or how easily the team can update content. Our review of website design trends for 2026 covers which visual changes are worth prioritising.

The clearest signs tend to show up in analytics data and in everyday use by staff and visitors. The cards below cover the four that come up most often in B2B and public sector projects.

If only one of these applies, a targeted fix may be more sensible than a full redesign. A redesign earns its cost when several problems share a common cause, such as an outdated theme or an information architecture that no longer reflects the services you offer.

Set Goals and Record a Baseline First

Every redesign should start with agreed goals and a record of current performance, so the new website can be judged against evidence rather than opinion. Goals might include more qualified enquiries, fewer visitors abandoning key forms, WCAG 2.2 AA conformance or a structure that supports new services and each one needs a measure the team agrees on before design begins.

On Priority Pixels projects this happens at the first project meeting, where objectives, stakeholders, success measures and any limitations are agreed before creative work starts. The same stage reviews existing copy, photography, brand assets and any external tools that need integrating, so content gaps are flagged early rather than discovered during the build.

The baseline should cover a full year where possible, so seasonal changes in demand are not mistaken for the effect of the redesign. The table below sets out what to record and where to find it.

For performance, PageSpeed Insights provides lab data from a controlled test and field data from real visitors. Field data reflects how people experienced the website over time, which makes it a fairer comparison point after launch than a single lab test.

Decide What Content to Keep

A content audit decides which existing pages move across unchanged, which are improved, which are merged and which are retired. Pages that attract organic traffic, earn backlinks or produce enquiries should be treated as assets, as they hold search visibility that a new page would have to earn again from nothing.

That does not mean everything stays as it is. Outdated service descriptions, thin pages and duplicated content are often the reason a website underperforms and a redesign is the right moment to deal with them. Where several weak pages cover the same topic, merging them into one stronger page and redirecting the old URLs usually serves visitors and search engines better than keeping them all.

User research is worth including at this stage, particularly for websites with several audiences. The GOV.UK Service Manual guidance on user research sets out how to plan research and analyse findings and the same principles apply to B2B websites where buyers, partners and job applicants all look for different things. The comparison below summarises how to approach content decisions.

Conversion paths deserve the same scrutiny as content. A redesign is a good opportunity to simplify forms and calls to action and our guide to conversion rate optimisation covers how to test those changes rather than relying on assumptions.

Map Every URL and Plan Redirects

URL mapping is the most effective single step for protecting search visibility during a redesign. Every URL on the current website needs a destination on the new one, either its direct equivalent or the most relevant replacement page and the mapping should be agreed while the new sitemap is still being planned.

Google’s guidance on redirects and Google Search recommends a permanent server-side redirect whenever a page’s URL changes and explains that the 301 and 308 status codes tell search engines a page has moved permanently. Temporary redirects such as 302 do not send the same signal, so they should not be used for pages that are moving for good. Google’s documentation on moving a website with URL changes advises keeping redirects in place for as long as possible, generally at least one year, so signals can transfer to the new URLs.

A spreadsheet listing the old URL, the new URL and the reason for each decision makes the mapping easy to check and easy to revisit months later. Our website migration SEO checklist covers redirect mapping, crawl comparisons and launch checks in more detail, so this guide does not repeat them here.

Set Accessibility, Performance and Mobile Requirements

Accessibility, performance and mobile behaviour should be written into the brief before design starts, as they are far harder to add once templates are built. For accessibility, the reference point is the Web Content Accessibility Guidelines (WCAG) 2.2 published by the W3C, which sets testable success criteria at levels A, AA and AAA.

Public sector bodies in the UK need to meet WCAG 2.2 AA and publish an accessibility statement, as set out in the government’s accessibility requirements for public sector websites. Private organisations that provide services to the public have obligations to disabled people under the Equality Act 2010 and an accessible website is a practical way to meet them. Priority Pixels designs and develops every WordPress website to WCAG 2.2 AA as a minimum and our website accessibility services cover audits and remediation for websites that already exist.

Performance targets need to be equally specific. Google’s Core Web Vitals define a good experience as a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less. Setting those targets in the brief gives designers and developers a shared standard to test against, rather than a vague aim for a fast website.

Mobile layouts matter for search as well as for visitors. Google uses mobile-first indexing, which means the mobile version of a page’s content is used for indexing and ranking, so mobile templates need to carry the same content as desktop rather than a reduced version. Bespoke builds make these requirements easier to hold and premade themes frequently introduce accessibility barriers deep in the code that are difficult to remove later.

Structure Content for Search Engines and AI Answers

A redesign is the right time to make page structure clearer for both search engines and AI search tools. Google states that there are no additional requirements to appear in AI Overviews or AI Mode and that standard SEO practice still applies, so a sound technical foundation does most of the work.

In practice, that means one clear topic per page, a logical heading hierarchy, descriptive internal links and direct answers at the start of each section. Structured data gives Google explicit clues about what a page means, so any schema markup on the current website should be carried across and extended where new templates allow. An updated XML sitemap helps search engines find the new URLs and crawl the website more efficiently.

Technical checks such as canonical tags, robots.txt rules, internal linking depth and index coverage belong in the same plan. Our technical SEO services include migration planning for platform changes, restructures and major design updates and these details are much easier to get right before launch than to correct afterwards.

Test Thoroughly, Then Launch With a Plan

Testing should confirm that the new website works on every device, browser and form before any visitor sees it. Priority Pixels tests each build on Windows, Mac, iOS and Android across Chrome, Safari, Firefox and Edge, checking navigation, forms, accessibility and performance and creates the 301 redirects at this stage so they can be checked before go live.

Launch itself needs a defined sequence. The development website should be backed up and moved to the live server, the DNS updated and then the redirects, cookie consent tool, contact forms, Google Tag Manager, analytics and SSL certificate checked in the live environment. Launching early in the week, with the team available and the previous version kept ready for a quick rollback, keeps the risk manageable if something unexpected appears. Our article on the web design process sets out each stage from brief to launch in more detail.

Monitor Performance After Launch

Monitoring should start on launch day and continue for several months, as search engines need time to process a redesign. Google’s site move guidance, linked above, notes that ranking fluctuations are normal while it recrawls and reindexes a website and that medium-sized websites can take a few weeks or more for the new URLs to replace the old ones in results.

Search Console is the main tool for this work. Submit the new XML sitemap, watch the page indexing report for spikes in errors and use URL Inspection on the most important pages. In GA4, compare organic sessions and conversions for the pages in your baseline and review 404 reports to catch any URLs the redirect map missed.

A gradual recovery with a few dips along the way is normal. A sustained fall on specific pages usually points to a missing redirect, a page that is not being indexed or content that changed more than intended and the baseline makes those problems much quicker to find. Priority Pixels supports websites after go live through ongoing development, managed WordPress hosting and maintenance, so issues found in the weeks after launch can be fixed quickly and the new website can keep improving from a stable starting point.