Redirect Checker

Trace a URL’s full redirect chain hop by hop. See every 301, 302, 307, and 308 along the way, the final destination, and flags for long chains, loops, and insecure HTTP hops.

100% free
No signup
Runs in your browser

Guide

What a redirect checker does

When a URL forwards to another address, that is a redirect. This tool traces the entire chain hop by hop, showing every redirect (301, 302, 307, 308) between the URL you enter and its final destination, and flags problems like long chains, loops, and insecure HTTP hops along the way.

301 vs. 302 redirects

The status code matters for SEO. A 301 is a permanent redirect: it tells search engines the page has moved for good and passes its ranking signals to the new URL, so it is what you use when you change a URL permanently. A 302 (and 307) is temporary, signalling the move is short-term, so the original URL keeps its ranking. Using a 302 where you meant a 301 is a common SEO mistake.

Why redirect chains and loops hurt

Every redirect adds a round trip, so a chain (A to B to C to D) slows the page for users and wastes crawl budget for search engines, and a little ranking signal can leak at each hop. A loop (A to B back to A) never resolves, so the page simply fails to load. Both are worth fixing by pointing the original URL directly at the final destination in a single hop.

How many redirects is too many?

Ideally zero or one. A single redirect is normal and fine; beyond two or three, you are in chain territory that browsers and crawlers treat as a warning sign, and many give up after about five. Also make sure any HTTP version of your page redirects straight to HTTPS, so visitors are not bounced through an insecure hop on the way.

Last updated: July 2026

Frequently Asked Questions

What’s the difference between a 301 and 302 redirect?

A 301 is a permanent redirect: search engines transfer ranking signals to the new URL and update their index. A 302 is temporary: the original URL is kept in the index. Use 301 for permanent moves and 302 only for genuinely temporary ones.

Why are too many redirects bad for SEO?

Each redirect adds latency and can dilute link equity. Long chains slow page loads, waste crawl budget, and risk errors. Keeping redirects to a single hop preserves speed and ranking signals.

What is a redirect loop?

A redirect loop happens when URLs redirect to each other in a cycle (A → B → A), so the destination is never reached. Browsers eventually show a "too many redirects" error. This tool detects loops and stops safely.

How do I fix a redirect chain?

Update each source to point directly at the final destination in one hop. For example, change A → B → C into A → C and B → C, so no request passes through more than one redirect.

Does HTTPS to HTTP count as a redirect issue?

Yes. Redirecting from HTTPS down to HTTP (or routing through an HTTP hop) exposes the request to interception and is flagged as a security/SEO issue. Every hop should stay on HTTPS.

How many redirects is too many?

Aim for zero or one. Google can follow several hops, but more than three meaningfully hurts performance and crawl efficiency. This tool flags any chain longer than three hops.