To redesign a website without losing search traffic, list every URL the old site has, decide where each one belongs on the new site, and set permanent server-side redirects from old to new before launch. Keep those redirects for at least a year, update your internal links and sitemap, and watch Google Search Console closely for the first few weeks. It's unglamorous work, and it's the difference between a redesign that keeps its rankings and one that starts over.
Google publishes a guide for exactly this. I follow it closely, and I plan the redirects on the same sheet of paper as the new sitemap.
Why do redesigns lose traffic in the first place?
Because page addresses change. The old site had /services/kitchens.html, the new one has /kitchen-remodeling/. Google has the old address indexed, other websites link to it, and customers may have it bookmarked. On launch day, all of them hit a "page not found" error unless someone told the server where that page went. Google sees a page that ranked for years suddenly vanish, and the new page, with no history, starts from scratch.
The missing map causes the damage far more often than the design does.
How do you build the redirect map?
Start with a complete list of old URLs. Pull them from three places, because each one catches pages the others miss: the old site's sitemap, a crawl of the old site with a tool like Screaming Frog, and the Pages list in the Performance report in Google Search Console, which shows the URLs that actually get clicks and impressions. Add any URLs you know are used in ads, email campaigns, printed materials or QR codes, since those don't always show up in a crawl.
Then, for every old URL, write down its new home. The best destination is the page that serves the same purpose. A page about kitchen remodeling redirects to the new kitchen remodeling page. If a page has no equivalent anymore, redirect it to the closest relevant page, like the parent service. Dumping everything on the homepage is tempting and it throws away most of the value.
Planning something like this? Evan plans, shoots and builds websites, brands and campaigns from Baton Rouge. Book a Chat and tell him what you are working on.
What kind of redirect should you use?
A permanent, server-side redirect, the kind called a 301. Google's site-move guide recommends server-side permanent redirects where possible, and says to avoid chains, where page one redirects to page two, which redirects to page three. Point every old URL straight at its final destination. Chains add delay for visitors and some browsers don't follow long ones.
How long should they stay?
Google says generally at least a year, and from a visitor's point of view, consider keeping them indefinitely. I keep them indefinitely. Old links on other websites and in people's bookmarks live for a very long time, and a redirect costs nothing to leave in place.
What else has to change at launch?
A few things people forget. Update internal links so your new pages link to each other directly instead of through redirects. Submit the new sitemap in Search Console. Carry over the title tags and meta descriptions from pages that ranked well, unless you're deliberately improving them. Keep the same page content where it was working, since a redesign that rewrites every page at the same moment it changes every URL makes it hard to tell what caused a drop. And check your Google Business Profile's website link points to a working page.
One more that catches people: anything outside the website that uses the old addresses. Printed brochures, truck wraps with a URL, QR codes on signs, links in email signatures and online directory listings. The redirects cover them, but it's worth updating the ones you control, like directory listings and email signatures, so they point straight at the new pages.
Here's the tradeoff I'd admit. Keeping old content and URL structures where they work can limit how bold the new site's structure gets. Some designers push for a clean slate, and sometimes a clean slate is right. But the bolder the structural change, the more carefully the map has to be built, and the more patience you'll need while Google catches up.
What should you watch after launch?
For the first four to six weeks, check Search Console weekly. The Pages report shows errors, including any old URLs that now return "not found." The Performance report shows whether clicks and impressions are holding. Expect some wobble in the first couple of weeks while Google recrawls the site. A steady decline after that means something in the map is wrong, so test the old URLs directly: paste a handful into a browser and confirm each lands on the right new page. Also watch your forms and calls. If search traffic holds but leads drop, look at the new design's path to contact instead of the redirects. That's a different fix, usually a buried phone number, a longer form or a call to action that moved below the fold.
Is it worth the effort for a small site?
Yes, even for a 10-page site. Building the map for a small site is an hour or two. Losing years of search history because nobody did is far more expensive, and "the new site looks great but the phone stopped ringing" is a story owners tell far too often.
Planning a redesign?
Every redesign in our website design service starts with the old site's URL list and a redirect map, and our SEO service watches Search Console through the first months after launch. You can see finished rebuilds in the portfolio. Book a Chat and we'll pull your current URL list together before anything else changes.