Skip to content

Redirect Checker

Understand HTTP redirect codes (301, 302, 307, 308), get a curl command for any URL, and paste curl output to visualize the complete redirect chain.

FreeNo SignupNo Server UploadsZero Tracking

Check Redirect Chain

Run this in your terminal
curl -I -L -s "https://example.com"

The -I flag fetches only headers. -L follows redirects. -s hides progress.

HTTP Redirect Codes

301Moved PermanentlyPermanent

The resource has permanently moved to a new URL. Search engines will transfer SEO value (link equity) to the new URL. This is the most common redirect for SEO.

302Found (Temporary)Temporary

The resource is temporarily at a different URL. Search engines keep the original URL indexed. Use when the move is truly temporary (e.g., A/B tests, maintenance).

307Temporary RedirectTemporary

Similar to 302 but guarantees the request method (GET, POST) won't change. Preferred over 302 in HTTP/1.1 for temporary redirects that must preserve the request method.

308Permanent RedirectPermanent

Similar to 301 but guarantees the request method won't change. The HTTP/1.1 version of 301. Use when permanently redirecting POST requests.

SEO Tips

  • -- Use 301 for permanent URL changes to pass link equity.
  • -- Avoid redirect chains (multiple hops) as they slow down crawling and dilute link equity.
  • -- Keep chains to 3 hops or fewer when possible.
  • -- Always redirect HTTP to HTTPS with a 301.

How to Use Redirect Checker

  1. 1

    Enter a URL

    Type or paste the URL you want to check for redirects.

  2. 2

    Copy the curl command

    Copy the generated curl command and run it in your terminal. The command follows all redirects and shows headers only.

  3. 3

    Paste curl output

    Copy the terminal output and paste it into the text area. The tool will parse the HTTP headers automatically.

  4. 4

    View the redirect chain

    Click Parse Redirect Chain to see a visual representation of each hop with status codes and destination URLs.

Frequently Asked Questions

Due to browser security restrictions (CORS), client-side JavaScript cannot follow HTTP redirects for arbitrary URLs. Using curl in your terminal bypasses this limitation and gives you the full redirect chain.

A redirect chain is a series of HTTP redirects between the original URL and the final destination. For example: Page A (301) -> Page B (302) -> Page C (200). Chains with more than 3 hops can cause SEO issues.

A 301 is a permanent redirect that tells search engines to transfer link equity to the new URL. A 302 is a temporary redirect where search engines keep the original URL indexed. Use 301 for permanent URL changes.

Google recommends avoiding redirect chains when possible. While Googlebot follows up to 10 redirects, each hop adds latency and may dilute link equity. Keep chains to 3 hops or fewer.

No. All parsing and visualization happens entirely in your browser. The curl command runs locally on your machine.