Internal URL Redirect Broken: How to Fix It

What this check flags

This audit hint fires when a crawler follows an internal link, hits a redirect (usually a 301 or 302), and then finds that the final destination of that redirect is not accessible. The destination might return a 404 Not Found, a 410 Gone, a 500 Internal Server Error, or the redirect might loop back on itself and never resolve at all. The redirect promises users and search engines that the content has moved, then fails to deliver anything at the new address, which is why Sitebulb classifies this hint as high priority.

In plain terms: you have a broken internal link, hidden behind a redirect. The link looks fine, the first response is a healthy looking 301, and only by following the chain to the end do you discover the dead page. That is why these issues survive for months on otherwise well maintained sites.

Why this is worse than a normal redirect

A standard internal redirect is a minor inefficiency. One that terminates in an error is an outright failure, hurting on three fronts at once.

PageRank flows into a dead end

Internal links pass link equity, and a redirect is meant to carry that equity through to the final URL. If the final URL returns an error, there is nothing to land on. Every internal link feeding that chain pours authority into a hole, and any external backlinks pointing at the redirecting URL are wasted too.

Users hit errors they cannot explain

A visitor clicks a normal looking link, bounces through the redirect, and ends up staring at an error page. They never see the original URL that caused the problem, so they cannot even work around it.

Common after migrations with stale redirect maps

This pattern is a classic migration leftover. A redirect map gets built once, the migration ships, and nobody revisits it. Later, destination pages get renamed or retired in a second round of changes, and the old redirects keep firing at targets that no longer exist. Internal links written before the migration still point at the legacy URLs, so the whole chain quietly rots.

How to diagnose it

The key is to follow every redirect to its final status code rather than trusting the first response. In Screaming Frog, crawl the site with "Always Follow Redirects" enabled, then export Reports, Redirects, All Redirects. Filter the Final Status Code column to 4XX and 5XX values. The Source column shows the page carrying the broken internal link, Address shows the redirecting URL, and Final Address shows the dead destination. In Sitebulb, the Redirects report lists the affected URLs directly under the "Internal URL redirect broken (4XX or 5XX)" hint, with the referring pages one click away.

You can also spot check a single chain with curl -sIL and read each hop. A broken chain looks like this:

<a href="/old-services/">Our services</a>

GET /old-services/        301 Moved Permanently
  Location: /services-2024/
GET /services-2024/       404 Not Found   <-- dead end

And the same path after the fix resolves in a single healthy response:

<a href="/services/">Our services</a>

GET /services/            200 OK          <-- direct hit, no chain

How to fix it

There are two repairs, and on most sites you should do both.

1. Repoint the redirect to the live equivalent

Find the closest living replacement for the dead destination and update the redirect rule so the old URL resolves there in one hop. This protects every reference you do not control: external backlinks, bookmarks, and stale links elsewhere on your site. The replacement must be genuinely equivalent content, not merely a page that exists.

2. Fix the internal link to skip the redirect entirely

Edit the linking page so the anchor points straight at the final live URL. Internal links are fully under your control, so they should never route through redirects at all. This removes the wasted hop and keeps the link working even if the redirect rule is cleaned up later.

3. Use 410 when the content is gone for good

If there is no sensible replacement because the content is permanently retired, do not invent a redirect target. Remove the redirect, let the URL return a 410 Gone (or a clean 404 with a helpful error page), and delete the internal links that pointed at it. A deliberate 410 is an honest signal that search engines process quickly; a forced redirect to an irrelevant page is not.

Common mistakes

Redirecting everything to the homepage. This feels like a tidy fix but Google treats mass redirects to the homepage as soft 404s, since the destination does not match what the original URL promised. Google's Martin Splitt has explicitly advised against the practice. The pages get dropped from the index just as if they returned errors, and users land somewhere confusing with no idea why.

Fixing only the redirect and leaving the internal links. The hint clears, but you still have internal links routing through redirects, which wastes crawl budget and will break again the next time the redirect map changes.

Never re-auditing after a migration. Redirect maps decay. Recrawl after every significant restructure and check final status codes, not just first responses.

FAQ