Redesigning a site without losing rankings

Redesigns are the single biggest avoidable cause of organic traffic loss. The fix is unglamorous: a structured pre launch checklist that every team member signs off on before the new site goes live.

Pre launch checklist

The steps below walk through this one stage at a time. Complete each step before continuing so nothing gets missed.

1. Crawl the old site. Export every URL with traffic in the last 12 months.
2. Map every URL to its new equivalent. Decide on redirects for the rest.
3. Implement 301 redirects (never 302).
4. Re audit page speed on staging. Match or beat the old LCP.
5. Re submit the sitemap on launch day.
6. Monitor Coverage and Performance reports daily for 30 days.

Content and structure changes to sign off separately

Redesigns often bundle a visual refresh with content and information architecture changes. Treat those as a separate risk category, because they can lose rankings even when every redirect is correct.

• Do not rewrite top performing page copy at the same time as the redesign, unless it is being deliberately improved.
• Preserve heading structure and internal linking patterns on high traffic pages.
• Keep URL slugs unchanged wherever possible, since every changed slug needs a redirect.
• Flag any page being merged or removed to the whole team before launch, not after.

A redesign should change how a site looks, not quietly change what it says.

What to do if traffic still drops

Even a careful migration can see a temporary dip while Google reprocesses the new site. The response depends on whether the drop is temporary reprocessing or a real technical fault.

1. Check Search Console Coverage for a spike in errors or excluded pages first.
2. Confirm redirects are returning 301, not chained through multiple hops.
3. Compare the new page's content and internal links against the old version for anything missing.
4. Give it two to four weeks of normal crawling before treating a dip as a genuine loss.