What is a redirect chain?
A redirect chain happens when URL A sends users to URL B, which then sends them to URL C. Search engines and browsers can follow chains, but every extra hop wastes crawl budget, slows page loads, and increases the chance of a broken final destination.
Common sources include HTTP to HTTPS migrations, www canonicalization, CMS permalink changes, and leftover plugin rules stacked over years.
Why redirect chains hurt SEO and UX
Chains dilute link equity transfer, create fragile dependency paths, and make analytics harder to trust. On mobile networks, each hop can add noticeable latency before content appears.
- Crawl budget is spent resolving hops instead of discovering new pages
- Users wait longer before the destination renders
- One broken hop in the middle turns the whole path into a soft 404 experience
- Marketing links and QR codes quietly degrade over time
How to find redirect chains
Start with a full-site crawl that follows redirects and records the full path. In Verify My Link, redirect findings show up alongside broken links so you can see both dead ends and inefficient hops in one report.
Prioritize chains on high-traffic landing pages, product URLs, and anything linked from ads, email, or partner sites.
- Export or review redirect findings from your latest scan
- Group chains by shared hop patterns (for example, all http:// variants)
- Map old URLs directly to the final 200 destination
- Remove intermediate rules once the single-hop map is live
Best-practice fix pattern
The ideal state is simple: every outdated URL should 301 (or 308) directly to the final canonical URL in one hop. Avoid temporary redirects for permanent moves, and keep protocol, host, and trailing-slash rules consistent sitewide.
- Collapse A → B → C into A → C
- Prefer one canonical host (www or non-www) and one protocol (HTTPS)
- Update internal links to point at the final URL instead of relying on redirects forever
- Re-scan after deploy to confirm chains are gone
WordPress and migration notes
WordPress sites often accumulate chains from permalink changes, redirection plugins, and domain moves. After a migration, scan both the old path patterns and the new sitemap destinations. Our WordPress redirect checker and post-migration quality page are useful starting points.