301 redirects wreck rankings after a redesign when old pages aren't matched to their new homes properly. If Google, users, and backlinks hit dead ends, homepage dumps, redirect chains, or the wrong status codes, your hard-earned visibility leaks away. A redesign changes the furniture. Bad redirects change the address without telling anyone.
Why 301 redirects matter after a redesign
A 301 redirect tells browsers and search engines that a page has moved permanently. It is the online version of forwarding your post after moving house. Without it, people turn up at the old address, find nothing, and leave muttering about how useless your website is.
Google uses URLs as part of how it understands your site. If your old service page ranked for a search term, picked up backlinks, earned trust, and brought in enquiries, you cannot just delete it during a redesign and hope Google works it out. Sometimes it does. Often it does not. Google is clever, not psychic.
A proper redirect keeps the connection between the old URL and the new one. It helps preserve rankings, referral traffic, bookmarks, links from other websites, and the general SEO value you have already built.
If you want the nuts and bolts first, I have covered how redirects work and why getting them wrong kills your rankings in more detail. This article is about the redesign mistakes that cause the damage.
Mistake 1: Building the redirect map after launch
The redirect map should be built before the new site goes live. Not after. Not once traffic drops. Not when Dave from sales asks why the phone has gone quiet. Before.
A redirect map is a simple document showing each old URL and the new URL it should point to. It sounds boring because it is. Most important SEO work is boring. That is why it gets skipped, and that is why rankings get battered.
You need to collect every important URL from the old site. That means more than the pages in the menu. Blog posts, old landing pages, product pages, PDF links, location pages, campaign URLs, and any page that has backlinks or search traffic should be checked.
| Source | Why it matters |
|---|---|
| Website crawl | Finds live pages, hidden pages, and odd URLs your menu ignores |
| Google Search Console | Shows pages Google already knows about |
| Analytics data | Identifies pages that brought traffic or enquiries |
| Backlink tools | Finds URLs with links from other websites |
| Old XML sitemaps | Catches legacy pages that may still matter |
If your web designer launches first and asks about redirects later, you are already playing SEO whack-a-mole.
Mistake 2: Redirecting everything to the homepage
Redirecting every old URL to the homepage is lazy. There, I said it. It is also one of the quickest ways to tell Google that you have no idea what each old page was about.
If an old page about emergency plumbing redirects to the homepage, that is not a proper replacement. If a blog post about boiler pressure redirects to a generic services page, that is not ideal either. The redirect should go to the closest matching new page.
This matters even more on large sites with lots of categories, listings, or location pages. A property platform with pages for specific areas, like a site helping users find office space for rent in Malta, cannot just send old listing or location URLs to the homepage and expect everything to be fine. The same logic applies to trades, e-commerce, accountants, clinics, and any local business with service-specific pages.
Good redirect matching keeps the topic clear. Bad matching turns your site into a confusing mess. Google dislikes confusing messes. So do customers.
Mistake 3: Using 302 redirects when you mean 301 redirects
A 302 redirect means a move is temporary. A 301 redirect means a move is permanent. During a redesign, most old URLs are permanently replaced by new URLs, so a 301 is usually the right choice.
This mistake happens when developers use default settings, plugins are configured badly, or nobody checks the status codes after launch. The redirect might look like it works in your browser, but search engines read the status code behind the scenes. That code tells them how to treat the move.
| Redirect type | Best used for | What it tells search engines |
|---|---|---|
| 301 | Permanent page move | The old URL has been replaced for good |
| 302 | Temporary page move | The old URL may come back later |
| 307 | Temporary redirect | The move is temporary and method should be preserved |
Using a 302 for a permanent redesign can slow down how signals transfer from the old URL to the new one. It may not always ruin everything, but why make Google guess? Use the right tool for the job.
Mistake 4: Creating redirect chains and loops
A redirect chain happens when one URL redirects to another, which redirects to another, which redirects to another. Old page A goes to page B, page B goes to page C, page C goes to page D. It works, eventually, but it is messy and slow.
A redirect loop is worse. Page A redirects to page B, and page B redirects back to page A. The browser gives up. Google gives up. Everyone gives up. Lovely.
Chains often appear when a site has had several redesigns over the years. Nobody cleans up the old redirects. New ones get added on top. Before long, your website has a redirect history that looks like a family tree after three divorces and a disputed will.
The fix is simple in principle. Redirect the original URL directly to the final destination. If /old-page/ now needs to land on /new-page/, send it there in one jump. Do not send it through two retired versions of the website first.
This improves crawl efficiency, page speed, and clarity. More importantly, it removes unnecessary friction between Google, your old rankings, and your new pages.
Mistake 5: Changing URLs that did not need changing
Some redesigns cause ranking drops because the URLs changed for no good reason. Not every page needs a new address just because the site looks different.
If a page already ranks, brings enquiries, and has a clean enough URL, think very carefully before changing it. Keeping the same URL is often safer than redirecting it. A redesign can update layout, copy, images, navigation, and calls to action without moving the page at all.
This is where design and SEO sometimes clash. Designers like tidy structures. Business owners like fresh starts. Developers like rebuilding things cleanly. Google likes continuity. If the old URL is doing a job, do not bin it just because someone thinks /services/cheshire-electrician/ looks nicer than /electrician-cheshire/.
There are good reasons to change URLs. Maybe the structure is awful, duplicated, confusing, or full of old CMS junk. Fine. Change them carefully and redirect them properly.
But changing URLs purely for aesthetics is SEO vanity. Vanity does not pay wages.
Mistake 6: Forgetting internal links, canonicals and XML sitemaps
Redirects are not the only thing that needs updating after a redesign. If your new site still links internally to old URLs, you are forcing users and Google through unnecessary redirects every time they move around the site.
Internal links should point directly to the final live URLs. Your XML sitemap should only include final indexable URLs. Canonical tags should reference the correct new pages, not retired versions from the old site. Robots rules should not block the new pages either, which sounds obvious until you have seen a staging block carried over to launch. Yes, that happens. More often than it should.
Check these items before and after launch:
- Navigation links
- Footer links
- Blog links
- Service page links
- Canonical tags
- XML sitemap URLs
- Hreflang tags if you use them
- Robots.txt rules
A redirect should be a safety net, not the main route through your website. If every internal click triggers a redirect, your site has been launched half-finished.
Mistake 7: Ignoring the pages that actually make money
Business owners often worry about the homepage during a redesign. Fair enough, it is the page everyone argues about in meetings. But rankings and leads usually come from individual service pages, location pages, product pages, and helpful blog content.
If your drain repair page brings in calls, that page needs special attention. If your Cheshire accountant page ranks well, protect it. If an old guide gets backlinks and sends customers into your funnel, do not throw it in the digital skip.
Before launch, identify your high-value pages. These are pages with traffic, rankings, enquiries, backlinks, or commercial importance. Then make sure each one has a proper destination on the new site.
Do not treat every URL equally. A forgotten privacy policy is annoying. A forgotten lead-generating service page is expensive.
This is also where many redesigns expose weak planning. If the new site does not have a replacement for a high-value old page, you have not redesigned the site properly. You have removed an asset. That is not improvement. That is self-sabotage with nicer fonts.
Mistake 8: Letting your developer handle redirects without an SEO brief
Good developers are worth their weight in gold. But development and SEO are different jobs. A developer can make redirects work technically. That does not mean they know which old page should point where, which pages have backlinks, which pages rank, or which URLs bring enquiries.
You need an SEO brief before the build starts. It should explain which URLs must be preserved, which can change, which pages need redirects, which pages should not be indexed, and what needs testing after launch.
Without that brief, your developer is guessing. They might make logical technical decisions that are terrible SEO decisions. Not because they are bad at their job, but because nobody gave them the right information.
This is exactly the sort of thing covered in proper technical SEO. It is not glamorous, but it keeps your website from falling on its face when a redesign goes live.
If your redesign project has a designer, developer, copywriter, and business owner involved, add an SEO person before launch. Adding one after the crash is more expensive and much more irritating.
Mistake 9: Assuming launch day is the finish line
Launch day is not the finish line. It is the point where the real checking starts. A redesign can look perfect on the surface while redirects, indexation, metadata, tracking, and internal links are quietly making a mess underneath.
Some ranking movement after a redesign is normal. Google needs to crawl the new site, process redirects, reassess pages, and update its index. A bit of wobble does not mean disaster.
But a major drop in impressions, clicks, calls, form fills, or indexed pages is not something to ignore. The first few days and weeks after launch matter. That is when you catch problems before they settle in and become harder to fix.
At minimum, you should monitor Google Search Console, analytics, form submissions, phone call tracking if you use it, and rankings for your most important terms. Look for patterns. One page dropping might be a page issue. Everything dropping might be a sitewide technical cock-up.
Do not let anyone tell you to just wait three months if the data clearly shows something is broken.
How to build a safe 301 redirect plan before a redesign
A safe redirect plan is not complicated. It just needs doing properly. The earlier you start, the less painful it is.
Use this process before the new site goes live:
- Crawl the old website and export all live URLs.
- Export performance data from Google Search Console and analytics.
- Identify URLs with backlinks using your SEO tool of choice.
- Match each old URL to the most relevant new URL.
- Keep existing URLs where there is no strong reason to change them.
- Test the redirects on staging or immediately at launch.
- Crawl the new site after launch to find errors, chains, loops, and old internal links.
If your site is built on WordPress, this planning still matters. Plugins can help manage redirects, but they do not decide the strategy for you. That is why WordPress SEO should include redirect planning, crawl checks, and post-launch testing, not just installing a plugin and hoping for the best.
Hope is not a redirect strategy. Hope is what people use when nobody has opened the spreadsheet.
How to test redirects after the new site goes live
Testing redirects means checking what actually happens, not what everyone assumes happens. Your browser is not enough. It may hide issues because of caching, previous visits, or extensions.
After launch, crawl the old URLs and confirm they return a 301 status code and land on the correct final destination. Then crawl the new website and check that internal links point directly to final URLs, not old ones.
You should also test your most important pages manually. Search for them in Google, click old indexed results if they still appear, and make sure they land somewhere sensible. Check forms, buttons, menus, and page templates while you are there.
Important checks include:
- Old URL returns a 301, not a 302 or 404.
- Final destination returns a 200 status code.
- Redirect goes to a relevant page, not the homepage by default.
- There are no chains or loops.
- Canonicals and sitemaps use the new final URLs.
If that sounds dull, it is. But it is less dull than explaining to your team why leads disappeared after the shiny new site launched.
What to do if rankings already dropped after a redesign
If your rankings have already dropped, do not panic, but do not sit there stroking your chin for six weeks either. Start with the basics. Crawl the old URLs, check status codes, review Search Console errors, and compare old top-performing pages with their new destinations.
Look for obvious failures first. Are old URLs returning 404s? Are they all going to the homepage? Are important pages blocked from indexing? Did the new site remove content that used to rank? Did title tags and headings get rewritten into vague nonsense? Did tracking break, making it look like leads disappeared when they are simply not being recorded?
Once you find the cause, fix it cleanly. Reinstate missing pages if needed. Add proper 301 redirects. Update internal links. Resubmit the sitemap. Request indexing for key pages in Search Console. Then monitor recovery.
You cannot always get everything back overnight. But quick, tidy fixes give you the best chance. The longer bad redirects stay live, the more awkward the recovery can become.
Frequently Asked Questions
What is a 301 URL redirect? A 301 URL redirect is a permanent instruction that sends users and search engines from an old URL to a new one. It is commonly used during website redesigns, domain changes, page moves, and content consolidation. When used correctly, it helps preserve SEO signals, traffic, and user access to old pages.
Can bad 301 redirects really damage rankings? Yes. Bad redirects can damage rankings if important old pages are sent to irrelevant pages, left as 404 errors, chained through multiple URLs, or redirected with the wrong status code. Google needs clear page-to-page signals. If those signals are messy, rankings and traffic can drop after a redesign.
Should every old page be redirected after a redesign? Not always. Important pages with traffic, rankings, backlinks, or useful content should usually be redirected to the closest relevant new page. Thin, duplicated, outdated, or useless pages may not need redirecting. The key is deciding page by page rather than dumping everything onto the homepage.
How long does it take Google to process 301 redirects? Google can discover redirects quickly, but processing them fully can take days, weeks, or longer depending on crawl frequency, site size, internal links, and technical quality. Important pages on active websites are usually picked up faster. Clean redirects, updated sitemaps, and strong internal links help speed things up.
Is it better to keep old URLs during a redesign? If an old URL already ranks, brings leads, and has a sensible structure, keeping it is often safer than changing it. A redesign does not automatically require new URLs. Change URLs only when there is a clear reason, such as fixing a poor structure, removing duplication, or improving long-term site organisation.
Do I need an SEO specialist before a website redesign? If your website gets traffic, leads, bookings, or sales from Google, yes. SEO input before launch can prevent redirect mistakes, lost rankings, indexation issues, and broken tracking. Bringing SEO in after traffic drops usually costs more and takes longer because the damage has already happened.
