How to redesign your website without losing your search rankings

The new site goes live on a Friday. It looks fantastic. By the following week, enquiries have dried up and the pages that used to bring in steady traffic from Google have vanished from the results. The design was the success. The launch was the disaster.

This is one of the most common and most avoidable ways a business hurts itself online. The good news is that almost all of the damage comes from a handful of mistakes, and every one of them can be planned around.

The fear is justified#

If you are nervous that a redesign could tank your search traffic, that instinct is correct. It happens often enough to be a genuine risk rather than a horror story.

Search engines have spent years learning your current site. They know which page sits at which address, what each one is about, and how much they trust it. A redesign that quietly changes all of those addresses, or strips out the content that earned the trust, throws that knowledge away. The rankings do not move to the new pages. They simply disappear.

The fear is healthy because it makes you plan. The businesses that get hurt are the ones who treat search as something that will sort itself out after launch.

Map every URL before you touch anything#

Before a single new page is built, write down every address your current site has. This list is the single most important artefact of the whole project.

Pull your pages from your content system, your analytics and your search console, and combine them into one master list. You are looking for every URL that exists and, just as importantly, which ones actually receive visitors or rank for something. A page nobody visits and nobody links to can be retired without ceremony. A page that quietly brings in customers every month must be protected at all costs.

Keep this list close, because the next two sections both depend on it.

Redirects done properly#

When an address changes, you have to tell browsers and search engines where the content has moved. That instruction is a redirect, and getting the type right is the difference between keeping your rankings and losing them.

301 not 302#

A 301 is a permanent redirect. It tells search engines the page has moved for good and that the trust built up over years should follow to the new address. A 302 is temporary, and it signals the opposite, that the old address is coming back, so the value tends to stay put rather than transfer. For a redesign, you almost always want a 301, as the MDN reference on the 301 status makes clear, and the broader guide to HTTP redirections explains when each one is appropriate.

Map every old URL that is changing to its closest new equivalent, one to one, and avoid sending everything to the homepage. A redirect to an irrelevant page is barely better than a dead end, and it frustrates the human who clicked an old link just as much as the search engine that followed it.

Keep the content that earns traffic#

Designers love a clean slate, and a redesign is a natural moment to cut clutter. The danger is cutting the wrong thing.

That guide which ranks on the first page of Google, the case study that visitors read before they enquire, the FAQ that answers the question everyone asks: these are assets, not clutter. If a page earns traffic or trust, the redesign should carry its substance across, even if the wrapper around it changes completely. You can restyle the content. You should not quietly delete it.

Where you genuinely improve a page, keep the address stable if you can, so the history attached to it stays intact. Reworking the words on an existing URL is far safer than starting a new one from scratch.

Launch day checklist#

With the mapping and content sorted, launch becomes a controlled event rather than a leap of faith. A few checks catch the problems that slip through.

Confirm the redirects all fire and land on the right pages. Make sure you are not accidentally blocking search engines, a surprisingly common mistake where a setting that hid the staging site is left switched on, and check your robots.txt rules are not still disallowing the whole site. Submit an updated sitemap so crawlers find the new structure quickly. Check that titles, descriptions and headings survived the move. Finally, look at speed, because a heavier new design can drag performance down, and the free PageSpeed Insights tool gives you a real reading before users feel it.

Watching the recovery#

Even a clean migration causes a brief wobble while search engines recrawl and reassess. Knowing that in advance stops you panicking and undoing good work.

Watch your search console for crawl errors and broken redirects, and fix them quickly. Keep an eye on your key landing pages rather than obsessing over every term. Expect a short dip followed by a return to roughly where you were, often within a few weeks. Speed plays into how fast you bounce back, since Google ties Core Web Vitals to ranking and experience, so a faster site can recover stronger than the old one. Solid hosting performance underpins all of it.

If keeping on top of rankings and content feels like a job in itself after launch, an SEO tool like marketGoo can turn the ongoing work into a checklist rather than a guessing game, and Google's own guidance on good page experience is a sound reference to keep nearby.

A redesign should be a step forward, not a reset to zero. Map the URLs, redirect them properly, protect the content that works, and the new site keeps everything the old one earned while looking far better doing it.