Redirect Chain Checker

Why We Built This Redirect Checker

After 11+ years working in technical SEO—from enterprise e-commerce migrations with 50k+ URLs to independent blog restructures—one problem kept recurring across every engagement: misconfigured redirects causing ranking drops and wasted crawl budget.

Developers would configure redirects in .htaccess or Nginx without validating the full chain. SEO analysts would discover infinite loops or excessive chains only after sudden traffic drops. Content managers would migrate domains without auditing whether all old links properly redirected to new destinations.

We tested dozens of existing solutions and found two problematic extremes: checkers that only show the final destination (without detailing each hop) or expensive enterprise suites requiring registration and limiting verifications. What was missing: a tool that's fast, transparent, and shows the complete redirect chain—with technical details that actually matter for SEO.

That's why we built the RankBox Redirect Checker. The approach is different: you see everything. Each HTTP hop (301, 302, 307, 308), response time per redirect, returned headers, and alerts for critical issues like loops or excessive chains. All processed with intelligent server-side caching and SSRF mitigation for security.

Whether you're a developer validating redirect rules post-deploy, an SEO specialist auditing a domain migration, or a content manager fixing broken links: this tool transforms a technical process into a simple seconds-long validation.

Unlike our 100% client-side tools, the Redirect Checker requires server-side processing to perform external HTTP requests. However, we've implemented robust security layers:

Applied mitigations:

1. Strict URL validation: Only http/https schemes accepted; private IPs and internal ranges blocked to prevent SSRF. 2. Rigorous timeouts: Each request has a 10-second limit to prevent hangs. 3. Intelligent APCu caching: Results cached for 1 hour to reduce server load and accelerate repeated checks. 4. Rate limiting: Maximum 50 URLs per session to prevent abuse. 5. Zero persistent storage: Verified URLs are not logged or stored in databases.

• GDPR & CCPA compliant: No URLs or personal data stored permanently.
• Enterprise security: Companies can verify redirects for internal sites without exposing infrastructure.
• Performance: Caching reduces response time for recurring checks.
• Transparency: You see exactly what the server returned—no filters or simplifications.

The interface is designed for speed, but following a structured workflow ensures complete, actionable analysis.

Step 1: Enter URL for Verification

