What is a redirect chain?

Redirect chain, explained

Chains build up over time. You move http:// to https://, then bare domain to www, then rename a page, then add a trailing slash. Each change was fine on its own, but an old link now goes http://example.com/features → https://example.com/features → https://www.example.com/features → https://www.example.com/product/. That's three hops before any content loads.

Google's documentation says its crawlers follow up to 10 redirect hops by default. Beyond that, or when the chain loops back on itself, Search Console reports a "Redirect error" in the Page indexing report, which it describes as a redirect chain that was too long, a redirect loop, or a similar problem. Short chains usually still work for Google, but every hop is another request for users on slow connections and another place for something to break.

The fix is to collapse chains so every old URL points straight at the final destination in one hop. Then update internal links, canonicals and sitemap entries to the final URL, so the redirect only catches outside links and old bookmarks. Loops usually come from two rules fighting each other, for example a CDN forcing a trailing slash while the app strips it.

Audit after every migration. Chains are invisible in a browser, which follows them silently.

Why it matters for founders

Rebrands, domain changes and URL cleanups stack up fast in a startup's first years. Collapsing chains keeps old backlinks pointing at live pages and removes a whole class of crawl errors.

Example

A redirect checker shows your most-linked blog post takes four hops to load. You change the old URL's rule to point directly to the current URL, so it now resolves in one 301.

Common mistakes

• Adding new redirects on top of old ones instead of updating the originals.
• Conflicting trailing-slash or www rules at the CDN and in the app, causing loops.
• Linking internally to URLs that redirect.
• Testing only in a browser, which hides the hops.