A redirect chain occurs when one URL redirects to another, which redirects again. Each hop adds latency and slightly dilutes the signal passed through, and crawlers abandon chains after a small number of hops.
Keep every redirect to a single hop pointing at the final destination.
Chains accumulate silently during migrations — audit after any URL change.
301 for permanent moves, 302 only when the original genuinely returns.