Redirect Chain

Redirect chains commonly accumulate over time through successive site migrations or URL restructures, where each change adds a new redirect on top of old ones instead of updating the original redirect to point straight to the current final destination. Each additional hop in a chain adds real page-load latency (a meaningful Core Web Vitals concern for a chain of several hops) and, historically, was believed to dilute link equity with each additional redirect step — while Google has stated it can generally follow reasonable chains without major signal loss, very long chains still risk not being fully followed and add unnecessary technical debt regardless. Auditing and flattening chains (updating every redirect to point directly to the final URL) is standard technical SEO hygiene, particularly valuable to check after a series of migrations.

Example

A technical audit finds a URL redirecting through four intermediate hops before reaching its final destination, the result of three separate site migrations over five years — flattened to a single direct redirect, improving load speed and simplifying future maintenance.

Related terms

• Redirect (301/302)
• Site Migration
• HTTP Status Code
• Page Speed
• Core Web Vitals
• Technical SEO
• Link Equity