Redirect Chains Add Requests You Usually Do Not Need

A redirect chain happens when one URL redirects to another URL, which redirects again before reaching the actual page.

For example:

URL A → URL B → URL C → final URL

Every hop adds another request and another place for the journey to fail. The delay may be small on a fast connection, but it becomes more noticeable with network latency.

Why chains accumulate

Redirects often build up through several reasonable changes. A page moves, HTTP becomes HTTPS, the hostname changes, and a trailing-slash rule is added. Years later, an old link takes the scenic route through all of them.

Search engines can follow redirects and generally use them as canonicalisation signals, but long chains waste crawl time and can slow consolidation. The old idea that each redirect always loses a fixed amount of ranking value is too simplistic. There is still little reason to keep avoidable hops.

Point directly to the destination

Use a crawler, HTTP inspection tool, or browser network panel to find the complete chain. Then:

  1. Update internal links to use the final URL.
  2. Change each old redirect so it points directly to the final destination.
  3. Use a permanent redirect such as 301 or 308 when the move is permanent.
  4. Keep a temporary redirect such as 302 or 307 only when the move really is temporary.
  5. Check for loops and confirm the final page returns the expected successful status.

Relative URLs do not inherently prevent redirect chains, and absolute URLs are not an SEO problem by themselves. What matters is that the resolved link points where you intend.

Do not delete an old redirect merely because internal links are fixed. External links and bookmarks may still depend on it. Keep the redirect, but make it a direct one and review the rules whenever URLs change again.