The fear behind most delayed redesigns is simple: “What if we lose our Google rankings?” It is a fair worry. Rankings are tied to URLs, content and internal links, and a redesign can change all three at once. The good news is that traffic losses after a redesign are almost always caused by a short list of avoidable mistakes. Here is how to redesign a website without losing SEO, step by step.
This guide is part of our website redesign services resources, which explain how we plan, build and support this kind of work.
Why redesigns lose traffic
Search engines rank individual pages, not your brand. When a redesign changes or removes the pages that ranked, those rankings have nothing to attach to. The usual causes are:
- Changed URLs without redirects, so old links and rankings point to 404 pages.
- Removed or shortened content, so the page no longer answers what people searched for.
- Lost on-page signals such as title tags, headings and structured data replaced by template defaults.
- Broken internal linking, where important pages disappear from the navigation and lose authority.
- Technical blockers such as a leftover noindex tag, a blocked robots.txt or slower templates.
Each of these has a fix you can plan before launch.
Step 1: Find the pages that matter
Export the last 12 months of data from Google Search Console (clicks and impressions by page) and Google Analytics 4 (conversions by landing page). Combine them into one list and mark each URL as:
- Protect — pages with meaningful search traffic, leads or external links.
- Improve — pages that rank on page two or three, or convert poorly.
- Merge or remove — thin, outdated or duplicate pages.
Check backlinks too. A page with links from other sites carries authority even if it gets little traffic, and that authority should be passed on with a redirect.
Step 2: Keep or map every URL
The safest URL is the one that does not change. Keep existing URLs for every “protect” page unless there is a strong reason to move it. For every URL that does change, create a one-to-one 301 redirect to the most relevant new page.
- Redirect to the closest equivalent, not the home page. Mass redirects to the home page are treated much like 404s.
- Avoid chains. If an old URL already redirects, point it straight to the final destination.
- Keep the redirects in place long term. Removing them after a few months throws away the signals they pass on.
Step 3: Carry content over, then improve it
Design teams often want shorter pages. Search engines and buyers usually want the opposite. For pages you are protecting:
- Keep the topics, headings and answers that matched what people searched for.
- Keep the main keyword in the title tag, H1 and opening paragraph.
- Improve readability with better structure, visuals and FAQs rather than by deleting text.
When you merge pages, combine their best content into the surviving page and redirect the others to it.
Step 4: Rebuild on-page SEO in the new templates
Check that each new template supports a custom title tag and meta description, one H1, a logical H2 and H3 structure, image alt text, canonical tags and structured data. Then make sure the values from the old site are actually moved across — templates that fall back to “Page title | Site name” on every page are a common cause of post-launch drops.
Step 5: Keep internal links strong
Pages that were linked from the main navigation or the home page receive a lot of internal authority. If the new navigation drops them, link to them from relevant service pages, footers or hub pages instead. Update links in your content to point to new URLs directly rather than relying on redirects.
Step 6: Test on staging, then launch carefully
- Block the staging site from search engines, and remove that block at launch.
- Crawl staging and compare it with a crawl of the live site: titles, H1s, status codes, canonicals and internal link counts.
- Test every redirect in your map.
- Check Core Web Vitals on the new templates. A slower site can cost rankings even if everything else is right.
- Submit the new XML sitemap in Google Search Console on launch day.
Step 7: Monitor and fix fast
For the first two weeks, check Search Console daily for new 404 errors, indexing drops and position changes on your protected pages. Re-crawl the live site to catch broken links and redirect chains. Expect some movement while Google re-crawls; investigate any protected page that drops sharply and does not recover within a few weeks.
A quick pre-launch SEO checklist
- Every changed URL has a one-to-one 301 redirect.
- Protected pages keep their content, keyword, title and meta description.
- No noindex tags or robots.txt blocks on the live site.
- XML sitemap updated and submitted.
- Analytics, conversion tracking and forms tested.
- Structured data rebuilt and validated.
- Core Web Vitals equal to or better than the old site.
For the full list of design, content and launch tasks, use our 25-point website redesign checklist.
Frequently asked questions
How long does it take for rankings to settle after a redesign?
Usually a few weeks, depending on how often Google crawls your site. Large sites and big URL changes take longer.
Can a redesign improve my rankings?
Yes. Faster pages, clearer structure, merged duplicate content and better internal linking often improve rankings once the new site is crawled.
Do I need to keep redirects forever?
Keep them for as long as possible, and at least a year. They cost almost nothing to maintain and continue to pass on links from other sites.
Should I change my domain at the same time?
Avoid it if you can. A domain change adds a second migration on top of the redesign and makes any traffic changes harder to diagnose.