A page's response is part of its behaviour

A browser asks a server for a resource, and the server returns a response status with the content. A successful response commonly uses 200. A missing resource commonly uses 404. A redirect uses a redirect status and a destination. These observations describe what happened during one request; they are not a complete explanation of why it happened.

A friendly error screen can be helpful, but its appearance does not prove the server sent the correct status. If a nonexistent address returns a normal success response containing an error message, a crawler may receive a misleading signal. Check the response directly as well as looking at the rendered page.

Investigate a failed destination

Record the source page, the link label, the requested address, and the observed status. Retry cautiously if the failure may be transient. If the address is genuinely obsolete, identify the intended replacement from site knowledge rather than guessing that every missing page should lead to the home page.

A useful repair may be to update a link, restore an accidentally removed resource, or explain that the information is no longer available. Redirecting an unrelated page can frustrate readers. Preserve the reason for the change so someone reviewing it later can understand the intended connection.

Try a response check

The example destination below lets you compare the address you requested with the response you receive. Use browser developer tools or an HTTP client to inspect it. The site deliberately includes imperfect examples, so treat the result as an observation to record.