A server response identifying the outcome of a request, such as success (200), redirection (301), or an error (404/500).
An HTTP status code is part of the response to a request. It reports an outcome such as a successful response, a redirect or an error. The code is separate from the visible wording of the page: a beautifully designed “not found” screen can still send the wrong status if the server reports success.
Common examples include 200 for a successful response, 301 for a permanent redirect and 404 when a resource is not found. Other codes describe different situations, so a developer should choose the response that matches what actually happened. The aim is accurate communication, not making every address return 200 to remove warnings from a report.
For search, a successful status permits further processing but does not guarantee indexing. Google can also recognize an apparent error page behind a successful response as a soft 404. Conversely, an intentionally removed URL may correctly return an error status. Interpreting the number requires the intended purpose of the URL and the actual response content.
Takeaway: Check both the response code and what the visitor receives. A status is diagnostic evidence, not a standalone quality score or proof that a page is visible in search.
Example
A bakery retires an old campaign landing page with no replacement. Its website displays “This offer has ended,” but the template returns the same success code as active pages. The developer reviews the intended handling rather than assuming the explanatory sentence has already communicated the removal to every system.
What to check
Use a browser network panel or a trusted response checker to inspect the exact URL. If it redirects, follow the full sequence and check the final destination. Record whether a reported problem affects a real published page, an intentionally removed resource or a malformed request.
For more detail, see Google HTTP response guidance.