How it works
Distinguish success, redirects, client errors and server errors; the code should match the displayed content.
Example
Example: A missing article returns 404; an existing accessible article usually returns 200.
Common mistakes
An error page's design does not determine its HTTP status.
How can you check this in practice?
Inspect the actual document status in the browser Network panel or an HTTP client. 2xx indicates success, 3xx another destination, 4xx a resource or request issue, and 5xx a server issue. Visual design does not replace this check.
Distinctions and limitations
Status describes an HTTP response, not text quality. A polished error message returning 200 can be a soft 404; a 301 without a suitable destination does not restore missing information either.
Official sources
Editorial responsibility: Martin Zhelyazkov · Founder of Z-Consult
Updated: 05/11/2026
For a correction or question: office@z-consult.bg