Why redirect chains matter for SEO
A redirect chain happens when a URL redirects through two or more intermediate steps before reaching its final destination, instead of redirecting directly. Google has confirmed that Googlebot stops following a chain after 5 hops — beyond that, the page may not get crawled or indexed at all.
Even short chains cause real problems:
- Crawl budget waste — every extra hop is a wasted request that could have gone toward crawling new content.
- Slower page loads — each redirect adds round-trip time before the page starts rendering, which hurts Core Web Vitals.
- Link equity loss — SEO value can leak at each hop, especially across mixed redirect types.
- Broken user experience — chains through HTTP pages or unexpected domains can trigger browser security warnings.
The fix is always the same: flatten the chain so the original URL redirects directly to the final destination in a single hop.
301 vs 302 vs 307 vs 308: what's the difference
| Code | Name | Permanent? | Passes SEO value | Use case |
|---|---|---|---|---|
| 301 | Moved Permanently | Yes | Yes | Page or site has moved for good |
| 302 | Found | No | Partial | Temporary swap — A/B tests, maintenance pages |
| 307 | Temporary Redirect | No | Partial | Like 302, but preserves the HTTP method (POST stays POST) |
| 308 | Permanent Redirect | Yes | Yes | Like 301, but preserves the HTTP method — common for API endpoints |
How to use the Redirect Chain Checker
- Paste your URL, or up to 50 URLs (one per line), into the input box above.
- Click Check Redirects.
- Each URL appears as a result row with its final status code and response time.
- Click any row to expand the full chain — every hop, its status code, and its response headers.
- Review the canonical tag, meta description, H1, and language shown for the final destination page.
What each result field means
- Status code
- The HTTP response code at each hop (200, 301, 302, 404, etc.)
- Response time
- How long that hop took to resolve, useful for spotting slow intermediate redirects.
- Headers
- The raw HTTP response headers returned at each step, including things like Location, Cache-Control, and security headers.
- Canonical tag
- The canonical URL declared on the final page, to confirm it points where you expect.
- Meta description
- Pulled from the final destination, so you can spot missing or duplicate descriptions.
- H1
- The page's primary heading, useful for confirming the right page loaded.
- Lang
- The declared language of the final page, handy for hreflang and international SEO checks.
Frequently asked questions
What is a redirect chain?
A redirect chain is when a URL redirects through two or more intermediate URLs before reaching its final destination, rather than redirecting directly in one step.
How many redirects is too many?
Google generally stops following a chain after 5 hops. As a best practice, aim for zero unnecessary hops — every redirect should go directly from the old URL to the current final URL.
Does a redirect chain hurt SEO?
Yes. Chains slow down page loads, waste crawl budget, and can dilute link equity, all of which are factors search engines weigh when ranking pages.
Can I check multiple URLs at once?
Yes — paste up to 50 URLs, one per line, and the tool checks all of them in a single run.
Is this tool free?
Yes, the Redirect Chain Checker is free to use with no signup required.
What's the difference between a redirect checker and a bulk redirect checker?
A standard checker is built for testing one URL at a time — useful for quick troubleshooting. A bulk checker, like this one, is built for scale: reviewing dozens of URLs at once to spot patterns and structural issues across a whole site or migration.