A clean redirect passes nearly all your ranking authority to the new URL. Chain several together and you add latency, waste crawl budget, and risk leaking equity. Loop them and the page breaks entirely. Here's how to find and collapse them.
Redirects accumulate over a site's life — every migration, rename, and protocol change adds a rule, and the rules start tripping over each other.
No one sets out to build a redirect chain. They emerge: you move a page, then move it again a year later, and now the original URL hops twice. You add an HTTPS redirect, then a trailing-slash redirect, and a URL passes through both. Do this across a site over several years and you get a tangle of multi-hop redirects — and occasionally two rules that point back at each other and form a loop. The audit flags both chains and loops because both cost you, in different ways.
One degrades performance and authority; the other breaks the page completely.
Every hop in a chain is an extra round-trip for the user (slower page loads) and an extra request for the crawler (wasted crawl budget). While Google follows several hops and consolidates signals, each hop adds risk: a chance of equity loss, a chance the chain breaks if one hop later 404s, and slower indexing of the final page. There is never a benefit to a chain — only downside to minimise.
A loop never resolves. The browser eventually shows a "too many redirects" error and the crawler abandons the URL. The page is effectively offline — no users, no indexing, no rankings. Loops are almost always caused by conflicting rules (an HTTPS rule and a trailing-slash rule each undoing the other) and are urgent: they take a live page completely out of search.
Collapse, then point links at the final URL.
Step 1 — Map the hops. Crawl the site and identify every redirect and where it ultimately lands. The audit surfaces redirect chains and the pages whose internal links point to a redirect. Step 2 — Collapse each chain. Rewrite the redirect rules so the first URL goes straight to the final destination: turn A→B→C into A→C and B→C. Step 3 — Break loops at the source. Find the conflicting rules and fix the order or logic so the cycle resolves to a single final URL. Step 4 — Update internal links. Change internal links so they point at the final URL directly, not at a redirecting one — this removes the hop entirely for crawlers and users. Step 5 — Use the right status code. Permanent moves should be 301s; see 301 vs 302.
Aim for zero unnecessary hops — every redirect should go straight to the final URL. While Google follows several hops, more than one is worth collapsing, and long chains risk being abandoned. The simplest rule: one redirect, directly to the destination.
No. If you know the final URL, link to it directly. Linking to a URL that redirects wastes a hop on every crawl and every click, and it's entirely avoidable. The audit flags internal links pointing to redirects for exactly this reason.
Conflicting server rules — most often an HTTPS-enforcement rule and a trailing-slash (or www/non-www) rule that each rewrite the URL in a way that re-triggers the other. Fixing the order and conditions of those rules resolves the loop.
Free to start. Find redirect chains, loops and links pointing to redirects across your site.
Start my free audit