Redirect chain

How chains form

Usually by accident over time: a page moves and gets a redirect, then the new page moves again and gets another, and the first redirect still points to the middle address. Changing from http to https and from www to non-www can add hops of their own.

Why to avoid them

Each hop adds a round trip, which slows the page for visitors. Search engines follow a limited number of hops and may stop before the end of a long chain. Chains also make it easy for a loop to appear, where two URLs redirect to each other and nothing loads.

Fixing them

Point every old URL straight at the final destination in one hop, and update internal links to use the final address directly. When you retire pages in bulk, check the existing redirects that pointed at them and update those too.

Checking for chains

Run old URLs through a redirect checker, which follows each hop and shows the status codes along the way. Check especially after a migration, a domain change or a content cleanup, when many redirects are added at once and old ones can end up pointing at addresses that now redirect again.

Example

An old blog URL redirects to a merged post, which was later merged again. Updating the first redirect to point at the final guide turns a two-hop chain into one hop.

Questions people ask

How many redirects is too many?

Aim for one hop. Two is tolerable; longer chains slow pages down and risk crawlers giving up.

Do redirect chains lose link value?

Search engines say 301 redirects pass ranking signals, but long chains risk not being followed to the end. One hop is the safe choice.