Long redirect chain (3+ hops)

What this means

This URL passes through three or more redirects before settling. Each hop adds latency and dilutes link equity, and Googlebot follows only a limited number of hops in one pass. (Distinct from the legacy http_redirect_chain check, which fires at 2+ hops — this one flags the longer chains that risk being abandoned outright.)

How to fix it

Collapse the chain into a single redirect from the original URL straight to the final destination, and update internal links to point at the destination directly.

Fix effort

This check needs a developer fix: it turns on a routing, hosting or infrastructure decision that no automatic edit can make safely.

Authoritative source

https://developers.google.com/search/docs/crawling-indexing/301-redirects