External URL Redirect Broken: How to Fix It

What "External URL Redirect Broken" means

This issue flags an external link on your site that does not return its content directly. Instead, the URL responds with a redirect (a 301, 302, 303, 307 or 308), and the crawler follows that hop to the final destination. The problem is that the final destination is broken: it returns a client error in the 4xx range (such as 404 Not Found or 410 Gone) or a server error in the 5xx range (such as 500 or 503). In other words, the link technically goes somewhere, but that somewhere is a dead end.

This is subtly different from a plain broken link, which errors immediately. Here, the first request looks healthy because it returns a redirect status, which is why these often slip past quick checks. You have to follow the redirect to discover the failure at the end of the chain. Sitebulb tracks this under a dedicated hint, "External URL redirect broken (4XX or 5XX)," and Screaming Frog surfaces it via Reports > Redirects > All Redirects, filtering the final status code column to any error code.

Why broken external redirects hurt

User experience

A reader clicks your link expecting a relevant resource. After a brief redirect they land on an error page or a site outage screen. The redirect even adds a small delay before that failure, which makes the experience feel worse than an instant error. Every dead destination is a moment where a visitor questions whether your content is current and trustworthy.

Trust and perceived quality

Outbound links are editorial signals. Google's guidance on qualifying outbound links treats the links you place as statements about the resources you endorse. When those endorsements resolve to errors, the page reads as stale and poorly maintained, and looks neglected to both readers and reviewers assessing site quality.

Link rot and crawl waste

Link rot is the natural decay of links over time as external pages move or disappear. A redirect that once worked can later collapse when the destination is removed. Beyond the bad impression, redirect chains that end in errors waste crawl activity: a crawler follows the hop only to hit a wall. If a redirect lands on an off-topic page or an error, search engines may treat it as a soft 404 and pass little to no value through it.

How to diagnose it

The key is to follow the redirect and inspect the final status code, not the first one. You can confirm a single URL quickly from the command line with curl, which prints every hop and the final code:

curl -sIL "https://example.com/old-link" -o /dev/null \
  -w "final URL: %{url_effective}\nfinal code: %{http_code}\nhops: %{num_redirects}\n"

If the final code is in the 4xx or 5xx range, the link is broken after the hop. To find every instance at once, use a crawler. In Screaming Frog, crawl the site, then open Reports > Redirects > All Redirects and filter the final status code column to any value that is not 200. In Sitebulb, open the Links report and review the external links status table. Both tools export the source page for each broken redirect, so you know exactly which of your pages to edit.

How to fix it

1. Update to a working URL

Most often the resource still exists, just at a new address. Visit the site and find the current page, then point your link directly at that live URL. Link to the final, working destination rather than to an old URL that redirects, so you avoid the hop entirely. This is the best outcome because it preserves the reference you intended.

2. Replace with an alternative source

If the resource is genuinely gone and has no successor, find an equally credible page that covers the same information and link to that instead. Your reader still gets the supporting reference; only the address changes.

3. Use an archived copy

When the original content was unique and irreplaceable, link to a snapshot in the Wayback Machine at web.archive.org. An archived link keeps the citation honest while clearly signalling it is a historical copy.

4. Remove the link

If none of the above applies and the link adds nothing, delete it. Keep the surrounding text readable by unlinking the words rather than leaving a hyperlink to nowhere. A clean sentence beats a dead link every time.

After editing, re-crawl the affected pages and confirm the final status code now returns 200 instead of a 4xx or 5xx.

Common mistakes

The most frequent error is checking only the first response code. The initial redirect looks fine, so people assume the link is healthy and never follow the chain to the broken end. Always test the final destination.

Another mistake is sending the link to your own homepage as a quick patch. When the original link promised topic-specific content, redirecting or repointing to a generic homepage creates a soft 404 that helps no one and passes little value. Match the replacement to the topic the reader expected.

Finally, do not leave the old redirecting URL in place even after finding the live page. Pointing at a URL that still has to redirect adds an unnecessary hop and risks breaking again later if that redirect is removed. Link straight to the final working address.

FAQ