How do you redesign a website without losing your search rankings?
Redesigning your website? Map every old URL, redirect it, carry over what Google reads and watch Search Console so the new site keeps its rankings.
TL;DR
Search rankings belong to pages, and every page lives at an address. When a new site changes those addresses and nothing tells Google where each old page went, the rankings attached to them have nowhere to go. The same happens when a page that ranked gets cut, when its words get rewritten or when its title and tags don't make the move.
So the work that protects your search traffic is mostly clerical. List every page on the old site, decide where each one lives on the new one, redirect it permanently, carry over what Google reads and check all of it before and after launch. Rankings often wobble for a few weeks after a launch. If the map is right, they settle.
Related: Thinking about a website redesign? · How much does a website redesign cost? · Hiring for a website
The short answer
Map every old URL to its new home before launch and redirect each one permanently, with a 301. Keep the pages that rank, and the content on them, unless you have a reason to change them. Carry over the titles, descriptions, canonical tags and structured data. Test all of it on a staging site, launch, then watch Google Search Console for a few weeks. Rankings often wobble after a launch and settle if the map is right.
What I think
Most redesigns that lose search traffic lose it in the move. The designer is thinking about the look, the developer about the build and the owner about the words. Nobody has been given the job of making sure every page Google already trusts still exists at an address Google can find.
That job is unglamorous and easy to leave out of a quote. It's a spreadsheet, a list of redirects and a few days of checking. It also decides whether the new site starts with the search traffic the old one earned or starts again from nothing. If you have a quote in hand, look for the migration as its own line.
So before anyone talks about layouts, I'd want two things on paper: the pages that bring in search traffic now and the name of the person who owns moving them. They belong in the brief for the new site as much as anything about how it looks.
A redesign doesn't lose rankings. Unmapped URLs do.
Why redesigns lose rankings
A redesign tends to change three things at once, and any one of them can cost you.
The addresses change. A new platform or a new site structure usually means new URLs. A page at /services/roof-repair becomes /roofing/repairs. Google still has the old address on file, and so does every site that linked to it. If the old address now shows an error, the page's history doesn't follow. As far as Google can tell, a page that ranked has gone and a new, unknown page has appeared.
The content changes. A redesign is a natural moment to cut. Pages that look thin get merged or dropped. Copy gets rewritten to sound sharper and loses the plain words people typed into Google. Say a page ranked for "commercial roof repair" and the new copy never uses the phrase. The page can look better and rank worse.
The signals don't carry. Google reads more than the words on a page. It reads the title tag, the meta description, the headings, the canonical tag that says which address is the real one, the structured data that says what kind of thing the page is and the internal links that say which pages matter. A new build starts with none of these unless someone puts them back.
Each of these is small. Together they look like Google punishing the new site.
Before launch
Almost all of the work happens before launch, on a spreadsheet.
Start with an inventory. List every URL on the old site. A crawler or the old sitemap will give you this. Then add what Search Console shows: which pages get impressions and clicks, and for which searches. If you have a tool that shows links from other sites, add the pages those links point at. That list is what the old site has earned.
Then decide, page by page. Keep it, merge it into another page or let it go. Pages that bring in search traffic stay unless you have a reason. If two pages merge, the new page should cover what both of them ranked for.
Then map. Every old URL gets one new URL, the closest match on the new site. Not the home page. Sending everything to the home page is the common shortcut, and Google tends to treat it as if the old page had simply been deleted. A page you let go can redirect to the nearest relevant page, or return a plain "gone" if nothing fits.
Then carry. For every page you keep, move the title, the description, the headings and the copy that ranks. Point each page's canonical at its own final address. Move the structured data. Rebuild the internal links so they point straight at the new addresses.
Then test on staging. Run every old URL through the redirect rules and check where each one lands.
The map is the migration. The design sits on top of it.
The checklist
None of these will stop the site launching if it's missing, which is why they get missed.
- Every old URL listed, with its clicks and impressions from Search Console
- Every old URL mapped to one new URL, never to the home page by default
- Redirects set as permanent (301), one hop from the old address to the final one
- Pages that rank kept, with the copy and headings that earned the ranking
- A unique title and meta description on every page
- A canonical tag on every page, pointing at that page's own final address
- Structured data carried over and checked
- Internal links pointing at final addresses, not at redirects
- One version of every address (with or without a trailing slash, with or without www) and redirects from the others
- An XML sitemap that lists only final addresses
- The staging "don't index" setting removed at launch, and the robots.txt file checked
- Analytics and Search Console connected to the new site before the switch
Launch week
Launch is when the map goes live, so check it live.
Switch the redirects on at the same moment as the new site. Then test them again, because rules that worked on staging don't always behave the same once they're live. Submit the new sitemap in Search Console. Ask Google to index the handful of pages that matter most.
Leave the redirects in place for good. Old links keep getting clicked for years.
Check on staging. Then check again live.
The canonical that pointed at a redirect
This site used to run on Wix. I moved it to a new build in July 2026, and the old blog addresses had to go somewhere. Each one redirects, one by one, to its new home. An old post about the Viasat work now redirects to the case page at /work/viasat/.
The new site also picked one form for every address, with a trailing slash. /quick-read redirects to /quick-read/. One page, one address.
On 4 November, checking a new page before it went live, I found its canonical tag pointing at the version of its address without the slash. The canonical is the line in the code that tells Google which address is the real one for this page. This one named an address that immediately redirected somewhere else. Google can often work out what you meant, but you've handed it two signals that disagree and asked it to choose. It was caught before launch and corrected in the brief.
The same week turned up another. Ten pages were sharing one title, one description and one canonical, when each needed its own. To a visitor they were ten different pages. To Google, all ten were saying they were the same page.
I can't tell you what either mistake would have cost in rankings. I can tell you nobody would have spotted them by looking at the site. Both problems sat in the part of the page only Google reads, and that's where a migration tends to break things without anyone noticing.
Check the parts nobody looks at. Those are the parts Google reads.
After launch
Expect a wobble, and know what you're watching for.
Rankings often move for a few weeks after a launch while Google recrawls the site and connects old addresses to new ones. A dip in that window is normal. In Search Console, four places tell you most of what you need.
- The pages report. New addresses should be getting indexed, and old ones should drop out as redirected rather than as errors.
- Not found errors. Any old address that slipped through the map shows up here. Each one is a redirect to add.
- Performance by page. Compare clicks and impressions for your top pages with the weeks before launch.
- Queries. Compare what you show up for now with what you showed up for before. A missing search usually points at a page whose words changed.
If a page drops and stays down, check it in this order. Does the old address reach it in one hop? Is the page indexed? Did its title and copy keep the words it used to rank for? Does its canonical point at itself?
Most drops trace back to one of those four. Fix the one you find, then give it time.
If the name is changing too
A rebrand that changes the domain puts a site move on top of a redesign, and two changes at once make it hard to tell which one moved the numbers. If you can, do them in stages. If you can't, use Search Console's change of address tool and keep the old domain and its redirects for good. How to rebrand without losing what already works covers the order. And if you're still choosing who builds the site, ask them who owns the URL map before you ask to see their portfolio. Here's where I'd start.
Not sure which problem you're looking at? The Quick Read is free and takes three minutes. It tells you whether it's the look, the message or something else. Take the Quick Read
Read next: Thinking about a website redesign? Decide what it has to do first. · How much does a website redesign cost? · How do you rebrand a business without losing what already works?