Technical SEO
Broken link
A broken link is a hyperlink whose resolved destination fails to provide the intended resource to the tested user agent in a declared observation context.
What it means
Failure can arise from an invalid reference, DNS or connection error, Redirect loop, access restriction, HTTP error, removed resource or destination that no longer matches the link's purpose. HTTP 404 means the server did not find a current representation and does not know or disclose whether the condition is temporary or permanent. A single timeout is evidence to recheck, not automatic proof of permanent failure.
Why it matters
Recording source page, raw target, resolved chain, user agent, response and time separates repairable authoring defects from access policy, transient infrastructure and intentional removal.
Example
A product guide links to `/manual-v2`, which redirects once and returns 404 for both a browser and crawler on two checks; the replacement manual is confirmed before the source link is updated.
Common mistakes
Do not classify every redirect, `Nofollow`, login wall or temporary timeout as broken; test only the homepage; discard the raw href; redirect unrelated missing URLs; overlook fragments; hide the user agent or promise ranking recovery.
How AYSA handles this
Signals reviewed
source URL, raw href, resolved chain, user agent, status, fragment, content type, capture time
Problem AYSA can identify
AYSA can identify reproducible destination failures, redirect loops, invalid fragments and source links that resolve to a different resource.
Recommendation prepared
The workflow proposes updating, removing or retaining each link only after destination equivalence and ownership are established.
Approval preview
The reviewer sees the source element, full resolution chain, response evidence, candidate destination and exact proposed edit.
Execution
AYSA can apply approved link edits on supported owned sites; it cannot repair or redirect an independently controlled destination.
Verification
A fresh crawl checks the rendered link, response chain and intended content after the approved change.
Limits
Geo, authentication, bot controls and transient outages can produce different observations, so one failed request is not universal proof.
Sources and further reading
- RFC 9110 — HTTP Semantics, status codes — Internet standard
- WHATWG HTML Standard — Links — Technical standard
- Google Search Central — Troubleshoot crawling errors — 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 404 response caused by a broken link?
No. A URL can be requested without any hyperlink, and an intentional missing resource may correctly return 404.
Is every redirect a broken link?
No. A valid redirect can resolve correctly, although source links should be updated when an owned canonical target is known.
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.
