Website ownership
What is an HTTP status code?
An HTTP status code is a three-digit number in a server's response that describes the outcome of a request. It can indicate success, a redirect or an error, independently of the words and design shown on the page.
By Plainview WebReviewed
The meaning
When a browser requests a page, the server returns a response with a status code and, often, content to display. A 200 response means the request succeeded. A 301 tells the browser that the resource has moved permanently. A 404 means the requested resource was not found; the code alone does not say whether that absence is permanent. A 503 means the service is temporarily unable to handle the request.
A single page visit can involve many requests: the page itself, images, fonts and other resources. Each has its own response. When someone reports a problem, identify which request failed rather than assuming one number describes everything visible in the browser.
An example
Example: moving a fictional repair guide
GET https://example.com/repair-notes
→ 301, pointing to /guides/book-repair
GET https://example.com/guides/book-repair
→ 200, with the replacement guide
GET https://example.com/no-such-guide
→ 404, with a helpful not-found pageThis fictional publisher moves a guide to a clearer address. The old address redirects, and the replacement returns the guide. Both responses matter: checking only the final page's 200 status would miss whether the old address has the intended redirect.
A separate nonexistent address returns 404 and a page offering navigation back to useful content. Those helpful links do not change the meaning of its status. These are illustrative responses, not measurements of a live example.com website.
When it matters
Status codes help distinguish a missing page, an intended move and a temporary service problem. During a launch or URL change, check the original address, any redirects and the destination. For routine troubleshooting, record the address, response and time of the check so the maintainer can investigate the right request.
A browser's network panel or an HTTP inspection tool can show the response status. Confirm which request you are reading and whether the tool followed redirects automatically. Then inspect the actual page: a successful response alone does not verify correct content, working forms or search indexing.
A common confusion
A page that says “not found” may still return 200
The visible error message and the server's status are separate. If a missing page returns a success code, Google may classify it as a soft 404. Equally, a correctly designed error page can return a genuine 404. Ask the maintainer to check the response as well as the page's appearance.