A website redesign can quietly wipe out years of SEO progress if the old URLs disappear without a map telling Google — and your visitors — where everything moved. The fix isn’t complicated, but it has to be done methodically and before the new site goes live, not after traffic starts tanking.
Table of Contents
This guide walks through building a redirect map, implementing 301 redirects correctly, and verifying the migration so search engines transfer rankings to your new URLs instead of treating them as a brand-new site.
Quick Answer
Before launch, crawl your current site to get a full list of live URLs, then create a one-to-one 301 redirect from every old URL to its closest matching new URL (never dump everything on the homepage). Keep those redirects live for at least six months to a year, update your sitemap and internal links to point straight to the new URLs, and use Google Search Console to confirm old pages drop out of the index while new ones get indexed.
Step 1: Inventory Every URL Before You Touch the Old Site
You can’t redirect what you haven’t catalogued. Before the redesign goes live, crawl the existing site with a tool like Screaming Frog SEO Spider (free for crawls under 500 URLs) to export a full list of indexable pages, along with their status codes and titles. Cross-check that list against Google Search Console’s Page Indexing report and your analytics’ top-pages report so you know which URLs actually carry traffic and backlinks — those need the most careful handling.
Pay extra attention to pages with inbound links from other sites, pages ranking for valuable keywords, and category or hub pages other posts link to internally. Losing the redirect on a low-traffic page is a minor annoyance; losing it on a page with external backlinks throws away link equity you can’t easily rebuild.
Step 2: Build a One-to-One Redirect Map
For every old URL, identify the single new URL that covers the same topic or intent. Where content was consolidated or a page was genuinely retired with nothing equivalent, redirect to the closest related category or hub page rather than the homepage — a ‘catch-all to homepage’ approach signals a sloppy migration to search engines and gives users a confusing experience, and Google has said redirecting to an unrelated page can get the redirect treated as a soft 404 instead of a real move.
Implement the redirects as 301s (permanent), not 302s (temporary) — a 301 tells Google to treat the destination as the canonical URL and consolidate the old page’s ranking signals there, while a 302 tells it the move is temporary and the old URL should stay indexed. Set these up at the server or CMS level (via .htaccess, nginx config, or your platform’s redirect manager) so they fire before any page content loads. Still avoid chaining redirects (old URL to URL B to URL C): Google has confirmed that 301s themselves don’t bleed away ranking signal, but each extra hop adds load time, and browsers and crawlers will stop following a chain after enough hops — so point every old URL straight at its final destination instead of letting it bounce through intermediate ones.
Step 3: Update Internal Links, Sitemap, and Submit to Google
Redirects are a safety net, not a substitute for clean internal linking — update your navigation, footer, and in-content links to point directly at the new URLs so crawlers and users aren’t bouncing through redirects unnecessarily. Regenerate and submit a fresh XML sitemap containing only the new URLs through Google Search Console.
If the redesign also changed domains (not just URL structure), use the Change of Address tool in Search Console settings to formally tell Google about the move, in addition to having the 301s in place. If you only restructured URLs on the same domain, the redirects plus a resubmitted sitemap are enough — no Change of Address step needed.
Tips / Common Mistakes
Don’t remove the old redirects too soon — plan to keep them active for at least six months to a year after launch, and longer if possible, since older backlinks and bookmarks can still point to legacy URLs for years. Watch the Search Console Page Indexing report in the weeks after launch: you want to see old URLs marked as redirects and gradually drop out of the index while new URLs climb in. A sudden spike in 404s in that report usually means a URL was missed in the redirect map — check the Not Found section regularly during the first month.
Also avoid redirecting everything to a single URL, redirecting HTTPS pages back to HTTP, or leaving redirect loops in place (a URL that eventually redirects back to itself) — all of these confuse crawlers and can stall indexing of the new site. Re-crawl the live site with the same tool you used for the pre-launch inventory to confirm every old URL returns a single 301 straight to its new destination with a 200 OK status.
Explore more: More digital strategy guides.
301 redirects after a website redesign FAQs
How long should I keep 301 redirects active after a redesign?
At minimum six months to a year, and indefinitely if your hosting setup allows it — old backlinks, bookmarks, and cached search results can point to legacy URLs for a long time, and removing a redirect too early turns a working link into a broken one.
Will I lose rankings even with perfect 301 redirects?
Google has confirmed that a correctly implemented 301 redirect doesn’t itself cause ranking signals to be lost — the signals move to the new URL. Any dip you see is usually just the normal time it takes Google to re-crawl and re-index the new URLs, and a clean one-to-one redirect map with updated internal links and sitemap keeps that window as short as possible.
Should I redirect everything to my new homepage if I can’t match every old page?
No — redirect to the most topically relevant new page or category hub instead. Mass redirects to the homepage look like a low-quality migration to search engines and give visitors an irrelevant landing page.
Do I need Google Search Console’s Change of Address tool for a redesign?
Only if you’re also changing domains. If you’re keeping the same domain and just changing URL paths or site structure, 301 redirects plus a resubmitted sitemap are sufficient.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Want dev news in your inbox? Subscribe to the free newsletter.
Photo by Mark Fletcher-Brown on Unsplash.