Skip to content
PageSoarPageSoar

Redirect chains: send every old address straight to the final page

Each extra hop is another request for readers and crawlers. Google stops following after a limit.

Author: HD4 min read

Table of contents
  1. Key takeaways
  2. How chains form
  3. Why it matters
  4. The fix
  5. Find them
  6. See it on your own site
  7. Sources

How chains form#

A page moves, then moves again. The first redirect now points to the second, and the chain grows with each redesign.

Why it matters#

Google's crawling documentation says its crawlers follow up to 10 redirect hops by default. Each hop also slows the reader down.

The fix#

  1. Point each old address straight at the final page, with a permanent redirect.
  2. Change internal links to the final address, so nobody goes through a redirect at all.

Find them#

The site scan lists redirect chains, ranked by how many pages send visitors into them.

See it on your own site#

The free website check reads a site you name and reports what holds its pages back, with no account and no card. It changes nothing on your site.

Run the free website check

Sources#