A sequence in which one redirected URL leads to another redirect before reaching a destination (e.g., A -> B -> C).
A redirect chain occurs when an address redirects to a second address that redirects again before reaching the intended page. For example, A may point to B while B now points to C. The visitor eventually reaches C, but the route includes an avoidable intermediate step.
Chains often accumulate when a page moves more than once or separate rules normalize domains and paths. Each step needs to be understood before it is changed. A chain that reaches the right page is different from a loop, which never reaches a stable destination.
A useful repair aims for the intended final destination without breaking meaningful mappings. Update links under your control to point directly to the current page, and review whether old redirect rules can also target it directly. Do not remove an established old address merely because it is no longer part of current navigation; outside links may still use it.
Takeaway: Check the full redirect path, not just whether a URL eventually opens. Reduce unnecessary hops while preserving the relationship between old content and its relevant replacement.
Example
An old article address redirects to a renamed version, which later redirects to the final guide URL. A review confirms that all three addresses represent the same guide. The old rule can then be considered for a direct route to the final guide, while internal links are updated to avoid entering the chain.
What to check
Record each status and destination before editing. Test the old source again afterward, including whether it reaches the correct content rather than an unrelated page. Avoid broad rewrites that collapse different old topics into one generic destination simply to shorten the chain.
For more detail, see Redirections in HTTP.