Question 1

Can this tool check live redirects on a URL?

Accepted Answer

No — and we're upfront about it. Live HTTP redirect checking requires network access, and most websites block cross-origin requests from the browser (CORS). This tool instead provides: (1) a complete redirect type reference, (2) a chain analyzer where you enter the hops manually (from browser DevTools or curl), and (3) stats and warnings. Use DevTools (Network tab → Preserve log) or `curl -I <URL>` to capture the redirect chain, then paste it here.

Question 2

How do I check redirects with curl?

Accepted Answer

Run `curl -I -L https://example.com` in a terminal. The -I flag fetches headers only, -L follows redirects. You'll see each 3xx response with its Location header. Or use `curl -sIL -o /dev/null -w '%{url_effective}' https://example.com` to print just the final URL.

Question 3

How do I check redirects with browser DevTools?

Accepted Answer

Open DevTools (F12), go to the Network tab, check 'Preserve log', then navigate to the URL. Each 3xx response will appear in the network list with its status code and Location header. Right-click the column header → add 'Status' if not visible.

Question 4

What is the difference between 301, 302, 307, and 308?

Accepted Answer

301 = Moved Permanently (passes link equity, may downgrade POST to GET). 302 = Found (temporary, doesn't reliably pass equity, may downgrade POST). 307 = Temporary Redirect (HTTP/1.1, preserves method). 308 = Permanent Redirect (HTTP/1.1, preserves method). For SEO permanent URL changes, use 301 (or 308 if you need method preservation).

Question 5

Why are long redirect chains bad?

Accepted Answer

Each hop adds latency (extra round-trip), wastes crawl budget, and may dilute link equity slightly. Google has stated they follow up to ~5 hops in a chain; beyond that, they may stop. Best practice: redirect old URL → final URL in a single hop, not A → B → C → D.

Question 6

What extra features does this tool have compared to others?

Accepted Answer

(1) URL input + parser. (2) Complete redirect type reference (7 types with SEO impact notes). (3) Manual chain builder — add/remove/reorder hops. (4) Bulk paste (from | type | to per line). (5) Chain visualization with arrows. (6) Hop count + final destination. (7) Warnings for long chains (>5 hops), 302s, meta refresh, and JS redirects. (8) Loop detection. (9) Markdown report export. (10) History (localStorage, last 20) + shareable URL.

Question 7

Is my data sent anywhere?

Accepted Answer

No. All parsing and analysis runs locally. We never make HTTP requests. History is stored in localStorage on this device only.

Redirect Chain Checker

Redirect chain (0 hops)

Redirect type reference

How to use

Redirect chain (0 hops)

Redirect type reference