How to redesign a website without losing your rankings

Traffic loss after a redesign is almost never caused by the design. It is caused by URLs changing without redirects, content being cut, or internal linking being flattened. All three are avoidable with a fortnight of preparation.

Before anything is designed

1. 1Crawl the existing site and export every URL. Use a crawler, not your sitemap — sitemaps are routinely incomplete.
2. 2Export landing page data from analytics for the last twelve months, and query data from Search Console.
3. 3Export your backlink profile. Pages with external links are the ones that hurt most if broken.
4. 4Combine these into one spreadsheet: URL, traffic, conversions, external links, current rankings.
5. 5Make a keep, merge or retire decision for every URL, and record the destination for the ones you are not keeping.

Content decisions

Keep anything with traffic, conversions or external links, even if it is ugly. Merge thin overlapping pages into one stronger page and redirect the others to it. Retire only genuinely dead content, and even then redirect the URL to the most relevant surviving page rather than letting it 404.

Resist the urge to cut page count for tidiness. "We reduced from 200 pages to 30" is a sentence that precedes a traffic collapse surprisingly often.

The redirect map

• Every changed URL needs a 301 to its closest equivalent. Not the homepage.
• Avoid redirect chains. Old A to old B to new C loses value; map A directly to C.
• Handle trailing slashes, uppercase variants and parameter versions consistently.
• Redirect old image URLs too if they earn image search traffic.
• Keep redirects live permanently. Removing them a year later reintroduces the problem.

Things that quietly break

• Title tags and meta descriptions replaced with template defaults.
• H1s removed because the new design uses an image for the headline.
• Structured data lost with the old templates.
• Internal links flattened when a navigation is simplified — this redistributes authority, sometimes badly.
• The staging site left indexable, competing with production. Check robots and noindex before launch, and remember to remove them at launch.
• Canonical tags pointing at the staging domain. This one is catastrophic and common.

Launch day and after

1. 1Verify robots.txt is not blocking the site, and that noindex tags are removed.
2. 2Submit the new sitemap in Search Console.
3. 3Crawl the live site and check every redirect resolves in one hop with a 200 at the end.
4. 4Watch Search Console coverage and Core Web Vitals daily for a fortnight.
5. 5Expect a short dip. Two to four weeks of fluctuation is normal; a decline that is still deepening after six weeks means something is wrong.
6. 6Keep the old analytics data accessible for comparison. Annotate the launch date.