Technical SEO
Broken external link
A broken external link is a hyperlink on an analysed source page whose resolved outside-boundary destination fails a declared availability rule at the recorded check time.
What it means
Evidence can include terminal 404 or 410 responses, persistent 5xx errors, DNS failure, invalid URL syntax or redirect failure. A 301 to a valid replacement may work, while 401, 403, 429 or a timeout can reflect access policy, rate limiting or transient conditions and require retry or browser review.
Why it matters
A response-aware definition prevents useful citations from being deleted because one bot request was blocked and directs edits only to source pages the user controls.
Example
An owned guide links to a report that returns 404 on two spaced checks with no valid redirect; the proposal replaces it with the publisher's confirmed successor and preserves the original anchor context for review.
Common mistakes
Do not mark every non-200 broken, ignore redirects or fragments, test once without user-agent and retry policy, replace a citation with an unrelated homepage, edit third-party pages, or assume a successful response proves the content is still equivalent.
How AYSA handles this
Signals reviewed
owned source, original href, redirect chain, terminal status, DNS state, check time, retry result, replacement candidate
Problem AYSA can identify
AYSA can identify invalid URLs, terminal failures, redirect loops, repeated server errors and candidate replacements that are not equivalent.
Recommendation prepared
The workflow retries ambiguous cases, records terminal evidence and proposes remove, replace or retain only on the owned source page.
Approval preview
The user sees the source sentence, full redirect chain, response history, candidate content and exact before-and-after link.
Execution
AYSA can apply an approved replacement or removal on supported WordPress content; it cannot repair the external server.
Verification
The owned page is recrawled and the approved destination is checked again, with response and content equivalence recorded separately.
Limits
Availability can change after the check, access controls can mislead automated clients and a working replacement does not guarantee search impact.
Sources and further reading
- Google Crawling Infrastructure — HTTP status codes and network errors — Official crawling documentation
- RFC Editor — RFC 9110 HTTP Semantics — Internet standard
- WHATWG — URL Living Standard — Web standard
- Google Search Central — Link best practices — Official search documentation
Written by Marius Dosinescu. Reviewed by AYSA SEO Editorial Team · 2026-07-28 00:00:00.
Quick answers
Frequently asked questions
Is every non-200 external response a broken link?
No. Redirects can resolve successfully, while authorization, rate limiting and transient server errors require contextual review.
Does HTTP 200 prove the linked citation is still valid?
No. The destination can return unrelated or error-like content; equivalence still needs content review.
SEO execution campaign
Less SEO work. More organic growth.
AYSA monitors your website, finds opportunities, prepares the work, asks for approval and executes accepted changes so you can grow without living in SEO tools.
