Redirect External Links

Element Code: LI-030

What "Redirect External Links" actually flags

This check looks at every outbound link on a page, meaning a link whose href points to a different domain than the one you're on, and tests whether that URL resolves directly (a clean 200) or whether it 301s or 302s somewhere else before landing on the final page. If it redirects, the link gets flagged. Simple as that.

It's easy to confuse this with internal redirect chains, but they're different problems with different causes. An internal redirect chain usually happens because your own site restructured URLs over time and nobody went back to update the internal links. A redirecting external link happens because the site you're linking to changed something on their end: they migrated to HTTPS, moved to a new URL structure, merged two pages, or switched domains entirely. You have zero control over that. All you control is whether your anchor still points at the address they used to have, or the one they actually serve now.

A quick example: you link to http://example.com/guide in an article from three years ago. Example.com has since moved to HTTPS and restructured their URLs, so that link now 301s to https://example.com/resources/guide-2024. Your visitor still gets there, eventually. But the request took an extra round trip, and if example.com ever decides to retire that old URL instead of keeping the redirect alive forever, your link breaks with zero warning.

Why it's worth fixing

Let's be accurate about this instead of catastrophizing it, because a lot of SEO content treats any redirect as if it's setting your rankings on fire. It isn't. Google has been explicit that 301 and 302 redirects pass essentially the full value of a link to the destination URL, John Mueller has said this directly and Gary Illyes confirmed back in 2016 that 30x redirects (301, 302, 307, 308) all pass along signal to their target. So if your only concern is "am I losing link equity by linking through a redirect," the honest answer is: not much, if the redirect is a clean 1:1 mapping to an equivalent page.

That said, there are four real costs that do apply, and they're the actual reasons this check exists:

1. Latency. Every redirect hop is a full HTTP round trip before the browser gets to the real content. On a single link this is milliseconds. Across a content-heavy page with dozens of outbound citations, it adds up, and it's pure waste since the direct URL would get the visitor there just as reliably and faster.
2. Link rot risk. A redirect is a promise the other site is making to keep forwarding traffic. Promises expire. Sites get sold, migrated, deprecated, or restructured again, and old redirect rules get dropped in the process. When that happens your link goes from "works but slow" to "404, sends the user to a dead end." A direct link to the current URL has no expiration date tied to someone else's server config.
3. Diluted signal on 1:1 mismatches. The PageRank-passing guarantee assumes the redirect target is a genuine equivalent of the old page. When it's not (say the old URL now redirects to a homepage or an unrelated category page because the specific content was pulled), Google can treat that as a soft 404 and the value passed through drops. You want your link pointing at content that actually matches what you cited, not wherever a stale redirect happens to dump the visitor now.
4. Trust and polish. This is a UX and credibility issue as much as a technical one. Editorial sites and reference pages get judged partly on link hygiene. A page riddled with outdated, redirecting citations reads as unmaintained, and it's a signal (to readers and to any manual reviewer) that content hasn't been kept current.

None of that means "301s are killing your rankings." It means redirecting external links are a maintenance debt that quietly gets worse the longer you ignore it, and it's cheap enough to pay down that there's no good reason not to.

How the hop actually plays out

Direct external link (what "good" looks like) Your page Final page (linked href, live 200)

One hop rarely tanks rankings. It does add latency and a future breakage risk you don't need.

How to detect it

You need a tool that actually follows redirects on external URLs, not just internal ones. A few that work:

• Screaming Frog SEO Spider: the standard here. Configure it to check external links (Configuration > Spider > Crawl, tick "Check External Links"), then after the crawl finishes, filter the External tab by Status Code and look for 301, 302, 307, 308. The Redirect Chains report will also show you how many hops each one takes and where it finally lands, which is useful for spotting the worst offenders (2+ hop chains) versus a harmless single 301.
• Sitebulb: similar capability, with a dedicated "External Links" audit that flags redirected and broken outbound links in its hint system, plus a visual chain view that's a bit easier to skim than Screaming Frog's export for a quick gut check.
• Server log analysis: not useful for this specific check. Your logs show requests hitting your server, not what happens to outbound links after a visitor clicks away. Skip it for this one, it's the wrong tool for the job.
• Google Search Console: also not built for this. GSC reports links pointing to your site and some crawl stats, but it doesn't audit the outbound links you're placing on your own pages. Don't waste time hunting for this in GSC.
• Manual spot checks: for a smaller site, or to double check a Screaming Frog flag, open the link in an incognito window and watch the URL bar. If it changes after load, that's your redirect. Browser dev tools' Network tab will show you the exact status code and hop count if you want confirmation.

Run this as a recurring audit, not a one-time cleanup. Content ages, and other people's URLs change on their own schedule with zero notice to you. A quarterly external link crawl on any page with a meaningful number of outbound citations (resource pages, roundups, "further reading" sections) will catch new rot before it piles up.

How to fix it, step by step

1. Pull the full list of redirecting external links. Export the External tab from Screaming Frog filtered to 3xx status codes. Note the source page, the original href, and the final destination URL after all hops resolve.
2. Confirm the final destination is actually equivalent. Before you blindly swap the href, load the final URL and check it's still the content you meant to cite. Sometimes a redirect dumps you on a homepage or a generic category page because the specific article got removed, in which case updating the href just points you at the wrong content faster. That's a "remove or replace the link" case, not a "fix the href" case.
3. Update the anchor href to the final URL. Straightforward find-and-replace in your CMS or database for the specific link instances. Don't do a blanket domain-wide replace without checking each one individually, since not every redirect on a given domain necessarily points to the same place.
4. Decide what to do with low-value or dead links. If the final destination is thin, off-topic now, or the whole domain has gone dark, don't force a fix. Either swap in a better, current source that covers the same claim, or remove the link and adjust the surrounding sentence so it doesn't read like something is missing.
5. Re-crawl to confirm. After updates, run the external link check again and confirm those specific URLs now come back 200 directly, no hop.
6. Put it on a schedule. Quarterly or twice a year for content-heavy sites. This is never a "fix once, forget forever" job because you don't control the other side of the link.

Comparing redirect scenarios

Do this, not that

What good looks like

On a clean page, every outbound link resolves in one request: no 301, no 302, no chain to untangle. The anchor text still matches what's actually on the other end, and nothing you're citing has quietly turned into a homepage or a 404 since you wrote it. That's the whole target. It's not a glamorous fix, but it's a cheap one, and it's the kind of housekeeping that separates a page that's actually maintained from one that was written once and abandoned.

FAQ