Website redesign without losing SEO: a step-by-step plan

A step-by-step plan to redesign your website without losing search traffic: content audit, redirect mapping, launch checks and what to monitor after.

Crest Design
Website wireframe with arrows mapping old pages to new pages

A website redesign does not have to cost you search traffic. Redesigns lose rankings when URLs change without redirects, when content that ranked is cut or rewritten without thought, or when a staging setting slips through to the live site. Plan for those three risks and most sites come through a redesign with traffic intact, after a short period of movement while Google recrawls.

This guide gives you a practical order of work: audit, map, rebuild, launch and monitor. It follows Google's site move documentation, last updated in August 2026, and applies whether you are staying on the same platform or moving between WordPress, Shopify, Webflow, HubSpot or a custom build, at the time of writing (November 2026).

Why redesigns lose traffic

Most drops trace back to a handful of causes:

  • Changed URLs with no redirects, so links and rankings point at 404 pages.
  • Removed or thinned content: long, useful pages replaced by short, design-led ones.
  • Weaker internal linking after a new navigation drops links to important pages.
  • Staging settings left on, such as a sitewide noindex or a robots.txt block.
  • Lost on-page elements: titles, meta descriptions, headings, structured data and alt text that were never carried over.
  • Slower pages, often from large hero videos, animation libraries and new third-party scripts.

None of these are about the visual design itself. A new look rarely hurts by itself; what changes underneath it does.

Step 1: audit before anyone opens a design file

Build a list of every URL that matters before you plan the new structure. Combine:

  1. 1 A full crawl of the current site with a crawler such as Screaming Frog or Sitebulb.
  2. 2 Pages with clicks or impressions from Search Console's Performance report, using the longest date range available.
  3. 3 Top landing pages from your analytics.
  4. 4 Pages with external backlinks, from your SEO tool of choice.
  5. 5 Your XML sitemap, plus images and PDFs that get traffic or links.

Then give each URL a decision:

Decision When to use it What happens at launch
Keep Performs well and still accurate Same URL if possible, content carried over
Improve Ranks but outdated or thin Rewritten, URL kept or redirected
Merge Several pages compete for the same topic Combined page, others redirected to it
Remove No traffic, links or business value Redirect to the closest relevant page, or return 404 or 410 if nothing fits

Share this sheet with designers and copywriters. It stops a page that brings in a third of your enquiries from quietly disappearing in a sitemap workshop.

Step 2: build the redirect map

If a URL changes, it needs a redirect. Google's guidance is specific:

  • Map every old URL to its new equivalent, including images, videos, JavaScript and CSS files where those paths change.
  • Use server-side permanent redirects (301 or 308) where possible. Client-side redirects are a last resort.
  • Send each URL to the most relevant new page. Redirecting many old URLs to an unrelated page such as the home page can be treated as a soft 404. Consolidating several pages into one relevant page is fine.
  • Avoid chains. Googlebot follows up to 10 hops, but Google suggests ideally no more than three, and fewer than five.
  • Keep redirects for as long as possible, generally at least a year.

Every platform handles redirects differently: server or plugin rules on WordPress, the URL redirects tool on Shopify, 301 settings on Webflow and URL redirects in HubSpot. Check import limits and whether wildcard or pattern rules are supported before you rely on them. Old chains are worth fixing too: if A already redirects to B, point A straight at the new URL.

Step 3: carry over what search engines read

During the build, make sure each kept or improved page keeps or improves:

  • Its title tag, meta description and main heading.
  • Its body content and internal links, including links in the main navigation and footer.
  • Structured data such as Organization, Product, FAQ or Article markup.
  • Image alt text and file names for images that bring traffic.
  • A self-referencing canonical tag, and updated hreflang annotations if you run several languages.

Protect the staging site with a password or noindex, and write down exactly what to switch off at launch. Forgotten staging rules are among the most common causes of a sudden drop.

Step 4: launch day checklist

  1. 1 Remove staging noindex tags, password protection and robots.txt blocks.
  2. 2 Upload and test redirects: run your old URL list through a crawler and confirm every one returns a single 301 or 308 to a live 200 page.
  3. 3 Check canonical tags point at the new live URLs.
  4. 4 Submit the new XML sitemap in Search Console. Google says warnings about redirecting URLs in an old sitemap are expected.
  5. 5 Confirm analytics, tag manager, consent banner and conversion tracking fire correctly.
  6. 6 Test forms, checkout and key journeys on mobile.
  7. 7 If the domain changed, verify both properties in Search Console and use the Change of Address tool. It is not needed for moves within the same domain.
Test redirects with your old URL list, not by clicking around the new site.

After launch: what is normal and what is not

Google says to expect temporary ranking changes while it recrawls, and that new URLs can take a few weeks or more to settle on a medium-sized site, longer on large ones. In the first month, check weekly:

  • Search Console's Page indexing report for new 404s, redirect errors and pages excluded by noindex.
  • Clicks and impressions for your top 20 pages, compared with the weeks before launch.
  • Server logs or your host's error reports for unexpected error codes.
  • Core Web Vitals for the new templates once field data builds up.

A gradual dip that recovers is normal. A sharp, sitewide drop within days usually points to a technical problem such as blocked crawling or missing redirects, so check those first.

Frequently asked questions

Will a redesign hurt my rankings?

It can, but it does not have to. Sites that keep URLs or redirect them properly, and keep their useful content, often see only short-term movement.

Should we change domain or platform at the same time?

You can, but each change adds risk and makes it harder to tell what caused a drop. If timelines allow, separating a domain change from a redesign makes problems easier to diagnose.

How long should redirects stay in place?

Google recommends keeping them as long as possible, generally at least a year. For pages with backlinks, keep them indefinitely.

Need help with a website redesign?

We redesign sites with the SEO groundwork built in, from the content audit and redirect map to launch-day checks. See our design services and our WordPress website for a global logistics company, or read our SEO plan for moving to Webflow if you are changing platform. To plan yours, get in touch.

Sources: Google Search Central: Site moves with URL changes, Google Search Central: Redirects and Google Search

(over to you)

Planning a build like this?

Tell us what you're building and we'll come back with ideas and next steps.