Redirect Checker

Check whether a URL redirects, follow each HTTP hop, and identify the final destination, status codes, loops, and HTTP-to-HTTPS changes.

Parallel checks
Up to 50
Redirect depth
Up to 20 hops
Loop detection
Built-in
Supports comma or newline separated URLs.
Keep below 50 to avoid rate-limits on target sites.
The checker requests each URL, follows redirect locations manually, stops at repeated URLs, and caps the chain at your selected depth.

How to check a redirect

  1. Enter a complete HTTP or HTTPS URL. Add more URLs on separate lines if needed.
  2. Choose the maximum redirect depth and number of parallel checks.
  3. Select Check URLs, then review the final status and destination.
  4. Open View chain to inspect every hop, redirect type, target, timing, and protocol change.

How to interpret the results

301
Permanent redirect. Use it when a URL has a lasting replacement.
302
Temporary redirect. The original URL is expected to return.
307
Temporary redirect that preserves the request method.
308
Permanent redirect that preserves the request method.
200
The requested resource responded successfully and is normally the end of the chain.
4xx / 5xx
A client or server error stopped the check; inspect the code and last URL reached.

Example redirect chain

http://example.com
↓ 301 Permanent redirect (HTTP → HTTPS)
https://example.com
↓ 200 Successful destination

This fictional example shows one permanent protocol redirect followed by a successful final response. It is an illustration, not a live measurement.

Redirect chains, loops, and SEO checks

Keep chains short

Each unnecessary hop adds another request, slows navigation, and makes redirect rules harder to debug. Update internal links so they normally point directly to the final URL rather than an older URL in the chain, and use the Internal Linking Assistant to review relevant source-to-destination opportunities.

Fix redirect loops

A loop sends a request back to a URL already visited, such as A → B → A. Browsers and crawlers cannot reach a final page. The checker stops when it sees a repeated URL and shows the responses collected before the loop was detected.

Check migration signals together

For a URL with a true permanent replacement, use an appropriate permanent redirect. After a migration, verify that internal links and canonical URLs point to the intended final destination and avoid mixing unnecessary temporary and permanent hops. A redirect alone does not guarantee indexing or rankings.

Common questions

What does the final URL mean?

It is the URL that returned the last non-redirect response. If the check stops because of a loop, invalid location, timeout, or depth limit, the page labels the value as the last URL reached instead.

Does the checker detect HTTP and HTTPS redirects?

Yes. When a redirect changes the protocol, the hop is marked HTTP → HTTPS or HTTPS → HTTP.

Why can a browser and this checker show different results?

Redirects can vary by request method, cookies, location, user agent, or authentication. This checker sends a server-side HTTP request and does not reproduce a signed-in browser session.

Related technical SEO tools