AIO Copilot

Redirect Chain Checker

Enter each hop of a redirect path and see the chain counted, with loops, HTTPS downgrades, host changes and 302s flagged. It fetches nothing: trace the real chain first with curl or your browser.

Enter URLs in Redirect Order
Hop 1
Type:|
Final

How to check a redirect chain

Trace the chain, enter each hop, then point everything at the final URL.

  1. Trace the real chain

    Run curl -IL with the starting URL, or load it with your browser's developer tools open on the Network tab. Note each status code and the Location it points to.

  2. Enter each URL in order

    Put the starting URL first and the page that finally loads last, adding a field for each hop. Under each URL, choose the redirect that sends it onward: 301, 302, 307, 308 or meta refresh.

  3. Analyze the chain

    The checker counts hops, flags loops, HTTPS to HTTP downgrades and changes of host, and warns on 302 and meta refresh hops. It runs in your browser and fetches nothing.

  4. Collapse it to one hop

    Point the first URL, and every URL in the middle, straight at the final destination. Then update internal links, canonical tags and the sitemap to use the final URL.

What is a redirect chain?

A redirect chain is a path in which a URL redirects to a second URL that redirects again before any page loads, such as http://example.com/old to https://example.com/old to https://www.example.com/new. Googlebot "generally follows 10 redirect hops", but Google's site move guide advises redirecting "to the final destination directly" and, where that is impossible, keeping chains to "ideally no more than 3 and fewer than 5." Its reason is plain: "Chaining redirects adds latency for users, and not all user agents and browsers support long redirect chains."

A loop is the failure case: the path returns to a URL it already visited, so no page ever loads. The Page indexing report in Search Console lists "A redirect loop" and "A redirect chain that was too long" among its redirect errors, which it files under pages that are not indexed (see our glossary entry on indexing).

How do redirect chains affect SEO?

Mostly through crawling and speed. Google's crawl budget guide says to "avoid long redirect chains, which have a negative effect on crawling", but that guide is written for sites with a million or more pages, or 10,000 or more that change daily, and tells smaller sites they "don't need to read this guide." For most sites the cost is the extra round trip each visitor makes on every hop, and the drift a chain reveals: internal links, canonical tags and sitemap entries still pointing at addresses that moved years ago. Google's site move guide asks for all three to be updated to the new URLs.

Which redirect should I use: 301, 302, 307 or 308?

Use a 301 or 308 for a permanent move and a 302 or 307 only for a temporary one. Google's status code documentation treats the permanent pair as a strong signal for the target URL and the temporary pair as a weak one, and its redirects guide explains how it reads meta refresh. The difference within each pair is about the request method, which matters for forms and APIs rather than search; MDN's page on the 307 status explains that a 307 guarantees the browser "will not change the request method and body".

Redirect types and how Google treats them
RedirectWhat it meansHow Google treats it
301 Moved PermanentlyPermanentStrong signal that the target is canonical
308 Permanent RedirectPermanent, keeps the request methodSame as 301
302 FoundTemporaryWeak signal
307 Temporary RedirectTemporary, keeps the method and bodySame as 302
Meta refresh, 0 secondsInstant, set in the HTMLPermanent
Meta refresh, delayedFires after a set number of secondsTemporary

Google recommends "a permanent server-side redirect whenever possible", and JavaScript redirects only if you cannot do a server-side or meta refresh redirect, because rendering can fail and the redirect may never be seen. A 302 left in place for a permanent move is the common slip. For a temporary redirect, the redirects guide says, Google's indexing pipeline "doesn't use the redirect as a signal that the redirect target should be canonical", so the old URL can stay in results. The checker offers 308 as a hop type and treats it as permanent, like a 301.

How do I fix a redirect chain?

Point every old URL straight at the final destination. Export the rules wherever they live (the server configuration, a CMS redirect plugin, the CDN), find each source's final URL, and rewrite the first rule to go there in one hop. Rewrite the middle rules the same way, because old links may point at any URL in the chain. Then update internal links, canonical tags and the sitemap so nothing on the site sends visitors through a redirect at all, and keep the redirects for, in Google's words, "generally at least 1 year".

Loops need one rule removed rather than rewritten. The pairs to look for first are a trailing slash rule fighting its opposite, or a www rule fighting a bare-domain rule set somewhere else. Google treats /page and /page/ as separate URLs (the bare hostname aside), so pick one form, redirect the other to it, and delete whichever rule contradicts that choice. The redirects section of our technical SEO audit checklist explains how to check old URLs in bulk with a crawler in list mode, and the canonical tag checker confirms a page's canonical names the final URL.

What this checker can and cannot do

It analyzes a chain you type in; it does not request any URL. To trace a live chain, run curl with -I, which in curl's manual fetches "the headers only", and -L, which follows each Location; curl stops after 50 redirects by default. Search Console's URL Inspection live test follows redirects too, but it tests the final page without showing the hops.

The loop check compares URLs exactly, the way a server sees them: the scheme and host ignore letter case, but the path does not, and a trailing slash counts. So a one-way normalization such as /Page to /page or /page to /page/ is an ordinary hop; only a return to a URL already in the chain is reported as a loop. The hop thresholds sit inside Google's advice: one or two hops get an information note, three a warning, and four or more an error.

Redirect chain questions.

Hop limits, 301 versus 302, meta refresh, loops and how long to keep redirects.

How many redirects will Googlebot follow?

Googlebot generally follows 10 redirect hops when crawling web content, according to Google's documentation on HTTP status codes. Google's site move guide still advises redirecting straight to the final URL, or keeping a chain to ideally no more than 3 hops and fewer than 5. For a robots.txt file, Google follows at least five hops and then treats the file as missing.

What is the difference between a 301 and a 302 redirect?

A 301 says a move is permanent and a 302 says it is temporary. Google treats a 301 (and a 308) as a strong signal that the target should become the canonical URL, and a 302 (and a 307) as a weak one. Use a 301 when you are sure the move will not be reversed.

Is a meta refresh redirect bad for SEO?

Not necessarily. Google treats an instant meta refresh, set to 0 seconds, as a permanent redirect and a delayed one as temporary. It still recommends a permanent server-side redirect whenever possible, and JavaScript redirects only when neither a server-side nor a meta refresh redirect is available.

What causes a redirect loop?

Two rules that send URLs to each other, such as one adding a trailing slash while another strips it, or a server forcing www while a CDN forces the bare domain. Browsers give up with a too-many-redirects error, and Search Console lists "A redirect loop" among the redirect errors in its Page indexing report. Pick one form of the URL and delete the rule that fights it.

How long should I keep old redirects in place?

Google's site move guide says to keep redirects for as long as possible, and generally at least one year, so Google has time to transfer signals to the new URLs. Links on other sites keep sending visitors to old addresses long after that, so there is little reason to remove a redirect that still gets traffic.

Should HTTP redirect to HTTPS in a single hop?

Yes. Send each HTTP URL straight to its final HTTPS address, host and path included, rather than through a separate www or trailing slash hop. Google lists HTTPS among the signals it uses to choose a canonical, and an HSTS header then tells returning browsers to upgrade to HTTPS themselves, skipping the HTTP request.

Redirects rarely break alone.

A chain often comes with stale internal links, sitemaps that list redirected URLs, and canonicals that point at old addresses. Our technical SEO audit checklist covers each of them, in the order problems block rankings.

Read the checklist

What to do next.