stillindexedStart monitoringOpen the app

Redirect chain checker

Follow the first request through every redirect to the final response. See the status, URL, hostname, and scheme at each position.

Public check, no account needed. Records every response from the requested URL through the final destination. Rate limited to 60 an hour per IP.

Worked example

Illustrative result for a reserved example URL. Your check replaces it.

3 redirects before the final URL

Flatten this chain to two redirects or fewer.

Redirect hops
3
Responses in chain
4
Ends in HTTP 200
Yes
Crosses domains or subdomains
Yes
Crosses schemes
Yes
More than two redirects
Yes
Final URL
https://www.example.com/guides/technical-seo
  1. Request 1HTTP 301http://example.com/old-guide
  2. Request 2HTTP 302https://example.com/old-guide
  3. Request 3HTTP 301https://www.example.com/old-guide
  4. FinalHTTP 200https://www.example.com/guides/technical-seo

What this check means

HTTP redirect
An HTTP redirect is a 3xx response that sends a client from the requested URL to another URL.
Redirect chain
A redirect chain is the complete sequence of redirect responses between the first requested URL and the final response.
Redirect hop
A redirect hop is one 3xx response and its move to the next URL in the chain.

How to read the result

Redirect hops
This counts only 3xx responses. More than two is marked for review because the path can usually be shortened.
Responses in chain
This includes every redirect response plus the final response, so it is normally one higher than the hop count.
Ends in HTTP 200
No means the chain ended on another status. A final error or another redirect leaves the destination unresolved.
Crosses domains or subdomains
Yes means consecutive URLs use different hostnames. Confirm that the handoff is expected and maintained.
Crosses schemes
Yes usually records an HTTP to HTTPS move. An HTTPS to HTTP move deserves immediate review.
More than two redirects
Yes marks the chain for flattening. Update the first redirect and upstream links to point directly at the final URL.
Response list
Each line contains the observed position, status, and URL. Fix the earliest unnecessary hop so every upstream link reaches the final destination directly.

Common causes

  • HTTP redirects to HTTPS, then a second rule adds or removes the www hostname.
  • An old migration rule points to another URL that was later migrated again.
  • A CMS changes the slug while legacy redirect rules remain chained.
  • Locale, device, authentication, or trailing-slash middleware redirects in separate steps.
  • The final destination was deleted or moved without updating the earlier redirect.

How many redirects are too many?

This checker flags more than two redirect hops for review. One direct redirect is clearer, and chains longer than a couple of hops are usually worth flattening.

Why is a redirect chain bad for crawling?

Every hop requires another request before the crawler reaches the final content. Extra requests use crawl resources, delay the final response, and create more places for a chain to break.

What if the chain does not end in HTTP 200?

The destination did not return a normal successful page response. Review a final 3xx, 4xx, or 5xx before treating the redirect as complete.

Do HTTP to HTTPS and hostname changes count as redirects?

Yes when the server returns a redirect response for the change. The result reports scheme and hostname crossings separately so an unexpected boundary is easy to spot.