How to Protect SEO During a Website Redesign

Start with evidence from the existing website

Before design work begins, create a clear picture of the pages and signals that matter. A page that looks dated may still attract useful searches, enquiries or links from other websites.

• Export the current URL list from the XML sitemap and a site crawl.
• Use Google Search Console to identify pages receiving impressions, clicks and external links.
• Use analytics and enquiry data to find pages that contribute to leads or important customer journeys.
• Record current titles, main headings, canonical URLs and any structured data on priority pages.

The purpose is not to preserve every page unchanged. It is to avoid removing something valuable without knowing why.

Keep useful URLs when there is no reason to change them

Changing a URL adds migration work and creates another opportunity for something to go wrong. If an existing address is clear, relevant and already earning visibility, keeping it can be the simplest option.

When a URL genuinely needs to change, map the old address to the most relevant replacement page. Use a permanent server-side redirect and update internal links so they point directly to the final destination rather than passing through a redirect chain.

Do not rewrite strong content simply because the design is new

A redesign and a complete content rewrite are separate decisions. Retain information that is accurate, useful and already serves customers well. Improve weak sections where there is a clear reason, and create new content where the business now offers something the old site did not explain properly.

Priority pages should keep a clear title and main heading that describe what the page actually offers. Avoid turning every page into generic marketing copy or repeating the same location and service phrases across several URLs.

Build the new structure around real customer journeys

The redesign should make it easier for visitors to understand the business, compare services and take the next step. Give important services their own clear destinations and use descriptive internal links where another page provides genuinely useful detail.

For example, a rebuild project may connect naturally to website design, website development and SEO services without forcing all three subjects onto the same page.

Test more than the appearance before launch

A polished design is not ready to publish until the underlying journeys have been tested. Check the areas that affect both customers and measurement.

• Mobile navigation, buttons, forms and readable text sizes.
• Page speed, large images and unnecessary scripts.
• Contact forms, confirmation messages and email delivery.
• Analytics events and genuine lead tracking.
• Canonical URLs, robots directives and indexability.
• Old-to-new redirects and internal links.
• The XML sitemap and important structured data.

Launch with a redirect map, not a collection of guesses

Every changed URL should have a deliberate destination. Redirect an old page to the closest equivalent new page rather than sending large numbers of unrelated URLs to the homepage.

Once redirects are active, update your own navigation and contextual links to use the new URLs directly. This is faster for visitors and avoids unnecessary redirect hops.

Monitor the first weeks after the redesign

A migration is not finished the moment the new site is published. Review Search Console, analytics, form submissions and server errors after launch. Watch for unexpected 404s, important pages losing impressions, tracking gaps or customer journeys that no longer behave as expected.

Some fluctuation can happen while search engines recrawl changed pages. The useful question is whether the migration signals are correct and whether genuine problems are being found quickly.

Website redesign SEO FAQs