# Redirect Checker > Trace every redirect hop for any URL: status codes, Location headers and timing. Spot loops, long chains, 302s that should be 301s and meta refreshes. Use it free at https://swipetolaunch.com/tools/redirect-checker ## How to use it 1. **Paste a URL.** Start with http:// to test the HTTPS upgrade, or paste an old URL you moved. 2. **Trace the chain.** We request each hop ourselves, without following automatically, so you see every status code and Location header. 3. **Fix what is flagged.** Loops, chains longer than one hop, temporary redirects on permanent moves and meta refreshes are called out with what to change. ## Why redirects matter for SEO A redirect tells browsers and crawlers that a URL has moved. Done right, it carries the old page's links and rankings to the new one. Done wrong, it leaks link value, wastes crawl budget and slows down every visit. ## What to look for - **One hop, not several.** `http://example.com` to `https://example.com` to `https://www.example.com` to `/home` is three round trips before the page even starts loading. Point every old variant straight at the final URL. - **301 or 308 for permanent moves.** A 302 or 307 says the move is temporary, so search engines may keep the old URL in the index. Use them only when the old URL really is coming back. - **No loops.** A loop (A to B to A) is a dead end. Browsers show an error and crawlers drop the URL. - **HTTP always upgrades to HTTPS.** Every `http://` URL should 301 to its `https://` twin in a single hop. - **No meta refresh.** A `` tag is a client-side redirect. Google can follow it, but it is slower and less clear than a server redirect. - **The chain ends on a 200.** A redirect that lands on a 404 throws away everything the old URL had earned. ## Common causes of long chains Chains usually build up over years: a domain change, then an HTTPS migration, then a URL restructure, each adding a rule on top of the last. Audit old rules after each migration and collapse them so every legacy URL goes straight to its current home. Moving pages? Write the rules with the [redirect generator](/tools/redirect-generator), then confirm each old URL here. To check the headers on the final page, use the [HTTP header checker](/tools/http-header-checker). ## What you get - Every hop with status and Location - Per-hop and total timing - Loop and long-chain detection - 302 vs 301 and HTTP to HTTPS checks - Meta refresh detection on the final page ## Questions ### What is the difference between a 301 and a 302 redirect? A 301 means the page has moved permanently, so search engines index the new URL and pass ranking signals to it. A 302 means the move is temporary, so the old URL may stay in the index. Use 301 (or 308) for anything permanent. ### How many redirects is too many? Aim for one. Google follows up to 10 hops, but each one adds a round trip for visitors and makes it more likely a crawler gives up. Two or more in a row is worth fixing. ### Do redirects lose link value? Google says 301, 302 and 308 redirects all pass PageRank. The real losses come from chains, loops and redirects that land on irrelevant or broken pages. ### What is a redirect loop? A loop happens when URL A redirects to B and B redirects back to A, or through a longer cycle. The page never loads. It is usually caused by two conflicting rules, such as one forcing www and another removing it. ### Why does my browser not show the redirects? Browsers follow redirects silently and cache 301s. This tool requests each hop fresh from our servers, so you see the whole chain as a crawler would.