PeakKR
πŸ”€

Redirect Chain Checker

Paste any URL and follow it hop by hop β€” every 301, 302 and refresh with its status code, chains counted, loops caught, verdict in plain English. Essential after migrations, and any time a page "works fine" in the browser but rankings say otherwise.

βœ“ 100% free, no signup βœ“ Follows up to 10 hops βœ“ Flags loops & chains βœ“ Real status codes, not guesses
How to use it

Trace any URL in three steps

  1. Paste the URL you want to test β€” an old page after a migration, a link from a backlink report, or any URL a client says "used to work."
  2. Read the hops. Each row is one server response: green 200 means content, amber 3xx means a redirect, red means an error. The chain reads top to bottom in the order a browser (and Googlebot) experiences it.
  3. Act on the verdict. One redirect: normal. Two or more: point links and redirect rules straight at the final URL. LOOP: the page is unreachable β€” fix it today.
The damage report

Why redirect chains quietly cost rankings

Each hop leaks a little of three budgets at once. Speed: every hop is a full network round-trip before any content loads β€” on mobile, a three-hop chain can add over a second. Crawl budget: Googlebot spends a fetch on every hop; on large sites that's fetches not spent on your actual pages. Equity: a single 301 passes signals cleanly, but chains multiply the places where a link can rot into a 404 the next time anything changes.

  • Chains (301 β†’ 301 β†’ 200): fine once, toxic when every internal link takes the scenic route. After a redesign-on-top-of-a-redesign, chains breed β€” each migration adds a layer.
  • 302s that should be 301s: "temporary" holds equity back from the destination. Most 302s in the wild are permanent moves wearing the wrong hat.
  • Loops (A β†’ B β†’ A): takes the page out of the index entirely. Usually a CMS rule and a server rule fighting.
  • Protocol/host hops: httpβ†’httpsβ†’wwwβ†’page is three hops before content. Collapse them into one rule.
Migration rule of thumb: every old URL should reach its new home in exactly one hop, and internal links should skip the redirect entirely and point straight at the final URL. Redirects are for the links you don't control.
Reference

Every redirect type, decoded

TypeMeaningSEO effect
301 Moved PermanentlyThe URL has a new permanent home.Transfers ranking signals. The workhorse for migrations and URL changes.
302 Found (temporary)Temporarily elsewhere; the original will return.Old URL stays indexed. Use only for genuinely temporary moves (A/B tests, geo routing).
307 / 308Strict temporary / permanent (method preserved).Same SEO behavior as 302/301; common on HTTPS upgrades (HSTS shows as 307).
Meta refreshAn HTML tag reloads the page after N seconds.Slow and treated with suspicion β€” instant off-site refreshes are a spam/compromise signal. Replace with a server redirect.
JavaScript redirectScript sets location after load.Google usually processes it eventually, but it's the slowest and least reliable option. Last resort only.
FAQ

Redirect questions, answered

Do 301 redirects pass full link equity?

Google has said a single clean 301 passes full PageRank. The loss creeps in with chains β€” every extra hop adds latency, burns crawl budget, and multiplies the chances one link in the chain breaks later. One hop is fine; the goal is never more.

How many redirects is too many?

Googlebot follows up to ten hops before giving up, but trust erodes much earlier. In practice: one hop is normal, two is worth fixing, three or more is a finding that belongs on someone's task list.

What is the difference between a 301 and a 302?

A 301 says "moved permanently β€” transfer the signals to the new URL." A 302 says "temporary β€” keep the old URL indexed." A 302 left in place for months holds ranking signals hostage at an address that no longer exists. If the move is permanent, say so with a 301 or 308.

What is a redirect loop?

A redirects to B, and B redirects back to A (sometimes via a longer circle). Browsers give up with an error and search engines drop the page from the index entirely. Loops usually appear when a CMS rule and a server rule fight each other β€” this tool flags them explicitly.

Should redirects go http β†’ https β†’ www in separate steps?

No β€” that is the classic three-hop chain (http β†’ https β†’ https+www β†’ final page) and it triples the cost of every inbound link. Collapse protocol and host canonicalization into a single rule so any variant reaches the final URL in one hop.

How do I find redirect chains across a whole site?

One URL at a time, this tool. Site-wide, you need a crawler that records every hop β€” PeakKR's site audit traces redirects on every internal link and files the chains as fix-it tasks with an owner.

Doing a full site move? Work through the website migration SEO checklist β€” it covers redirects plus everything else that breaks.

Do this on every page, without the copy-paste. The PeakKR SEO Assistant for Chrome runs these checks on whatever page you're viewing β€” plus broken links, Core Web Vitals, live tag inspection, and one-click tasks into your agency workspace.

Get the Chrome extension Try PeakKR free

More free tools