What this guide will help you do
Redirect moved pages cleanly while protecting visitors, crawl efficiency, and accumulated search signals.
Key takeaways
- Redirect an old URL to the closest relevant final destination.
- Update internal links so visitors and crawlers do not travel through a redirect.
- Keep a tested redirect map during migrations and retain redirects long enough for old links to remain useful.
When a 301 redirect is the right tool
Use a permanent redirect when a page has moved, two pages have been merged, a URL format has changed, or one protocol or hostname should replace another. Visitors should land directly on a page that satisfies the same need as the old address.
A relevant category can be a reasonable destination when a product is permanently gone and no close replacement exists. Sending every removed URL to the homepage creates a poor experience and may be treated like a soft 404.
How chains and loops happen
A chain forms when A redirects to B and B later redirects to C. This often happens because teams keep adding rules without updating the original one. A loop happens when rules eventually send the request back to a URL already visited.
Each extra hop adds latency and another point of failure. Fix the first rule so A goes directly to C, update links to C, and remove contradictory HTTP-to-HTTPS, www, locale, and trailing-slash rules.
Build a migration redirect map
Export the old site's indexable URLs, top landing pages, backlinks, sitemap URLs, and valuable files. Map each old address to a specific new destination. Review unmatched pages manually instead of using a broad pattern that silently sends them somewhere irrelevant.
Test the map in a staging environment when possible. Check status codes, final destinations, loops, chains, query strings, fragments where important, and case sensitivity. Crawl both the old list and the new site immediately after launch.
What to update after redirects work
Redirects are a safety net, not an internal navigation system. Replace old URLs in menus, body links, canonicals, hreflang, structured data, feeds, and XML sitemaps. This gives crawlers a direct and consistent path.
Monitor 404s and redirect traffic after launch. Do not remove redirects simply because the new pages are indexed; old bookmarks and external links can continue sending useful visitors for years.
A practical next-step checklist
- Create an old-to-new URL map.
- Reject irrelevant homepage redirects.
- Test for one-hop destinations, loops, and errors.
- Update every internal reference to the final URL.
When you make a technical change, test a small group of representative URLs first. Then run the free SEO audit to catch broken links, metadata gaps, crawl signals, and page-level regressions before applying the change across the whole site.
Frequently asked questions
What is the difference between a 301 and 302 redirect?
A 301 communicates a permanent move. A 302 is normally used for a temporary change when the original URL is expected to return.
How many redirect hops are acceptable?
Aim for zero in internal links and one from an old external URL. Browsers may follow more, but every hop adds delay and risk.
Should removed pages redirect to the homepage?
Only when the homepage truly answers the same need, which is uncommon. Use the closest relevant replacement or return a clear 404/410 when none exists.
Primary references
Use these first-party references to confirm details that may change after this guide is published: