Internal URL Redirect Broken: How to Fix It

This audit flag means a page on your own site links to a URL that does not resolve directly. Instead, that URL fires a redirect, and the redirect sends the crawler and the visitor onward to a broken final destination. The chain looks like this: your page links to URL A, URL A redirects to URL B, and URL B returns a 404, 410, 403, 500, or another error. The link looks fine in your editor, but the journey it starts ends at a dead end.

What it means

A redirect is supposed to be a bridge from an old address to a working new one. When the far side of that bridge has collapsed, the redirect still fires but delivers the user and the search engine to nothing. Crawlers like Screaming Frog and Sitebulb catch this by following the full redirect path and checking the status code of the final URL, not just the first hop. If that final status is in the 4xx (client error) or 5xx (server error) range, the issue is raised. As Sitebulb describes it, the hint triggers whenever the redirect target returns a 4xx or 5xx header.

Why a broken internal redirect is worse than a broken external one

When you link out to another site and that link breaks, the failure sits on infrastructure you do not control. A broken internal redirect is different: every part of the chain lives on your own domain. You set the link, you configured the redirect, and you own the page that is now returning an error. There is no external dependency and no one else to wait on, so search engines reasonably expect you to keep your own house in order. A site that routes its own internal links into dead ends signals neglect, and that erodes the quality signals you are working to build.

Impact on crawl and user experience

For crawling, every redirect hop costs resources. Google's documentation notes that internal links should point to final URLs, not redirected ones, and that processing redirects in a chain consumes crawl budget that would otherwise go to pages that matter. When the chain ends in an error, that budget is spent for zero return: no content is reached, no link equity flows to a live page, and the broken target may eventually be dropped from the index.

For visitors, the experience is plainly bad. A person clicks an internal link expecting your content and is bounced to an error page instead. That breaks the user journey, sends them back to search results, and damages trust in your navigation. On internal links this is especially harmful because these are the paths you actively recommend people follow.

How to diagnose

The goal is to see the full chain: source page, linked URL, redirect target, and final status code. In Screaming Frog, crawl the site, then open Reports > Redirects > All Redirects and filter the Final Status Code column to 404 (repeat for other error codes). The Source is the page carrying the link, the Address is the redirecting URL, and the Final Address is the broken destination. You can also use Bulk Export > Response Codes > Client Error (4xx) Inlinks and Server Error (5xx) Inlinks.

In Sitebulb, open the affected URL from the URL List, click URL Details, and switch to the Incoming Links tab. That lists every page linking to the broken URL along with the anchor text, so you know exactly what to edit.

You can confirm any single chain from the command line:

curl -sIL https://seoprocheck.com/old-page/ | grep -i -E "HTTP/|location"

# Example output of a broken chain:
# HTTP/2 301
# location: https://seoprocheck.com/new-page/
# HTTP/2 404      <-- final hop is broken

How to fix it

There are two levers, and the right fix usually uses both. First, decide the correct live destination. If a genuine replacement page exists and returns 200, that is your target. If nothing relevant survives, send the link to the most appropriate live page (a parent category, for example) or remove it entirely.

Option 1: repoint the redirect

If the redirect should stay (because external links or bookmarks also rely on it), edit the redirect rule so its target is a live URL that returns 200. In an Apache .htaccess file:

# Before: target /gone-page/ now 404s
Redirect 301 /old-page/ https://seoprocheck.com/gone-page/

# After: point at a live replacement
Redirect 301 /old-page/ https://seoprocheck.com/new-page/

Option 2: repoint the internal link

Even after fixing the redirect, your internal links should not route through a redirect at all. Edit each source page so the link points directly to the final live URL, skipping the hop entirely. This is the change Google recommends: internal links go to final URLs, never to redirected ones.

<!-- Before -->
<a href="https://seoprocheck.com/old-page/">Read the guide</a>

<!-- After: link straight to the live 200 URL -->
<a href="https://seoprocheck.com/new-page/">Read the guide</a>

After editing, recrawl to confirm the chain now resolves to a single 200 response, and update your XML sitemap if any affected URLs appear in it.

Common mistakes

A frequent error is fixing only the redirect and leaving the internal link pointed at the redirecting URL; the page now resolves, but every internal click still wastes a hop. Another is repointing a redirect to the homepage as a catch-all, which Google can treat as a soft 404, barely better than the original error. A third is editing the link in the page builder but forgetting it also lives in a navigation menu, a reusable block, or a footer widget, so the same broken path survives elsewhere. Finally, do not assume a 200 in the browser means success: a soft 404 returns 200 while showing a "not found" message, so always verify the real status code.

FAQ