What an external redirect is
You link internally to a URL that lives on your own domain, say yoursite.com/go/partner. A crawler follows that link expecting to stay on your site. Instead the server answers with a 301 or 302 pointing to anotherdomain.com/landing. The redirect target is external, off your domain entirely. That is an external redirect surfaced from an internal link, and most audit tools call it out precisely because the hop crosses a domain boundary you did not intend to cross for an internal navigation link.
The distinction that matters: an ordinary internal redirect stays on your domain, which is normal and fine when a page moves. An external redirect ends somewhere you often do not control. Sometimes that is deliberate, like an affiliate /go/ cloak. Often it is not, and it points at a stale partner, a domain you sold, an expired campaign, or worse, a path that got hijacked.
Why it matters for SEO and crawling
Three real costs. First, crawl budget. Every internal link that fires a redirect forces an extra request. On a large site that adds up, and Google spends fetches resolving hops instead of discovering fresh content. Second, link equity dilution. A 301 passes most signals, but each hop is a small tax, and when the destination is off-domain you are handing that equity to someone else's site. Third, and this is the one that gets people fired, an external redirect can be a security signal. If an internal link is silently bouncing users to a domain you do not recognize, you may have an open redirect being abused or an outright compromise. That is not an SEO nuisance, that is a get-someone-on-the-phone problem.
There is also a plain user-experience angle. People click expecting to stay on your brand and land somewhere foreign. Trust drops, and if the destination is dead they hit an error on a domain that is not even yours to fix.
The hop, drawn out
How to detect external redirects
| Method | How | Signal you want |
|---|---|---|
| Screaming Frog | Crawl, open Response Codes then Redirection (3xx), sort by Redirect URL domain | Redirect target on a different host than source |
| Reports export | Bulk Export then Response Codes then Redirect Chains | Chains where the final URL leaves your domain |
| Server logs | Grep access logs for 301/302 with off-domain Location headers | Real crawler and user hits on redirecting paths |
| Sitebulb | Redirect hints and chain reports | Internal source URLs resolving off-site |
Screaming Frog is the fast path. Crawl, filter to 3xx, and add the Redirect URL column. Any row where the source is your domain and the redirect target is not is your list. Export it, because the useful part is finding which internal pages contain the offending links so you can edit them at the source.
Fixing it step by step
1. Triage each external redirect. Is it intentional (an affiliate or partner cloak) or accidental (a stale link, a moved partner, a compromised path)?
2. For accidental ones, update the internal link to point directly at the correct final URL. If the destination is genuinely off-site and legitimate, link to it directly with a normal external anchor so there is no server hop.
3. For intentional affiliate cloaks, confirm the destination is still live and still yours to send traffic to, and consider marking those links appropriately so you are not passing signals you do not mean to pass.
4. For anything you cannot explain, treat it as a security finding. Check your redirect rules, .htaccess, and any open-redirect endpoints. An internal path bouncing to an unknown domain is how open-redirect abuse looks in the wild.
5. Re-crawl and confirm the internal link now resolves in one request with no cross-domain hop.
- Link directly to the final destination URL
- Audit every internal link that fires a 3xx
- Confirm affiliate cloaks still point where you think
- Treat unexplained off-domain hops as security issues
- Re-crawl after edits to confirm a single clean request
- Route internal navigation through off-domain redirects
- Leave stale partner links redirecting into the void
- Assume a redirect is safe because it once was
- Ignore open-redirect endpoints attackers can abuse
- Let redirect chains end on a domain you do not control
What good looks like
Internal links resolve in one request to a 200 on your own domain, or link out cleanly to an external site with a plain anchor and no intermediate self-hosted hop. Your redirect map contains only paths you control and understand. A Screaming Frog crawl shows zero internal links whose final destination leaves your domain unexpectedly. Every remaining external redirect is one you can point to and explain in a sentence.
FAQ
Are external redirects always bad?
Does a 301 to another domain pass link equity?
Why does my audit tool flag this as high priority?
How do I find which page holds the bad link?
We map every redirect chain on your site, separate the intentional from the accidental, and flag any off-domain hop that looks like a security risk. You get a clean, prioritized fix list.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
