Question 1

Is a two-hop redirect chain acceptable, or should it always be one hop?

Accepted Answer

One hop (A → B) is the goal for any redirect. Two hops (A → B → C) is technically functional but suboptimal — it adds latency and a small amount of link equity dilution. Three or more hops is where the impact becomes material: noticeable load time additions, meaningful crawl budget waste, and more significant PageRank dilution. In practice, a two-hop chain on a low-traffic page is rarely worth urgent attention. Two-hop chains on high-authority pages with external links, or chains of three or more anywhere, should be resolved as part of any technical cleanup.

Question 2

Does removing a redirect chain affect rankings?

Accepted Answer

Flattening a chain to a single redirect can result in modest ranking improvements for the final destination URL, because more link equity flows to it without the dilution of multiple hops. The effect is usually small for two-hop chains but more noticeable for three or more. The more reliably measurable improvement is in page speed — reducing redirect hops measurably reduces time-to-first-byte for pages that users land on after following a redirect chain, which can affect Core Web Vitals scores.

Question 3

What's the difference between a 301 and a 302 redirect for SEO?

Accepted Answer

A 301 is a permanent redirect — it tells Google the old URL has moved permanently to the new one, and to transfer ranking signals to the new URL. A 302 is a temporary redirect — it signals that the old URL still exists and should retain its ranking signals, while temporarily forwarding traffic. Google treats 302s differently: it may continue to index and rank the original (302) URL rather than the destination, because it's been told the move is temporary. For any permanent URL change or consolidation, use 301. Only use 302 for genuinely temporary situations (A/B testing, temporary page swaps during maintenance) where you want the original URL to retain its indexed status.

Question 4

How long should redirects stay in place?

Accepted Answer

For pages with external links pointing to them, indefinitely. The cost of maintaining a redirect is negligible; the cost of removing it and breaking an external link is lost ranking authority for the destination page. For pages with no external links and no indexed history, you can safely remove redirects after one to two years — by which point any ranking signals from the original URL have fully transferred. When in doubt, keep the redirect. There's no SEO benefit to removing redirects and a clear risk from removing ones that still receive any external link traffic.

Question 5

How do I find which old URLs need redirects in the first place?

Accepted Answer

Before any URL structure change, export a full list of current URLs from a crawl, the sitemap, and Search Console's indexed pages report. After the change, every URL on that list that's no longer valid needs a redirect to its closest equivalent on the new structure. For historical chains you're auditing after the fact, Search Console's Links report and an external backlink tool (Ahrefs, Semrush) can surface old URLs that still receive external links but aren't on your current crawl — those are the highest-priority redirects to verify are still working correctly.

Question 6

Can too many redirect rules slow down the server itself?

Accepted Answer

At reasonable scale (hundreds to low thousands of rules), no — server-level redirect matching is fast and isn't typically a performance bottleneck. At very large scale (tens of thousands of individual rules, especially regex-heavy ones), poorly optimized redirect rule sets can add measurable server response time. The more common problem isn't rule count but rule order and complexity — badly structured regex rules or rules evaluated in an inefficient sequence can slow matching. If redirect rule count is in the thousands, it's worth checking response time specifically rather than assuming it's fine.

301 redirect

Redirect Chains and Loops: A Quick Audit and Fix