Website Redesign Without Losing SEO: Step-by-Step Guide
Short answer: You can do a website redesign without losing SEO if you protect what search engines already know about your site. Crawl every old URL, map each one to its best new page, set up 301 redirects, keep the content that ranks, test everything on a staging site before launch, and watch Search Console closely afterwards. Most ranking drops after a redesign come from skipped steps, not from the new design.
"Website redesign" is searched about 880 times a month in the US (Google search data via DataForSEO, US, November 2026). Many of those searches come from owners who have heard horror stories about traffic falling off a cliff after launch. Here is how to avoid becoming one.
Why do websites lose rankings after a redesign?
Google ranks individual pages at individual URLs. When a redesign changes or removes those pages without telling Google where they went, the rankings and links attached to them are lost. The usual causes:
- Old URLs return 404 errors because no redirects were set up.
- Content that ranked was cut to make the new pages look cleaner.
- The new site was launched still blocked from search engines (a staging "noindex" left on, or robots.txt blocking everything).
- Titles, headings and internal links changed in ways that weaken what each page is about.
- The site got slower with heavy new images, sliders or scripts.
- Tracking broke, so problems went unnoticed for weeks.
Every one of these is preventable.
Step 1: Crawl and record the old site
Before anyone designs anything, build a complete list of your current URLs. Pull from several sources, because no single one is complete:
- A crawl of the live site with an SEO crawler
- Your XML sitemap
- Google Search Console (pages with clicks or impressions)
- Google Analytics (pages with visits)
- Backlink data showing which of your pages other sites link to
For each URL, record its title, main heading, monthly clicks, top search queries and number of linking sites. This becomes your master spreadsheet.
Step 2: Decide what stays, merges or goes
Go through the list and give each URL a decision:
| Decision | When to use it | What happens |
|---|---|---|
| Keep | Page ranks, gets traffic or has links | Same URL if possible, content kept or improved |
| Merge | Several thin pages cover the same topic | Combine into one stronger page and redirect the rest to it |
| Move | URL is messy but the page is valuable | New URL, with a 301 from the old one |
| Remove | Outdated, no traffic, no links, no value | Redirect to the closest relevant page, or let it return 410 if nothing fits |
The safest default is to keep good existing URLs exactly as they are. Every change you make needs a redirect.
Step 3: Map every old URL to a new one
Create a redirect map: one row per old URL, with the new destination beside it. Rules of thumb:
- Redirect to the most relevant new page, not to the home page by default.
- Use 301 (permanent) redirects. Our glossary explains how a 301 redirect works.
- Avoid redirect chains (old to older to new). Point every old URL straight at its final destination.
- Include old URL variations: with and without trailing slashes, old parameters, and http or www versions.
- Include URLs from any previous redesign that still have links pointing at them.
When we rebuilt this site, we redirected about 4,700 old URLs so the links pointing at them kept their value. Most sites are far smaller, but the principle is the same: no URL with traffic or links should be left to break.
Step 4: Protect the content that ranks
Design teams often want shorter pages. If a page ranks, find out why before cutting it. Usually it is the content that answers specific questions.
- Keep the main topics, headings and answers of ranking pages.
- Keep or improve page titles and meta descriptions.
- Keep internal links between related services and areas.
- Keep structured data, such as LocalBusiness and FAQ schema, and check it still validates.
- Carry over image alt text and file names where they are useful.
Improve content where you can, but do it deliberately. A good test: for each ranking page, list the three or four questions it answers today. The new version should still answer every one of them, in visible text, and ideally answer them better. If a section is cut, ask where that information now lives on the new site, and link to it.
Step 5: Test on a staging site before launch
Build the new site on a private staging address, blocked from search engines, and test:
- Redirects: run every URL in your redirect map and confirm each returns a single 301 to the right page.
- Crawl the new site: look for broken links, missing titles, duplicate pages and orphan pages with no internal links.
- Speed: test key pages on a phone and with Google's PageSpeed Insights.
- Forms and calls: submit every form and tap every phone link.
- Tracking: confirm analytics, key events and call tracking fire.
- Mobile layout: check the main pages at phone width.
For a deeper list of what to check, see our guide to technical SEO.
Step 6: Launch day checklist
- Remove the staging noindex and any robots.txt block
- Switch on the redirect map
- Confirm HTTPS works across the whole site
- Submit the new XML sitemap in Search Console
- Spot-check your 20 most important old URLs by hand
- Update your Google Business Profile website link if it changed
- Update links on your main directory listings and social profiles
Launch early in the week, when your team is available to fix problems, rather than on a Friday afternoon.
Step 7: Monitor for the next few weeks
Some movement while Google recrawls is normal. Large or lasting drops are not. Watch:
- Search Console Pages report: look for rises in "Not found (404)" and "Excluded" pages.
- Search Console Performance: compare clicks and impressions for key pages week by week.
- Crawl errors and server logs for old URLs still being requested.
- Calls and form leads compared with the same period before launch.
Fix any missed redirects as soon as you find them. Keep the redirect map in place for good; there is little benefit in removing old redirects.
Questions to ask your web designer
- Will you crawl and map every existing URL before design starts?
- Who builds and tests the redirect map?
- Will the staging site be blocked from search engines, and who removes the block at launch?
- How will you protect content that currently ranks?
- What will you monitor after launch, and for how long?
If a provider has no clear answers, budget for that work separately. Our guide to how much a website costs explains why redirects belong in the scope. Our web design service includes the full URL map and post-launch monitoring on every redesign, and our SEO team can audit a redesign that has already gone wrong.
Key facts
Most rankings lost in a website redesign come from missing redirects, removed content and launch-day mistakes, not the new design. Crawl and record every old URL, map each one to its best new page with a 301 redirect, keep or improve the content that ranks, test on a staging site, and monitor Search Console closely for several weeks after launch. When we rebuilt this site we redirected about 4,700 old URLs.
Questions
Will a website redesign hurt my SEO?
It does not have to. Rankings usually drop when old URLs break, ranking content is removed or the new site is blocked from search engines. A careful URL map, 301 redirects and testing avoid most of that.
What is a 301 redirect?
A 301 is a permanent redirect that sends visitors and search engines from an old URL to a new one. It tells Google the page has moved, so it can pass most of the old page's standing to the new address.
How long does it take rankings to settle after a redesign?
It varies with site size and how much changed. Small fluctuations for a few weeks are common while Google recrawls. Large or lasting drops usually point to a fixable problem such as broken redirects.
Should I change my URLs during a redesign?
Only when there is a clear benefit, such as fixing messy or duplicate URLs. Every changed URL needs a redirect, so keeping good existing URLs is the safest choice.