Sitewalk / Guides / Issue guides / Redirect chains and loops

Redirect chains and loops: how to find and fix them

A redirect sends visitors and crawlers from one address to another. A chain does it in more than one step. A loop sends them in a circle and never reaches a page.

Check in about 2 minutes

Run this on an address you suspect:

curl -sIL https://example.com/old-page

-L follows the redirects and the output shows each hop. You want one redirect and then 200. Two or more redirects is a chain. The same addresses repeating, and a final "too many redirects" message, is a loop. In a browser a loop shows as a "too many redirects" error.

Why it matters

Which kind of redirect you use matters too. Google treats a permanent redirect (301 or 308) as a signal that the target should be the canonical address, and shows the target in results. A temporary redirect shows the source page.

Fix it

Chain. Point the first address straight at the final page, and update internal links to use the final address. Common causes: http to https combined with www and trailing-slash rules, and old site moves. Combine the rules in the server config, the CDN or the redirect plugin.

Loop. Find the two rules that send the address back and forth. Common causes: conflicting http to https or www rules between the server, the CDN and the CMS, and a redirect plugin pointing to itself. Remove one rule so the address lands on a normal page. Clear caches afterwards.

Check that it worked

Run curl -sIL again. A chain should now show a single redirect to a 200. A loop should end in a 200 within a few hops. Then run an audit.

What Sitewalk found on real sites

Sites with at least one such redirect, on the latest audit of each of 87 sites. Early users, a first look, not a survey.

Check your whole site

Sitewalk follows redirects from every address it crawls, with 200+ other technical checks. In ChatGPT, say:

Audit yoursite.com for technical SEO problems

Get started

Checked on 16 Nov 2026.

More guides

All issue guides ยท All guides