How to Redesign Your Website Without Losing Your Rankings
A redesign is the most reliable way to lose organic traffic, and it happens the same way every time: nobody mapped the old URLs to the new ones until after launch. The work that prevents it is unglamorous and takes a day.
Inventory before you design anything
Before a single page is built, export every URL that currently exists and attach data to each: organic sessions, impressions, conversions and inbound links. You need this from analytics, Search Console and a crawl of the live site.
This list is the thing you are protecting. Without it you cannot know what you broke, and you cannot prioritise. Pages with meaningful traffic or external links must survive the migration with a working destination.
Crawl the old site while it still exists. Once it is gone, reconstructing the URL list is far harder and you will miss pages nobody remembered.
Keep the URLs if you can
The safest redesign changes the design and not the addresses. Every URL change costs a little authority even when redirected correctly, and introduces a chance of error.
If URLs must change, change them once, deliberately, with a clear pattern. Avoid chained redirects where an old URL points to an intermediate that points somewhere else; each hop wastes crawl budget and dilutes signal. Map old directly to final.
Decide trailing slash and protocol behaviour explicitly and enforce it server-side, so that only one version of any URL is reachable. Check your redirect chains with our Redirect Chain Checker before and after launch.
Map every old URL to a real destination
Every removed URL needs a 301 to the closest equivalent page. Closest equivalent means a page serving the same intent, not the homepage. Bulk-redirecting everything to the homepage is treated as a soft 404 and loses the value entirely.
Where genuinely nothing equivalent exists, a 410 is more honest than a redirect to something irrelevant, and it removes the page from the index cleanly.
Test the mapping before launch, on staging, with the actual redirect rules rather than a spreadsheet. Redirect logic that looks correct in a document frequently behaves differently once regular expressions and server config are involved.
Pre-launch checks that catch the usual disasters
Two failures account for most catastrophic redesigns. First, the staging site had a site-wide noindex or a blocking robots.txt, and it shipped to production. Check both on the live site within minutes of launch.
Second, canonical tags still point at the staging domain. Crawl the live site and verify that canonicals reference the production URL.
Also confirm before launch: titles and meta descriptions carried over rather than reverting to template defaults, structured data still present and valid, internal links updated to the new URLs rather than relying on redirects, and analytics tracking actually firing.
The first month after launch
Expect some fluctuation. A modest dip for two to four weeks while Google reprocesses the site is normal. A sustained drop beyond six weeks is not.
Submit the new sitemap immediately and keep the old one available briefly so Google rediscovers the old URLs and follows the redirects. Watch Search Console coverage daily for the first fortnight: a spike in 404s or in "excluded by noindex" tells you exactly what broke.
If traffic drops hard, resist redesigning again. Crawl the old URL list against the live site, find which are not resolving to a good destination, and fix the redirects. That is the cause the overwhelming majority of the time.
Key takeaways
- Export every URL with its traffic, impressions and links BEFORE the old site disappears.
- Keep URLs unchanged if you can. Every change costs a little authority even when redirected right.
- Redirect each old URL to its closest equivalent, never in bulk to the homepage.
- Check for a leftover staging noindex and staging canonicals within minutes of launch.
- A dip for two to four weeks is normal; a sustained drop past six weeks means broken redirects.
Frequently asked questions
Will a redesign hurt my SEO?
Only if the migration is handled badly, which unfortunately is the norm. A redesign that keeps URLs, preserves content, maintains internal linking and does not regress page speed usually has no negative effect and can improve things. The damage comes from changing URLs without complete redirect mapping, dropping content that was ranking, losing title tags and structured data to template defaults, or shipping a staging noindex. None of these are inherent to redesigning; they are all preventable with a day of preparation.
Should I keep my old URLs?
Yes, wherever you reasonably can. Every URL change costs a small amount of accumulated authority even with a correct 301, and each one is an opportunity for a mistake. Change them only when there is a real benefit, such as fixing a genuinely broken structure or removing parameters. If you do change them, change them once, map old directly to final rather than through intermediate hops, and update your internal links to point at the new URLs rather than relying on the redirects permanently.
What redirect type should I use?
A 301 permanent redirect for anything moving to a new address, which passes the strongest signal and tells search engines to update their index. Use 302 only for genuinely temporary situations such as a seasonal page. For content that is gone with no equivalent, a 410 is more honest than redirecting somewhere irrelevant and removes the URL from the index more cleanly. Avoid chains entirely: if A once pointed to B and B now points to C, update A to point directly at C.
How long does it take to recover after a migration?
Google typically reprocesses a migrated site over two to four weeks, during which some fluctuation is normal and not cause for panic. Larger sites take longer because crawling all URLs takes longer. If organic traffic is still substantially down after six weeks, something is genuinely broken rather than settling. The usual culprit is redirect mapping: crawl your original URL export against the live site and find which old URLs are not resolving to a sensible destination.
What is the most common redesign mistake?
Shipping the staging site noindex directive to production. It is a single line, it is invisible unless you look for it, and it deindexes the entire site within days. The second most common is canonical tags still pointing at the staging domain, which has a similar effect. Both are checked in under a minute: view the live source and search for noindex, then crawl a sample of pages and confirm the canonicals reference the production URL. Do this within minutes of launch, not at the next review.
Should I redirect old pages to the homepage?
No. Google treats bulk redirects to the homepage as soft 404s, meaning the redirect passes no value and the old page effectively just disappears. Each old URL should point to the closest equivalent page serving the same intent. If a specific product is discontinued, redirect to its category or a genuine replacement. If truly nothing equivalent exists, return a 410 so the URL is removed cleanly. Homepage redirects also frustrate visitors, who arrive expecting specific content and get a generic landing page.