ThirteenBytesStart a project
Web Development··ThirteenBytes Team

How to Redesign Your Website Without Losing Search Traffic

Website redesigns often cost businesses years of accumulated rankings. A pre-launch inventory, a proper redirect map, and a performance budget prevent almost all of it.

How to Redesign Your Website Without Losing Search Traffic

A website redesign should be a step forward, but for many businesses it quietly becomes an expensive step back. The new site launches, everyone celebrates, and then over the following weeks organic traffic drops — sometimes by half. The rankings that took years to build erode because of decisions made in a few sprint cycles. The frustrating part is that nearly all of this damage is preventable with planning that costs a fraction of the redesign itself.

Why redesigns lose traffic

Search engines rank pages, not websites. Every URL on your current site that ranks has accumulated its own history: backlinks pointing to it, content signals, and user behavior data. When a redesign changes URLs, deletes pages, rewrites content, or slows the site down, those signals get orphaned or diluted. The redesign did not make your business less relevant — it broke the paths search engines were using to find and trust you.

The most common causes, in rough order of damage: changed URLs without redirects, removed pages that had rankings or backlinks, thinned-out content (a designer's "clean" page often deletes the text that was ranking), lost title tags and meta descriptions, and a new build that is slower than the old one.

Take inventory before you touch anything

Before design work begins, export a complete picture of what you have. Crawl the current site to get every URL. Pull search analytics to see which pages earn impressions and clicks. Check which URLs have external links pointing at them. This inventory becomes your protection checklist: every URL on it needs a deliberate decision — keep it, improve it, or redirect it. "We forgot about that page" is how rankings die.

Pay special attention to unglamorous pages. Old blog posts, FAQ entries, and product detail pages frequently drive more search traffic than the homepage. They are also the pages most likely to be cut during a redesign because nobody in the room remembers why they exist.

Map every old URL to a new one

If URLs are changing — new structure, new platform, new naming — build a one-to-one redirect map before launch, not after. Every old URL should permanently redirect (a 301) to the most relevant new page. Relevant is the key word: redirecting everything to the homepage tells search engines the original pages are gone, and their accumulated value largely evaporates.

Pages you are intentionally retiring deserve a decision too. If a page has backlinks or residual traffic, redirect it to the closest surviving topic. Only let a page return a 404 when it truly has no successor and no value worth preserving.

Carry over what was working

A redesign is a chance to improve content, not an obligation to rewrite it. For pages that rank well, preserve the substance: the topics covered, the depth, the headings that match what people search for. Keep title tags and meta descriptions for strong pages, or improve them deliberately rather than letting a new CMS regenerate them from scratch. Re-implement structured data the old site had. And hold the new build to a performance budget — launching a slower site is one of the most common self-inflicted wounds, and one a good development team will test for before launch, not after.

Launch carefully, then watch closely

Treat launch week as part of the project, not the finish line. Verify redirects with a crawler the day you go live. Submit an updated sitemap. Then monitor search analytics for the following month: some fluctuation after a major change is normal, but a steep sustained drop on specific pages usually means a missed redirect or gutted content — both fixable if you catch them early. Keep the old site's crawl data on hand so you can compare page for page.

Where to go from here

If a redesign is on your calendar, put the traffic-protection work at the start of the project plan: crawl and inventory the current site, flag every page that earns search traffic or backlinks, and make the redirect map a launch requirement with an owner and a deadline. Those three steps prevent the large majority of post-redesign traffic losses. If you'd like a second pair of eyes on this, tell us what you're building — we reply within one business day.

website redesignseo301 redirectssite migrationweb development

Want this handled for you?

From strategy to shipped — tell us what you're building.

Start a project