External URL Redirect Broken: How to Fix It

What this check flags

This audit issue fires when an outgoing external link on your site points to a URL that responds with a redirect (a 3XX status code), and the final destination of that redirect is not accessible. The end of the chain returns a 4XX client error, a 5XX server error, or the redirects loop back on themselves so a final page is never reached. Sitebulb documents this as the "External URL redirect broken" hint, and it triggers for any external URL which redirects where the redirect target returns a 4XX or 5XX status code.

The dangerous part is that this is a hidden broken link. If you only check the immediate response of your outbound links, the URL looks fine. It answers with a 301 or 302, which most quick link checkers treat as healthy. The breakage only appears when you follow the redirect to its final destination, which is exactly what your visitors' browsers and search engine crawlers do.

Why this is worse than a plain redirect

A normal redirect is a mild inefficiency. The user clicks, waits an extra round trip, and still arrives at working content. A broken redirect is a dead end with extra steps. The user clicks a link you vouched for, watches the browser hop through one or more intermediate URLs, and then lands on a "404 Not Found" or a server error page on someone else's site. From their point of view, your page sent them somewhere useless.

Search engines follow these chains too. A page that consistently references resources which no longer exist signals neglected, outdated content, and you will not notice it by glancing at the page yourself because the link still "goes somewhere" before it fails.

Redirect loops are the worst variant: the browser bounces between URLs until it gives up and shows a connection error, which looks even more alarming than a tidy 404 page.

How to diagnose it

The key is to always resolve the chain to its final status code, never stop at the first hop.

Follow the chain manually

The fastest spot check is curl from a terminal: the -L flag follows redirects and -I requests headers only, so you see every hop and the final response code. You can also open the link in a private browser window and watch where you end up.

Use a crawler that reports the final status

In Screaming Frog, the Redirect Chains report maps each chain, counts the hops, identifies the source page and flags loops, and its Final Status Code column tells you whether the end of the chain is a 2XX, 4XX or 5XX. The All Redirects export can be filtered by final status code 404 to isolate exactly these hidden dead ends, and Screaming Frog's own guidance notes that following destinations to their final target surfaces 4XX errors you would miss if you never audited the 3XX responses. Sitebulb reports the same finding as this hint, and its URL details view lists every incoming link that references the broken redirect.

Read the chain

Here is the difference between the problem and the fix, as a crawler sees it:

<!-- Broken: redirect masks a dead end -->
your-post.html
  → https://example.com/old-tool        301 Moved Permanently
  → https://example.com/tools/legacy    404 Not Found   ✗ final status

<!-- Fixed: link straight to the live page -->
your-post.html
  → https://example.com/tools/new-tool  200 OK          ✓ final status

How to fix it

1. Find the content's new home

Most of the time the external site moved or renamed the page and the redirect rule simply went stale. Search the destination site for the article or tool you originally linked to, then update your link to point directly at the new working URL. Linking straight to the final 200 destination also removes the redirect hop entirely.

2. Replace or remove the link

If the content is genuinely gone, decide whether the reference still earns its place. Swap it for an equivalent live source, or unlink the text if the sentence still reads well. Do not leave a known dead link in place.

3. Use the Wayback Machine as a fallback

When the original source mattered and nothing replaces it, check archive.org for a saved snapshot. Linking to the archived copy preserves the citation while keeping the link functional; label it as an archived version so nobody is surprised.

4. Re-crawl to confirm

After editing, re-run the crawl or at least re-test each changed URL and confirm the final status code is now 200 with no chain in between.

Common mistakes

Trusting the first status code. A 301 response is not a healthy link. Health is defined by the final destination, so always evaluate the end of the chain.

Repointing to the redirecting URL again. If you fix the link but still target the old URL that redirects, you have only restored the fragile setup. Link to the final working URL directly.

Fixing one page and missing the rest. The same external URL is often linked from several posts. Use your crawler's incoming links view to find every page that references the broken redirect and fix them all in one pass.

Never re-checking. External sites change without telling you. A link that resolved cleanly last year can rot at any time, so make outbound link checks part of your recurring audits.

FAQ