Redirect Chains SEO: Find Them and Collapse to One 301

Redirect Chains: Why Three Hops Cost You Speed and Equity

26 August 2026 · 5 min read · By Milvydas

A chain of gold rings stretching into fog, the nearest ring lit, the last dim

Every extra ring is a round trip. Cut the chain to one hop.

Redirects are how you keep old URLs alive. Chains are how those good intentions accumulate: a CDN rule, a WordPress slash setting, a leftover www canonical, a HTTP→HTTPS at the host. None of them is wrong alone. Together they make every first visit slower than it needs to be.

www, HTTPS and trailing-slash rules should collapse into a single 301, not a tour of every historical URL.

Why it matters

Each hop is another DNS/TLS/request cycle for someone, and a diluted signal for search engines. Google can follow chains; it would rather not. Users on a phone in a train carriage feel it first.

How they appear

http:// → https:// → https://www. → trailing slash.
Old domain → new domain → www version of the new domain.
HTTP 301 to a URL that 301s again because a plugin “fixes” permalinks.

The fix

Pick one canonical host (with or without www), HTTPS only, one slash rule. Point every other variant at that URL in a single hop — at the CDN or server, not in a plugin that runs after another plugin already redirected.

The redirect checker counts hops on the URL you paste. If you see more than one, flatten it, then re-test the homepage, a blog permalink, and a leftover http link from an old directory listing.

Frequently asked

Is a single HTTPS redirect bad?

No. http to https, or non-www to www, as one 301 is expected. The problem is stacking them.

301 or 302?

301 when the move is permanent. 302 for A/B tests and temporary maintenance. Search engines treat a long-lived 302 as a messy 301 anyway — prefer honesty.