• Single URL check: Paste a complete URL (with https://) in the main field
• Bulk verification: Use the "Bulk" tab to paste up to 50 URLs, one per line

Correct format:

https://yoursite.com/old-page https://yoursite.com/discontinued-product

Pro tip: Always use absolute URLs with protocol. Relative URLs or those without https:// may generate inconsistent results.

Step 2: Analyze the Redirect Chain

After clicking "Check", the tool displays:

• ✅ 301 + final 200: Correct permanent redirect
• ⚠️302 instead of 301: May not fully transfer link equity
• ❌ Loop detected: URL A → B → A (critical error)
• ❌ Chain >3 hops: Excessive latency, risk Google won't follow

Step 3: Identify Common Issues

The tool automatically flags:

🔄 Redirect loops Occurs when URL A redirects to B and B redirects back to A. Causes "ERR_TOO_MANY_REDIRECTS". Solution: Review .htaccess or Nginx rules to break the circular reference.

⚡ Long chains Each hop adds 50-200ms latency. Chains with >3 hops may cause Google to stop following, losing authority. Solution: Redirect directly from old URL to final destination in a single hop.

⚠️ Incorrect status code Using 302 when you want 301 for migrations is a common error. Google may not transfer ranking properly. Solution: Replace 302 with 301 for permanent changes.

🔗 Broken links (404) URLs returning 404 lose all link value and harm user experience. Solution: Configure 301 redirect to the most relevant equivalent page.

Step 4: Generate Correction Rules (Optional)

• .htaccess (Apache)
• Nginx (server configuration)
• PHP (programmatic redirect)
• Cloudflare (Page Rules)

Step 5: Bulk Validate for Migrations

For domain migrations or site restructuring: 1. Export old URLs from your CMS or crawl tool 2. Paste in "Bulk" tab (up to 50 at a time) 3. Verify all simultaneously 4. Filter results with errors and fix in batch

Professional workflow: Validate pre-deploy → Fix issues → Re-verify → Deploy to production.

To maximize the tool's value, it's essential to understand how redirects work and their SEO impact.

HTTP Status Codes: Which to Use & When

• Use 301 for 95% of migration or restructuring cases
• Use 302 only for defined-duration tests (<7 days)
• Avoid 307/308 unless working with APIs requiring method preservation
• Never leave important URLs returning 404—always redirect to relevant content

Why Redirects Impact SEO

Misconfigured redirects affect three fundamental pillars:

1. Authority transfer (link equity) Proper 301 redirects transfer most backlink value to the new URL. Long chains or incorrect status codes (302) can dilute or lose this value.

2. Crawl budget Each redirect adds an HTTP request. For large sites, unnecessary chains waste Google's daily crawl limit, delaying indexation of new content.

3. User experience & Core Web Vitals Redirects add latency. A 3-hop chain can add 300-600ms to load time—direct impact on LCP (Largest Contentful Paint), a Google ranking factor.

Real Impact Data

• Fashion e-commerce: Fixing 200+ long chains reduced load time by 1.2s and recovered 18% of organic traffic lost post-migration
• News portal: Replacing 302 with 301 on 500 URLs recovered rankings for competitive keywords within 3 weeks
• Corporate site: Eliminating 15 redirect loops resolved crawl errors in Google Search Console within 48 hours

🛒 E-commerce Migrations (Shopify, BigCommerce, WooCommerce)

Challenge: Thousands of product, category, and filter URLs changing structure after platform swap or redesign.

• Export old URLs from database or crawl tool
• Bulk verify all redirect to correct destinations
• Identify long chains and fix for direct redirect
• Validate status codes (301 for permanent changes)

Real example: An e-commerce migrating from Magento to Shopify with 15,000 products. Instead of relying on automatic plugins, export old URLs, verify in RankBox, identify the 200 problematic URLs, and fix before deploy—avoiding post-migration traffic drops.

🔀 Domain or Protocol Change (HTTP→HTTPS)

Challenge: Ensuring all URLs from old domain or HTTP version properly redirect to new destination.

• Verify key URLs: homepage, product pages, blog posts
• Confirm redirect is 301 (not 302)
• Validate no loops or unnecessary chains
• Use results to audit .htaccess or Nginx rules

Recommended workflow: Pre-swap → Verify representative sample → Fix issues → Execute migration → Re-verify post-deploy.

🔧 Developers & SEO Agencies

Challenge: Validating redirect configurations across multiple projects, each with different tech stacks (Apache, Nginx, Cloudflare, serverless).

• Standardize redirect validation across all projects
• Use bulk check for quick pre-deploy audits
• Ensure GDPR/CCPA compliance (zero URL storage)
• Integrate into QA workflow: verify redirects before pushing to production

Professional workflow: Create a migration checklist including: (1) export old URLs, (2) verify in RankBox, (3) fix issues, (4) re-verify, (5) document changes.

📝 Blogs & Content Sites

Challenge: Old posts with URLs changing after category restructuring or CMS swap.

• Verify URLs of posts with significant organic traffic
• Identify broken redirects or long chains
• Fix before Google deindexes content

Tip: Focus first on posts with backlinks or traffic—these impact SEO most if they have redirect issues.

Follow these guidelines based on Google's official documentation and 11+ years of hands-on experience:

1. Always Use 301 for Permanent Changes

• ✅ 301 redirect for domain migrations
• ✅ 301 redirect for HTTP→HTTPS
• ✅ 301 redirect for URL restructuring

• ❌ Use 302 "just in case"—Google may not transfer ranking
• ❌ Keep 302 after test period—replace with 301
• ❌ Mix 301 and 302 in same migration—causes inconsistency

2. Avoid Chains with More Than 1 Hop

• ✅ Redirect directly from old URL to final destination
• ✅ Update internal links to point to final URL
• ✅ Use crawl tools to identify existing chains

• ❌ Create redirect A→B→C when it could be A→C
• ❌ Keep intermediate redirects after consolidation
• ❌ Ignore chains discovered in audits

3. Validate After Every Deploy

• ✅ Verify key URLs after .htaccess or Nginx changes
• ✅ Use bulk check to validate redirect batches
• ✅ Monitor Google Search Console for crawl errors

• ❌ Assume configuration is correct without testing
• ❌ Wait for traffic drop to discover issues
• ❌ Fix only errors reported by users

4. Document Your Redirect Rules

• ✅ Maintain a record of redirected URLs and reasons
• ✅ Include implementation date and responsible party
• ✅ Periodically review old redirects that can be removed

• ❌ Leave redirect rules "forever" without review
• ❌ Forget to remove temporary redirects after deadline
• ❌ Fail to communicate changes to content/SEO team

🔄 Breaking Redirect Loops

Symptom: "ERR_TOO_MANY_REDIRECTS" in browser or loop detected in checker.

Common causes: 1. .htaccess rule redirecting www↔non-www conflicting with server config 2. WordPress plugin configuring redirect conflicting with manual rules 3. CDN (Cloudflare) Page Rule conflicting with origin

Step-by-step solution: 1. Use checker to identify loop (e.g., A→B→A) 2. Review your .htaccess or Nginx configuration 3. Remove redundant rule or adjust condition 4. Clear server and CDN cache 5. Re-verify in RankBox to confirm fix

Example .htaccess correction:

# WRONG: Causes loop if server already has rule RewriteCond %{HTTP_HOST} ^yoursite.com [NC] RewriteRule ^(.*)$ https://www.yoursite.com/$1 [L,R=301]

# CORRECT: Check if not already on www version RewriteCond %{HTTP_HOST} ^yoursite\.com$ [NC] RewriteCond %{REQUEST_URI} !^/www/ RewriteRule ^(.*)$ https://www.yoursite.com/$1 [L,R=301]

⚡ Shortening Long Chains

Symptom: Chain with 3+ hops in checker, high latency.

Common causes: 1. Sequential migrations without updating intermediate redirects 2. SEO plugins adding redirects without removing old ones 3. Manual configuration without auditing existing rules

Step-by-step solution: 1. Use checker to map full chain (A→B→C→D) 2. Identify correct final destination (D) 3. Update rule for A to redirect directly to D 4. Remove intermediate rules (B→C, C→D) if no longer used 5. Re-verify to confirm 1-hop chain

Optimization example:

# BEFORE: 3-hop chain # A → B (301) → C (301) → D (200)

# AFTER: Direct redirect # A → D (301)

⚠️ Fixing Incorrect Status Code

Symptom: 302 redirect for permanent change, ranking loss post-migration.

Common causes: 1. Plugin default configuration using 302 2. Developer using 302 "for testing" and forgetting to change 3. Confusion between "temporary" and "permanent" in documentation

Step-by-step solution: 1. Identify URLs with 302 in checker 2. Confirm if change is truly permanent 3. Update rule to use 301 4. Re-verify to confirm change 5. Monitor Google Search Console for ranking recovery

Example Nginx correction:

# WRONG: Temporary redirect for permanent change location /old-page { return 302 https://yoursite.com/new-page; }

# CORRECT: Permanent redirect location /old-page { return 301 https://yoursite.com/new-page; }

How many redirects are acceptable in a chain?

Ideally, always a direct redirect—from old URL to final URL in a single hop. Google recommends avoiding chains with more than 3 hops, but in practice, each additional hop adds latency and risk the crawler won't follow to the end. For SEO and performance, always aim for 1-hop chains.

Why does my site show "ERR_TOO_MANY_REDIRECTS"?

This error indicates a redirect loop: URL A redirects to B and B redirects back to A (or a larger circular chain). Common causes include conflict between .htaccess rules and server configuration, WordPress plugins with duplicate redirects, or CDN (Cloudflare) configuration conflicting with origin.

Does a 301 redirect transfer 100% of PageRank?

Google has stated that 301 and 302 redirects pass link value similarly. In practice, 301 tends to transfer more consistently because it signals permanent change. Most important is avoiding long chains—each hop can dilute some value. Focus on direct redirect with 301.

How do I check redirects for a whole list of URLs?

Use the "Bulk" tab in this tool—paste up to 50 URLs, one per line, and click "Check all". The tool will process each URL and display results in a table, making it easy to identify patterns and recurring issues. For larger lists, process in batches of 50.

What's the difference between 301 and 302 redirects for SEO?

301 (Moved Permanently) signals to Google that the change is definitive, transferring authority and replacing the old URL in the index. 302 (Found/Temporary) indicates a temporary change, keeping the old URL in the index. Use 301 for migrations, domain swaps, or permanent restructuring; use 302 only for defined-duration tests (<7 days).

How do I fix a redirect loop in WordPress?

1. Temporarily deactivate redirect plugins to isolate conflict 2. Check "Site Address" settings in Settings > General 3. Review .htaccess file in WordPress root 4. If using CDN (Cloudflare), check Page Rules 5. Use the checker to test after each change until identifying the cause

Do redirects impact Core Web Vitals?

Yes. Each redirect adds an HTTP request and latency (50-200ms per hop). Long chains directly impact LCP (Largest Contentful Paint), a Google ranking factor. To optimize Core Web Vitals, minimize redirects and ensure they're direct and well-configured.

Can I use this tool to check internal redirects?

Yes. The checker works for any publicly accessible URL, including subdomains and internal paths. For staging sites or authenticated environments, ensure the URL is accessible without login so the server can perform the request.

How do I know if a redirect is cached by the browser?

Use the "Network" tab in browser DevTools (F12) and check "Disable cache". Reload the URL and observe response headers. If the redirect doesn't occur with cache disabled, it may be cached in browser or CDN. To force update, use cache-busting (?v=timestamp) or clear CDN cache.

Should I remove old redirects after some time?

Yes, but cautiously. Very old redirects (2+ years) receiving no traffic or backlinks may be candidates for removal. Before removing: (1) check traffic in Google Analytics, (2) verify backlinks in Ahrefs or Search Console, (3) if no activity, remove rule and monitor for 404s.

How do I bulk verify redirects for domain migration?

1. Export all URLs from old domain (via CMS, database, or crawl tool) 2. Paste in checker's "Bulk" tab in batches of 50 3. Filter results with errors (loops, chains >3, incorrect status) 4. Fix rules on server 5. Re-verify corrected batches before final deploy

Does the checker work for URLs with parameters or fragments?

Yes. The checker processes complete URLs, including query parameters (?utm_source=...) and fragments (#section). However, for SEO, it's generally better to redirect to the canonical URL without unnecessary parameters. Use the tool to validate if parameters are handled as expected.

Redirect validation is essential for technical SEO, but it's part of a larger optimization ecosystem. Explore other free tools we've built:

• Page Optimizer: Preview and optimize how your site appears in Google with real-time title and meta description simulation.
• Word Counter: Analyze keyword density, reading time, and text structure for your content.
• XML Sitemap Generator: Create optimized sitemaps to accelerate Google indexing of your pages.
• Image Converter: Convert images between JPG, PNG, and WebP with client-side processing—zero uploads to servers.

About RankBox: An independent project built by SEO practitioners with 11+ years of hands-on experience. Our tools are 100% free, processed securely with privacy focus. No sign-ups. No persistent storage. No complications.