Internal URL Redirect Chain: How to Find and Flatten It

What this means

A single redirect is normal and healthy. You move a page, you 301 the old URL to the new one, and search engines pass the signals along. A redirect chain is different. It happens when the URL you redirect to is itself a redirect, which then points somewhere else again. So a request travels A to B to C before it finally reaches a live page that returns a 200 status code.

SEO ProCheck flags the "Internal URL Redirect Chain" issue when an internal link on your site points at a URL that triggers two or more consecutive redirects. The starting point is internal and under your control, which is exactly why this one is worth fixing: you own the link, so you can repoint it.

Chains build up quietly over time. A site migration adds one redirect, an HTTP-to-HTTPS rule adds another, a trailing-slash rule adds a third, and suddenly one internal link fires three hops to reach a page that has a perfectly clean URL.

Why it matters

Chains are rarely catastrophic, but they cost you on several fronts at once:

• Wasted crawl budget. Each hop is a separate request. Search crawlers spend several fetches to reach one page of content, which means fewer of your real pages get crawled in a given visit.
• Equity leakage. Redirects are generally believed to pass most signals, but a little can be lost at each hop. Stacking hops is the kind of slow drip you want to avoid.
• Slower users. Every redirect is a round trip to the server before the browser can render anything. On mobile connections, two or three extra hops are felt.
• Google may stop following. John Mueller has stated that Googlebot follows up to about five hops per crawl attempt. Chains that run longer can leave the final destination unreached, and an unreached page does not get indexed properly.

For more on how chains and loops behave, see our guide to redirect chains and loops.

How it gets flagged

Crawlers detect this issue by recording the full response path of every internal link. When a starting URL returns a 3xx status, and the target of that redirect also returns a 3xx, the path is logged as a chain.

In Screaming Frog, the clearest view is the dedicated report. Run a crawl, then open the Reports menu and choose Redirect Chains. The export lists each starting URL, every intermediate hop, the status code at each step (301, 302, and so on), and the final destination with its status. Sitebulb and SEO ProCheck surface the same data under their response-code or redirect sections. The number of hops and the final status code are the two columns you care about most.

How to fix it

There are two layers to fix, and you usually want both:

1. Repoint the internal links

Update the link in your content, navigation, or template so it points directly at the final 200 URL instead of the old starting URL. This removes the chain from the user's path entirely and is the most direct win. Use the redirect chains export to map each starting URL to its final destination, then search-and-replace those links across your pages. For broader context on link hygiene, see our internal linking guide.

2. Flatten the server redirect rules

Even after you fix internal links, the chain still exists for external links and bookmarks. Edit your redirect rules so each old URL points straight at the final destination in a single hop. In an .htaccess file, that means replacing a sequence of rules with one rule per old URL that targets the final page. Order your protocol and host rules (HTTP to HTTPS, non-www to www) so they resolve in one combined step rather than stacking. Always use a 301 for permanent moves so signals are passed cleanly; see 301 vs 302 redirects if you are unsure which to use.

After both changes, recrawl and confirm the starting URLs now reach a 200 in zero or one hop.

False positives

A few flagged chains are not worth chasing:

• Protocol plus host normalization. A jump from HTTP to HTTPS and then non-www to www is two hops, but if it is enforced site-wide and resolves quickly, the priority is low. Still worth combining into one rule when you can.
• Third-party or affiliate links. If the chain lives entirely on a domain you do not control, you cannot flatten it. Make sure your own link points at the cleanest entry URL the partner offers, and move on.
• Intentional staged redirects. Some tracking or consent systems route through an interim URL by design. Confirm the behavior is deliberate before treating it as a defect.