Log in Sign up free

Redirect Checker

Trace every hop of a redirect chain with status codes and timing.

What does a redirect checker do?

A redirect checker follows a URL the way a browser or Googlebot does and lists every hop with its HTTP status code — 301, 302, 307 or 308 — until it reaches the final page. It shows whether a redirect is permanent or temporary and how long the chain is.

Why redirects matter for SEO

Every time a URL changes — a new domain, HTTPS migration, renamed page or removed product — a redirect tells browsers and search engines where the content went. The type of redirect decides whether ranking signals move with it, and the number of redirects decides how fast users and crawlers arrive. Misconfigured redirects are one of the most common reasons sites lose traffic after a redesign.

301 vs 302 vs 307 vs 308

CodeMeaningWhen to useSEO effect
301Moved PermanentlyPage or domain moved for goodSignals consolidate on the new URL; old URL drops from the index
308Permanent RedirectSame as 301 but keeps the HTTP method (POST stays POST)Treated like a 301
302Found (temporary)A/B tests, short-term promotions, geo or login redirectsGoogle may keep the old URL indexed
307Temporary RedirectTemporary, method-preserving; also used internally by browsers for HSTSTreated like a 302

The practical rule: if the move is permanent, use a 301 (or 308). A 302 left in place for months makes Google guess, and it may index the wrong URL.

Redirect chains and loops

A redirect chain happens when URL A redirects to B, which redirects to C. Common example: http://example.com → https://example.com → https://www.example.com → https://www.example.com/. Each hop adds latency (often 100–300 ms on mobile) and Googlebot stops following after about 10 hops. A redirect loop (A → B → A) makes the page unreachable. This checker follows up to 10 hops and flags both problems.

How to fix the issues this tool finds

  1. Chain of 2+ hops: update the first rule so it points straight to the final URL, and update internal links to the final URL too.
  2. 302 on a permanent move: change the server rule to 301. In Apache use Redirect 301 /old /new or [R=301,L]; generate rules with the Htaccess Redirect Generator.
  3. Redirect to a 404: point the rule at the closest relevant live page instead.
  4. HTTP and www inconsistencies: combine the HTTPS and www rules into one rule so there is a single hop.

Example

1. http://github.com        301 Moved Permanently
2. https://github.com/      200 OK

One permanent hop to the HTTPS version — that is the ideal setup. Check the final page's headers with the HTTP Headers Checker or test many URLs at once with the HTTP Status Code Checker.

Frequently asked questions

How do I know if a redirect is 301 or 302?

Paste the URL into the redirect checker. Each hop shows its status code: 301 and 308 are permanent redirects, 302 and 307 are temporary.

How many redirects are too many?

Aim for one hop at most. Two or more redirects in a row form a chain that slows users down, and Googlebot gives up after about 10 hops.

Does a 301 redirect lose PageRank?

Google has said 301, 302 and 308 redirects pass ranking signals. Problems come from long chains, temporary redirects left in place, and redirects to irrelevant pages.

Why does my HTTP URL redirect with 307?

Browsers use an internal 307 when a site uses HSTS. The real server redirect may still be a 301 — this checker requests the URL directly, so it shows what your server actually returns.

Can I check redirects for many URLs at once?

Yes. Use the HTTP Status Code Checker to test up to 20 URLs in one go and see which ones redirect and where to.