How to plan a website redesign without losing traffic

Every few years, most businesses (and yours might be one of them) reach a point where their website needs a proper overhaul. The design looks dated, the tech is creaking, the content has grown organically into a mess. A redesign is the right call. But I've seen far too many businesses lose significant organic search traffic in the process, sometimes permanently.

It doesn't have to happen. With some planning, you can redesign your site and keep (or even improve) your search visibility.

Why redesigns kill traffic

In my experience, the most common cause is URLs changing without redirects. Your old site had /services/web-design and the new one has /what-we-do/website-design. Google has been indexing and ranking the old URL for years. Other sites have linked to it. When that URL suddenly returns a 404, all of that authority evaporates. Multiply that across dozens or hundreds of pages and you've got a serious problem.

The second common cause is content being removed or significantly changed. If a page ranked well because it had 1,200 words of genuinely useful content about a specific topic, and the redesign replaces it with a 200-word summary and a stock photo, you'll lose that ranking.

The third cause is technical regressions. The new site loads slower, has worse mobile usability, breaks structured data, or introduces crawl errors. Each one chips away at your search performance.

Before you start

Crawl your existing site. Use Screaming Frog (the free version handles up to 500 URLs) to get a complete list of every URL, its title tag, meta description, word count, and internal links. This is your baseline. Export it to a spreadsheet and keep it safe.

Check Google Search Console. Identify which pages bring in the most organic traffic and which queries they rank for. These are your priority pages, the ones you absolutely cannot afford to break.

Document your current URL structure. Every URL on the old site needs to map to a URL on the new site. If a page is being removed, it needs a redirect to the most relevant alternative. If a URL is changing, it needs a 301 redirect from old to new.

During the build

Create a redirect map early and keep it updated as the build progresses. A redirect map is simply a two-column spreadsheet: old URL on the left, new URL on the right. Every old URL gets a row. When the new site launches, these become 301 redirects in your server config or .htaccess file.

Preserve your content. If a page ranks well, keep the content that made it rank. You can redesign how it looks, restructure it, improve it, but don't gut it. If you want to reorganise your information architecture, fine, but make sure the actual content survives.

Maintain your on-page SEO. Title tags, meta descriptions, heading structures, image alt text, internal links, all of these should be carried over or improved, not lost in the redesign.

At launch

Test every redirect. Don't assume they work, verify them. Use Screaming Frog to crawl the old URL list against the new site and check that each one returns a 301 to the correct destination.

Submit your new sitemap to Google Search Console immediately. Monitor the Index Coverage report daily for the first few weeks. If you see a spike in 404 errors or a drop in indexed pages, act fast.

Keep the old site available (even if it's just a backup) for at least a month. If something goes badly wrong, you want the option to roll back.

After launch

Watch your analytics closely for 4-6 weeks. Some fluctuation in organic traffic is normal after a redesign, Google needs time to recrawl and reassess. A gradual dip followed by recovery is fine. A sudden 30% drop that doesn't recover within a week means something is broken.

If you're planning a redesign and want to make sure your search traffic comes through intact, I can help with the technical planning. Get in touch at [email protected].