Redirect Chain Planner
Build and validate redirect chains visually. Add redirect hops with status codes (301, 302, 307, 308), detect redirect loops, flag chains over 3 hops, and generate .htaccess redirect rules. Plan your redirect strategy before implementing.
Need more power?
Sign up free and get AI-powered versions of this tool — plus 60+ more SEO tools.
Sign up free →How to use Redirect Chain Planner
Build and validate redirect chains visually. Add redirect hops with status codes (301, 302, 307, 308), detect redirect loops, flag chains over 3 hops, and generate .htaccess redirect rules. Plan your redirect strategy before implementing.
This tool runs entirely in your browser — your data never leaves your device. No account required, no daily limits, no API calls. Use it as many times as you need.
Why use Redirect Chain Planner?
- ✓ Instant results — no waiting for API responses
- ✓ 100% private — your data stays in your browser
- ✓ No sign-up, no email, no credit card
- ✓ Works on mobile and desktop
📖 What Is a Redirect Checker?
A redirect checker is a technical SEO tool that traces the full HTTP redirect chain from any URL to its final destination. It reveals every hop along the way — showing the HTTP status code (301, 302, 307, 308), response headers, and final landing page for each redirect. This is essential for diagnosing redirect chains that slow down your site, redirect loops that create infinite cycles, and misconfigured redirects that leak link equity or send users to the wrong page.
Redirects are one of the most critical yet error-prone aspects of technical SEO. A single misconfigured redirect rule can break entire sections of your site, waste crawl budget on unnecessary hops, or silently drain link equity from your most valuable pages. During site migrations, URL restructuring, or domain changes, hundreds of redirect rules must work perfectly together — and a single conflict can create loops or chains that frustrate users and confuse search engines. Our Redirect Checker traces every hop, identifies problems, and gives you the information needed to fix redirect issues before they damage your rankings.
📊 Redirect & Technical SEO Statistics
of websites have at least one redirect chain with 2+ hops that could be consolidated to a single redirect
added latency per redirect hop, directly impacting Core Web Vitals and user experience metrics
of link equity is passed through a properly implemented 301 permanent redirect to the destination URL
maximum redirect chain length Google will follow before giving up — best practice is 1 hop maximum
of site migration traffic losses are caused by redirect errors, including loops, chains, and missing redirects
of crawl budget is wasted on average by unnecessary redirect chains across enterprise websites
errors spike after migrations when redirect maps are incomplete — monitor Search Console for 30+ days
minimum recommended duration to keep 301 redirects active after a URL change or site migration
📝 How to Use the Redirect Checker
Enter a URL to Trace
Paste the URL you want to check into the input field. This can be any URL — an old page you've redirected, a shortened URL, or a page you suspect has redirect issues.
Trace the Redirect Chain
Click the check button to follow the URL through every redirect hop. The tool sends an HTTP request and follows each 3xx response until it reaches a non-redirect status code or the maximum hop limit.
Review Each Hop
Examine every redirect in the chain. For each hop, you'll see the HTTP status code (301, 302, 307, 308), the source URL, and the destination URL. Identify unnecessary intermediate redirects that can be eliminated.
Check the Final Status
Verify that the final destination returns a 200 OK status code with the expected content. If it returns a 404, 500, or another error, the entire redirect chain is effectively broken.
Identify Issues
Look for redirect chains (consolidate to a single hop), redirect loops (break the circular reference), mixed protocol redirects (HTTP to HTTPS inconsistencies), and temporary redirects used for permanent moves.
Fix and Re-check
Update your server configuration, .htaccess rules, or CMS redirect settings to fix identified issues. Re-run the checker to confirm the redirect now goes directly to the final destination in a single hop.
⚠️ Common Redirect Mistakes
❌ Using 302 temporary redirects for permanent URL changes like site migrations
✅ Use 301 redirects for permanent moves — 302s signal that the old URL should remain in the index
❌ Creating redirect chains with 3+ hops (A → B → C → D) instead of direct redirects
✅ Update all redirects to point directly to the final destination URL — eliminate intermediate hops
❌ Conflicting redirect rules that create infinite loops (A → B → A)
✅ Map out all redirect rules and remove circular references — check WWW/non-WWW and HTTP/HTTPS rules
❌ Redirecting to pages that return 404 errors or are themselves redirected
✅ Always verify that redirect destinations return a 200 status code and contain the expected content
❌ Not redirecting old URLs after a site migration, causing mass 404 errors
✅ Create a complete URL mapping before migration and implement 301 redirects for every old URL with traffic or backlinks
❌ Using meta refresh or JavaScript redirects instead of server-side HTTP redirects
✅ Always use server-side 301/302 redirects — they are faster, pass full link equity, and are properly followed by crawlers
❌ Redirecting all old pages to the homepage instead of corresponding new pages
✅ Redirect each old page to its most relevant equivalent on the new site — blanket homepage redirects are treated as soft 404s
❌ Removing 301 redirects too soon after a migration before search engines have updated their index
✅ Keep 301 redirects active for at least 1 year after a URL change to ensure full link equity transfer and index updates
💡 Pro Tips for Redirect Management
Audit Redirects Quarterly
Schedule regular redirect audits to catch chains, loops, and broken destinations before they impact rankings. Use our checker to trace high-traffic URLs and pages with valuable backlinks.
Prioritize by Link Equity
When cleaning up redirects, start with pages that have the most backlinks and organic traffic. These URLs carry the most link equity, so fixing their redirect chains has the biggest SEO impact.
Use Server-Level Redirects
Implement redirects at the server level (.htaccess for Apache, server blocks for Nginx, next.config.js for Next.js) rather than through CMS plugins when possible. Server-level redirects are faster and more reliable.
Log Redirect Activity
Monitor your server logs for redirect activity. High volumes of 301/302 responses indicate crawl budget waste. Look for patterns in redirected URLs to identify systematic issues.
Test Before Deploying
Always test redirect rules in a staging environment before pushing to production. A single regex error in .htaccess can create a redirect loop that takes your entire site offline.
Document Your Redirect Map
Maintain a spreadsheet mapping old URLs to new URLs with the redirect type and implementation date. This documentation is invaluable for debugging issues months or years after implementation.
Handle Trailing Slashes
Choose a trailing slash convention (with or without) and redirect the other variant. Inconsistent trailing slashes create duplicate content and split link equity between two URL versions.
Monitor Post-Migration
After a site migration, monitor Google Search Console daily for 30 days. Check for 404 spikes, crawl errors, and indexation drops that indicate missing or broken redirects.
🔗 Related SEO Tools
Canonical Tag Checker
Ensure canonical tags and redirects work together — conflicting signals confuse search engines about preferred URLs.
Robots.txt Validator
Verify that robots.txt isn't blocking redirect destination URLs from being crawled by search engines.
Sitemap Validator
Ensure your XML sitemap contains only final destination URLs and not redirected or broken URLs.
Meta Tag Checker
Validate meta tags on redirect destination pages to ensure they have proper SEO signals after the redirect.
❓ Frequently Asked Questions
What is a 301 redirect?
A 301 redirect is a permanent HTTP status code that tells browsers and search engines that a page has permanently moved to a new URL. It passes approximately 95–99% of link equity (ranking power) from the old URL to the new one. Use 301 redirects when you permanently rename or move a page, migrate to a new domain, or consolidate duplicate content. Search engines will eventually drop the old URL from their index and replace it with the new destination.
What is the difference between 301 and 302 redirects?
A 301 redirect signals a permanent move — search engines transfer link equity and update their index to the new URL. A 302 redirect signals a temporary move — search engines keep the original URL in their index and may not transfer full link equity. Use 301 when the change is permanent (site migrations, URL restructuring) and 302 when the change is temporary (A/B tests, seasonal pages, maintenance).
How many redirects is too many?
Google recommends keeping redirect chains to a maximum of 5 hops, but best practice is to have no more than 1 redirect between the source and final destination. Each hop in a redirect chain adds latency (50–100ms per redirect), wastes crawl budget, and can cause small amounts of link equity loss. Our Redirect Checker traces the full chain so you can eliminate unnecessary intermediate hops.
Do redirects pass link juice?
Yes, 301 redirects pass the vast majority of link equity ("link juice") to the destination URL. Google's Gary Illyes confirmed that 301, 302, and 307 redirects all pass PageRank without loss. However, redirect chains (multiple hops) can dilute link equity slightly with each hop, and very long chains may cause search engines to stop following them entirely.
What is a redirect chain?
A redirect chain occurs when a URL redirects to another URL that also redirects, creating multiple hops before reaching the final destination. For example: page-A → page-B → page-C → page-D. Redirect chains slow down page loading, waste crawl budget, and can cause link equity dilution. Ideally, every redirect should point directly to the final destination URL with a single hop.
How do I fix redirect loops?
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A, creating an infinite cycle. Fix redirect loops by mapping out all redirect rules in your .htaccess, server configuration, or CMS settings, then removing the circular reference. Common causes include conflicting WWW/non-WWW rules, HTTP/HTTPS redirect conflicts, and plugin conflicts in WordPress.
What is a 307 redirect?
A 307 Temporary Redirect is the HTTP/1.1 equivalent of a 302. The key difference is that 307 strictly preserves the HTTP method — if the original request was a POST, the redirected request must also be a POST. This makes 307 important for form submissions and API endpoints. For SEO purposes, 307 behaves like a 302 and signals a temporary move.
What is a 308 redirect?
A 308 Permanent Redirect is the HTTP/1.1 equivalent of a 301 that strictly preserves the HTTP method. Like a 301, it signals a permanent move and passes full link equity. The difference is that a 308 guarantees the request method won't change (POST stays POST), while a 301 may convert POST requests to GET. For standard page redirects, 301 and 308 are functionally equivalent for SEO.
How do redirects affect page speed?
Each redirect adds 50–100ms of latency as the browser must make an additional HTTP request to the new URL, wait for the DNS lookup, TCP connection, and server response. Multiple redirects compound this delay. Google's PageSpeed Insights flags redirect chains as a performance issue. Minimizing redirects is a Core Web Vitals best practice, especially for Largest Contentful Paint (LCP).
How do I implement redirects in .htaccess?
For Apache servers, add redirect rules to your .htaccess file using mod_rewrite. A basic 301 redirect looks like: RewriteRule ^old-page$ /new-page [R=301,L]. For Nginx, use the return directive: return 301 /new-page;. For Next.js, configure redirects in next.config.js using the redirects() function. Always test redirect rules in a staging environment before deploying to production.
Should I redirect HTTP to HTTPS?
Absolutely. Redirecting all HTTP traffic to HTTPS with a 301 redirect is essential for security, SEO, and user trust. Google uses HTTPS as a ranking signal, and browsers display "Not Secure" warnings on HTTP pages. Implement the redirect at the server level (not per-page) to ensure every URL on your site forces HTTPS. Don't forget to update canonical tags and sitemaps to use HTTPS URLs.
What happens to backlinks when I redirect a page?
When you 301 redirect a page, the backlinks pointing to the old URL pass their link equity to the new destination. Search engines update their records to associate the link value with the new URL. However, it's still best practice to update backlinks to point directly to the new URL when possible (via outreach to linking sites) to avoid depending on redirects for link equity transfer.
How do I handle redirects during a site migration?
Map every old URL to its corresponding new URL and implement 301 redirects for each. Prioritize pages with the most backlinks and traffic. Monitor 404 errors in Google Search Console after migration and add redirects for any missed URLs. Keep redirects active for at least one year — Google needs time to recrawl and update its index. Test the entire redirect map before going live.
What is a meta refresh redirect?
A meta refresh redirect uses an HTML <meta http-equiv="refresh" content="0;url=destination"> tag to redirect users after a specified delay. Meta refresh redirects are not recommended for SEO because they are slower than server-side redirects, may not pass full link equity, and create a poor user experience. Always use server-side 301 or 302 redirects instead of meta refresh.
How do I check if my redirects are working correctly?
Use our free Redirect Checker to trace the full redirect chain from any URL, see each hop's HTTP status code, and identify the final destination. You can also check redirects using browser developer tools (Network tab), command-line tools like cURL (curl -I -L url), or Google Search Console's URL Inspection tool. Regular redirect audits should be part of your technical SEO routine.
Stop Losing Traffic to Broken Redirects
Redirect chains, loops, and misconfigured status codes silently drain link equity and waste crawl budget. Use our free Redirect Checker above to trace every hop, or explore our full toolkit for comprehensive technical SEO auditing.