Result categories and redirects
Decide which findings need a content edit, an access check or another attempt.
Response categories#
A category describes what Linky observed during a request. It starts an investigation rather than delivering a final verdict about content. Read it with the destination, source context and final response.
Review missing pages and anchors first, then access problems, retries and other errors. Working means no classified problem was detected; important destinations still need a content check.
| Category | Typical finding | Next step |
|---|---|---|
| Missing page | HTTP 404 or 410 | Check whether content moved, should be restored or has a replacement. |
| Missing anchor | The page responds but its fragment target is missing. | Compare the fragment with the intended element ID. |
| Login needed | HTTP 401 | Check whether authentication is expected for readers. |
| Access blocked | HTTP 403 or 451 | Investigate access before calling content missing. |
| Retry needed | No response, timeout, HTTP 408/429 or server error. | Check availability, rate limits and request settings. |
| Redirect | The destination changes before the final response. | Confirm the route and final content. |
| Other error | Another HTTP client error. | Read the actual status and examine the destination. |
| Placeholder link | Empty, # or javascript: link, when enabled. | Check whether it is an intentional interface control. |
| Working | No classified error detected. | Verify important content matches the reference. |
Redirect trail#
Review the path from the original address to the final URL. A 301 followed by the appropriate successful page can be valid. The same redirect ending at a missing page requires investigation.
Redirect information can accompany another category when a URL redirects and then fails. Redirect totals and other category totals are not always mutually exclusive. Adding all category counts may not equal the unique-destination count.
Source context#
Expand a whole-site destination to inspect source pages and link text. Open a source and find the actual reference before editing. The same URL can appear on several pages or in shared navigation.
Grouped results combine destinations while keeping source occurrences. These counts answer different questions: how many addresses need attention and how many references may need a fix.
- Find the destination in the relevant category.
- Inspect its original URL, final response and redirect trail.
- Expand source-page information.
- Open a source and confirm the reference.
- Repair and obtain a new scan.
Response time and content type#
Response time measures an individual scan request, not complete page loading for a visitor. Network conditions and request methods affect it. A missing measurement is not a zero-duration response.
Content type helps distinguish HTML from downloads or other resources. Open important files to confirm the expected document and version, even if their requests succeeded.
When a browser result differs#
A signed-in browser, a without-cookies scan and a HEAD request can receive different responses. Start with Automatic request mode and without cookies. For a suspected HEAD-handling problem, try a controlled GET-only check.
Keep uncertain findings as observations. Do not remove a useful reference solely because of a timeout or access response; establish whether intended readers can reach it.