Before your redesigned site goes live, finalize a 1:1 redirect map and implement 301 redirects for every high-priority old URL: that single step preserves most of your search equity. Prioritize pages by traffic, backlinks, and conversions, build the map in a spreadsheet, and test it in staging before launch. Then run a second audit on the live site and keep the redirects active until your rankings and traffic settle.
TL;DR:
- Properly mapping and testing all high-priority old URLs with 301 redirects can preserve up to 85% of link authority during a redesign.
- Building a comprehensive redirect spreadsheet from multiple sources ensures no valuable pages or backlinks are missed before launch.
- Implementing server-level redirects and avoiding chained or duplicate rules prevents SEO issues and reduces load delays.
- Conducting thorough pre- and post-launch audits with tools like header checkers, crawlers, and Search Console helps identify and fix redirect errors quickly.
- Maintaining redirects for at least 180 days and monitoring traffic and indexing over time preserves search signals and prevents soft 404s.
Table of Contents
- Why redirects matter after a website redesign
- Build a redirect map before you touch a single URL
- How to implement redirects across different platforms
- Test and audit redirects before and after launch
- Special assets and edge cases you can't skip
- Timing, retention, and Search Console's Change of Address tool
- Common pitfalls and how to catch them fast
- What a redesign practitioner wishes teams did differently
- How Forge Web Studio handles redirects during a redesign
- Sources
- FAQ
Why redirects matter after a website redesign
A redirect tells search engines and browsers that a page has permanently moved, so the authority built up by links, shares, and years of indexing transfers to the new URL instead of disappearing. Skip that step and every old page that still gets clicked or crawled returns a 404, which strands visitors and tells Google the content is simply gone.
The most common mistake is redirecting a batch of old pages to the homepage instead of their closest equivalents. Search engines often read that pattern as a signal of a broken site, sometimes called a soft 404, and it can undercut the very rankings you're trying to protect.
A correct 301 redirect strategy can preserve most of a page's earned link authority, according to Stony Brook University's web support guidance. That number is the difference between a redesign that keeps its search traffic and one that has to rebuild it from scratch.
Build a redirect map before you touch a single URL
The redirect map is the single most important document in a redesign. It needs to be finalized, reviewed, and tested before launch day, not assembled after something breaks.
Pull your old URL list from several sources so nothing gets missed: your analytics platform, a full site crawl of the old site, a Google site: search of indexed pages, your backlink reports, and any campaign or affiliate URL lists that marketing has been running. Each source catches pages the others miss, especially old landing pages that no longer show up in navigation but still receive traffic.
Your spreadsheet needs at least these columns:
- Old URL: the exact path being retired.
- New URL: the destination it maps to.
- Status code: almost always 301 for a permanent move.
- Priority tier: how urgent this mapping is to test and verify.
- Source of discovery: analytics, crawl, backlinks, or campaign list.
- Notes: anything unusual, like a page being merged or discontinued.
Score priority using traffic volume, backlink count, and conversion history. A page with heavy inbound links but low traffic still deserves a high tier because the link equity attached to it matters even if visits are modest.
Pro Tip: Use pattern-based, section-level redirects for large URL groups that share a structure (like a blog archive), but map high-traffic and high-backlink pages one-to-one so each lands on its true equivalent instead of a generic category page.
How to implement redirects across different platforms
Where you set the redirect depends on your stack, and the choice affects both performance and how easily you can manage hundreds of mappings.
Server-level rules are the most reliable option for scale. On Apache, a simple Redirect 301 line in .htaccess handles individual URLs, while mod_rewrite handles pattern-based rules for larger batches; InMotion Hosting's walkthrough covers both with working examples and cPanel steps. Nginx uses its own rewrite syntax and tends to process large rule sets faster than Apache.
For WordPress sites, plugins like Redirection or Yoast's redirect manager make small to medium mappings easy to maintain without touching server files, though they start to slow down once you're managing several thousand rules.
CDN or edge-level redirects are worth considering when you're also moving hosting providers or restructuring how static assets are served, since they can handle redirects closer to the visitor before a request ever reaches your origin server.
Avoid JavaScript redirects and meta refresh tags. They load the old page first, delay the redirect, and search engines treat them as a much weaker signal than a server-level 301.
- Order your rules carefully: put specific, one-to-one redirects before wildcard patterns so a broad rule doesn't accidentally catch a URL meant for a precise match.
- Avoid chaining: a redirect that points to another redirect adds load time and can eventually break.
Pro Tip: Test every wildcard rule against a handful of real old URLs before launch: a pattern that looks correct on paper can silently misroute an entire folder of pages.
Test and audit redirects before and after launch
Testing happens twice: once on staging before the new site goes live, and again on the production domain right after launch.
- Crawl the staging server and confirm that every mapped URL returns the correct destination and status code before anything goes public.
- Run a full crawler on the live site immediately after launch to catch anything that behaved differently in production.
- Spot-check high-priority URLs with a header-checker tool to confirm each one returns a clean 301, not a 302 or a 200 on the wrong page.
- Use URL Inspection in Search Console on your top pages to see how Google itself is reading the new setup.
- Watch organic traffic, impressions, and your "Links to your site" report over the following weeks as the clearest sign that signal transfer is actually working.
| Signal to check | Tool | What a problem looks like |
|---|---|---|
| Status code | Header-checker tool | 302 or 200 instead of 301 |
| Redirect path | Site crawler | Multiple hops (a chain) |
| Indexing status | Search Console URL Inspection | Old URL still indexed weeks later |
| Traffic transfer | Analytics | Organic visits drop with no recovery |
When something's off, the fix is usually simple: swap a 302 for a 301, collapse a chain into one hop, or clear a cache that's still serving the old response. Accidental 302s are common enough that it's worth a dedicated pass, as SE Ranking's comparison of 301 and 302 redirects points out.
Special assets and edge cases you can't skip
Redirects aren't just for HTML pages. Images, PDFs, and other binary files need the same care, and they're the ones teams forget most often.
- Images moving to a CDN need either a 301 from the old image URL to its new CDN location or updated
srcreferences across every page that displays them. - PDFs and other documents should redirect to the most relevant new resource, never to the homepage, or you risk the same soft 404 pattern that affects HTML pages.
- Canonical tags work alongside redirects, not instead of them: use
rel=canonicalto indicate a preferred version among similar pages, but rely on a 301 whenever a URL has actually moved. - Sitemaps and hreflang entries need to point to the new URLs before launch, so search engines are never crawling a map full of redirects.
Timing, retention, and Search Console's Change of Address tool
File a Change of Address in Search Console only after your redirects are live and tested, and only if you're moving to a new domain rather than restructuring URLs on the same one. According to Google's own guidance, the tool's effects can be tracked for about 180 days, though many practitioners keep the underlying redirects active for far longer than that.
Keep the old domain registered even after traffic has fully moved. An expired domain can be picked up for phishing, and as long as external sites still link to your old URLs, those redirects are still doing work.
Common pitfalls and how to catch them fast
Most post-launch redirect problems trace back to a handful of repeat offenders.
- Redirect chains and loops: a URL that hops through two or three redirects before landing, or one that loops back on itself.
- Accidental 302s: often left over from a staging environment that never got updated to permanent redirects.
- Mass redirects to the homepage: the fastest way to trigger the soft 404 pattern instead of preserving a page's value.
- Cache-related false negatives: a redirect that's actually working but appears broken because a browser or CDN cache is still serving the old response.
Pro Tip: Before assuming a redirect is broken, test it in an incognito window or with a fresh header-checker request; half of "broken" redirects turn out to be cached results.
What a redesign practitioner wishes teams did differently
The redesigns that go smoothly are the ones where developers and SEOs agree on the mapping spreadsheet format and a testing deadline before a single line of code changes. Bring in whoever owns campaign URLs and affiliate links early, too, since those are the mappings that get forgotten until a partner emails asking why their link now 404s.
When a team doesn't have the bandwidth to build the map, implement server rules, and run two rounds of audits on top of everything else a launch requires, bringing in a partner who's handled this kind of migration before is usually cheaper than untangling it after the fact.
— Dylan
How Forge Web Studio handles redirects during a redesign
Forge Web Studio builds the redirect map, implements the 301 rules at the server or CMS level, tests everything in staging, and audits again once the new site is live, all as part of a website redesign project. The redirect and testing work happens on the same tight timeline as the rest of the launch rather than as an afterthought bolted on at the end.
- Redirect mapping and prioritization: built from your analytics, backlinks, and old sitemap.
- Server-level 301 implementation: set up correctly the first time, without relying on fragile plugins.
- Staging and production testing: two full passes before anything is called done.
- Post-launch monitoring: watching traffic and indexing for weeks, not just launch day.
If you're planning a redesign and want the redirect work handled alongside it, see pricing for Starter, Growth, and Custom Business Website projects or start a website project to get a scoped plan.
Sources
Lean on Google's Change of Address guidance for domain moves and its URL Inspection tool for checking how individual pages are being read post-launch. A header-checker tool and a full-site crawler cover most status-code auditing. For a longer view on migration timelines, this 4 to 8 week site migration guide walks through the process from an SEO consultancy's perspective.
- Use redirect spreadsheet — Stony Brook University Web Support
- Change of address — Search Console Help
- How to set up a 301 permanent redirect via .htaccess — InMotion Hosting
FAQ
How do I fix broken redirects after launch?
Start by identifying whether the issue is a wrong status code, a chain, or a caching problem, since each has a different fix. Replace any 302 with a proper 301, collapse multi-hop chains into a single redirect, and clear server or CDN caches before retesting with a header-checker tool.
Is a redirect bad for SEO?
A correctly implemented 301 redirect is not bad for SEO. It's the mechanism that preserves link authority during a move, and Stony Brook University's guidance notes that a correct strategy can preserve up to 85% of that authority, while a poorly mapped redirect (especially one sending many pages to the homepage) is what causes ranking problems.
Why do I keep getting redirected on a site I visit often?
Ongoing redirects usually mean the site has moved a page or domain and set up a permanent forward from the old address to the new one. If it happens repeatedly on unrelated pages, the site may be running a broad, generic redirect rule rather than proper page-to-page mapping.
Is a 301 redirect permanent?
Yes, a 301 status code specifically signals a permanent move, which is why it's the right choice for a completed redesign or domain change rather than a temporary one. A 302, by contrast, signals a temporary redirect and should only be used for content still in development.
How long should I keep 301 redirects active after a redesign?
Search Console's Change of Address guidance tracks the move for about 180 days, but many practitioners keep redirects live well beyond that window since external backlinks to old URLs can persist for years. The safest approach is to keep them active as long as any meaningful traffic or links still point to the old address.