How to capture redirect headers
Terminal (curl):
curl -ILv https://example.com 2>&1 | grep -E "HTTP/|location:"
Browser DevTools: Open Network tab → reload page → click first request → Headers tab. Copy the Status and Location for each row in the chain.
The tool parses three common formats: full curl -ILv output, the simplified HTTP/x.x STATUS + location: pairs, and raw status/URL pairs separated by arrows or newlines.
Frequently asked questions
How many redirects are too many?
Google recommends no more than 5 hops in a chain, but ideally a single 301. Each additional hop slows page load, dilutes link equity slightly, and risks Googlebot abandoning the crawl.
Do 302 redirects pass link equity?
302 (Found) is officially a temporary redirect. Google has stated it eventually treats long-standing 302s like 301s, but the transfer is slower and less reliable. Use 301 for permanent moves.
What is a redirect loop?
A redirect loop occurs when URL A redirects to URL B which redirects back to URL A (directly or through intermediate hops). Browsers detect this and show ERR_TOO_MANY_REDIRECTS; search engines drop the URL from the index.
Is meta refresh redirect bad for SEO?
Meta refresh with delay=0 is treated similarly to a 301 by Google, but server-level 301 is always preferred. Delays greater than 0 are interpreted as user-initiated and may not pass equity at all.
How do I get the input for this tool?
Run 'curl -ILv https://example.com' in your terminal, or use browser DevTools Network tab and right-click → Copy as cURL. Paste the response headers directly into the input below.