Tested internal link returned a broken-destination status
ShipReady found one or more same-origin destinations that returned 404, 410, or a server-error status to its bounded link probe.
Why it matters
A link to a destination that consistently returns an error can leave visitors at a dead end and should be reviewed in the page that links to it.
How ShipReady detects it
What it inspects
ShipReady collects same-origin links from successfully fetched pages and includes same-origin URLs discovered but not yet fetched. It does not probe external links or re-request pages already fetched by the crawl.
Candidates are deduplicated and tested within a fixed probe budget. The scanner uses a HEAD request where possible and falls back to GET when HEAD is refused.
What triggers a finding
The rule triggers when a tested destination returns 404, 410, or a server-error status.
What the evidence shows
The report lists up to five same-origin destinations and the statuses returned to the scanner's request. The finding is associated with the fetched pages that linked to those tested destinations.
Limits of this check
ShipReady does not perform a complete site crawl. Redirects, 200, 204, 403, and 429 responses do not trigger this rule; 403 and 429 are deliberately treated as possible bot mitigation. Network failures and unavailable responses produce no finding, so silence is not proof that every link works.
How to fix it
Review each tested destination
Confirm whether the linked URL should exist, has moved, or should be removed from the linking page.
Update the source page deliberately
Point the link to an intended live destination, restore the intended route, or remove a link that no longer serves a purpose.
How to verify the change
Verify the deployed link
Request the exact destination and follow the link in a browser after deployment.
Expected: The intended same-origin destination responds successfully for normal visitors.