Home >Blog

Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets

Published 2026/09/19Updated 2026/09/19

Redirects quietly shape your site’s rankings. A clean 301 from an old URL to its new home passes link equity and keeps visitors moving. A messy setup — chains, loops, or targets that lead nowhere — leaks equity and drives users into dead ends. This checklist walks through finding each problem, judging how serious it is, and fixing the worst cases first.

What a redirect audit covers

A redirect audit checks every URL that returns a 3xx status and answers three questions: where does it point, how many hops does it take to get there, and does the final destination actually exist? The three problems you are looking for are:

Redirect chains — a URL that redirects two or more times before reaching the final page.
Redirect loops — a URL that redirects to itself or back to a previous hop, so the request never resolves.
Broken targets — a redirect that points to a page returning 404 or another error status.

Step 1: Collect every URL that can redirect

Start with a complete list of redirect sources:

Export all URLs from your sitemap and crawl your site to capture every internal link.
Include old URLs you know were retired: deleted pages, changed paths, moved content, and migrated domains.
Add external sources that point at your site — your crawler will pick up the redirects when it follows the links.

Feed the list into a tool that reports the final URL and status for each hop. Run the check without following redirects first, so you see the raw 3xx response and its Location header.

Step 2: Find chains and measure their length

A chain exists when a URL redirects to a URL that redirects again. Track the full path:

https://example.com/old-path
  → 301 https://example.com/blog
  → 301 https://example.com/blog/post
  → 200 final page

Flag any chain longer than two hops. Each hop adds latency and, in most models of link equity, each extra redirect dilutes the authority passed to the final page. Chains also make debugging harder: when one link in the middle breaks, every URL behind it breaks too.

Most chains come from migrated content being redirected more than once over time — a CMS change, then a domain move, then a path reorganization. The fix is to flatten each chain into a single direct 301 from the original URL to the final URL.

Step 3: Detect loops

A loop is a chain that never ends:

https://example.com/a → 301 https://example.com/b
https://example.com/b → 301 https://example.com/a

Browsers stop following after a fixed number of redirects and show an error, and crawlers give up sooner. Loops usually come from two rules that match each other, such as a trailing-slash rule and a non-trailing-slash rule fighting, or a www redirect and a non-www redirect both active on the same host.

When you find one, trace the rule set and remove the rule that creates the cycle. Keep a single canonical redirect for each path pattern.

Step 4: Check every final target

For each chain, verify that the destination returns 200 and that the page is the intended one:

Compare the destination title and URL to the source page — a redirect that lands on an unrelated page is worse than no redirect.
Confirm the destination is not itself a redirect or a soft-404 page.
Check that the destination is indexable unless you deliberately want it noindexed.

Broken targets are the most common audit finding because sites change after the redirect was created. A redirect written for a page that was later deleted becomes a 404 funnel.

Step 5: Look for common redirect mistakes

Run through this list of frequent problems:

Mixed status codes — 302 used where 301 belongs, or 301 used for temporary moves. Use 301 only for permanent moves; temporary content changes should use 302 or 307.
Relative URLs in Location headers — some configurations emit relative paths that clients resolve inconsistently.
Protocol and host mismatches — http to https is normal, but a redirect that hops http → https → www → final adds an unnecessary chain.
Trailing-slash inconsistencies — /path and /path/ resolving differently fragments your URL structure.
Query strings dropped — a redirect that loses parameters breaks tracking links.
Redirects pointing to redirects from external sources — third-party links are outside your control, but the landing page they reach still matters.

Step 6: Prioritize fixes

Not every redirect problem deserves equal attention. Fix in this order:

Loops and infinite redirects — users and crawlers cannot reach the page at all.
Broken targets — the redirect actively destroys value by sending traffic to a 404.
Chains of three or more hops — flatten them to one hop.
Two-hop chains and mixed status codes — clean them up during the same pass.
Cosmetic issues — trailing-slash and query-string inconsistencies, handled when convenient.

After each batch of fixes, re-run the audit and confirm that the affected URLs now resolve in one hop to a 200 page.

Common questions

How long can a redirect chain be before it matters? Any chain beyond one hop has a cost; chains of three or more hops should be fixed as part of routine maintenance. Search engines treat long chains as a signal to stop following.

Should I keep redirects forever? A well-targeted 301 can stay in place indefinitely, but audit them periodically because the destination may have changed. If a redirect no longer serves a meaningful destination, remove it and let the old URL 404 with a helpful error page.

Do redirects affect page speed? Each hop adds a full round trip. On a slow connection, a three-hop chain can add a second or more of latency before the page even starts loading.

Next steps

Run the audit on your highest-traffic sections first. Export the full hop map, fix loops and broken targets immediately, then flatten chains. Schedule a repeat audit after any major site change — migrations, redesigns, and CMS upgrades are when redirect problems multiply.

FAQ

How long can a redirect chain be before it matters?

Any chain beyond one hop has a cost; chains of three or more hops should be fixed as part of routine maintenance. Search engines treat long chains as a signal to stop following.

Should I keep redirects forever?

A well-targeted 301 can stay in place indefinitely, but audit them periodically because the destination may have changed. If a redirect no longer serves a meaningful destination, remove it.

Do redirects affect page speed?

Each hop adds a full round trip. On a slow connection, a three-hop chain can add a second or more of latency before the page even starts loading.

Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets

What a redirect audit covers

Step 1: Collect every URL that can redirect

Step 2: Find chains and measure their length

Step 3: Detect loops

Step 4: Check every final target

Step 5: Look for common redirect mistakes

Step 6: Prioritize fixes

Common questions

Next steps

FAQ

Table of Contents

Information

Tags

More Posts

301 vs 302 Redirects: When to Use 301, 302, 307, and 308

How to Find the Final URL Behind a Short Link

What Is a Redirect Chain? A Clear Guide With Real Examples

Too Many Redirects: Causes, Diagnosis, and Fixes

Do Redirect Chains Hurt SEO? What Google Recommends

How to Set Up and Test HTTP to HTTPS Redirects Correctly