What Do HTTP Status Codes Mean? The Quick Map

An HTTP status code is a three-digit number your web server sends back with every request. It tells the browser whether the request worked and, if not, whose side the problem is on. The first digit sets the class: 1xx informational, 2xx success like 200 OK, 3xx redirection like 301, 4xx client errors like 404, and 5xx server errors like 500. Read the first digit first.

What is an HTTP status code?

An HTTP status code is the server's one-line verdict on a request, sent in the first line of the response, the status line, before any page content arrives. Every image, script, and page load gets one, even when you never see it.

You only notice a code when something breaks and the browser shows it, like a 404 or a 500. The rest of the time a silent 200 means the request succeeded and the page loaded normally.

MDN groups the codes into five classes by their first digit. That first digit is the fastest read, because it tells you whether to look at a redirect, the browser's side of the request, or the server itself.

The five classes, by first digit

The five classes sort every response by where things stand: still processing, succeeded, redirected, client error, or server error. The first digit alone places any code you meet.

Class	Meaning	Common example
1xx	Informational, request received, still processing	100 Continue
2xx	Success, the request worked	200 OK
3xx	Redirection, go elsewhere or use a cached copy	301 Moved Permanently
4xx	Client error, the request was faulty	404 Not Found, 403 Forbidden
5xx	Server error, the server could not complete a valid request	500, 503

Source: HTTP status code classes, MDN, retrieved September 2026.

The 4xx versus 5xx split is the one that matters most in a crisis. A 4xx says the request was wrong, a missing URL or a blocked visitor. A 5xx says the server itself failed while trying to answer.

Which codes should a business owner recognize?

A handful of codes cover almost everything you meet running a website. Knowing these five saves a panicked phone call.

• 200 OK: the page loaded normally. Nothing to do.
• 301 Moved Permanently: a permanent redirect, used when a URL changes for good, so Google treats the new address as the one to show.
• 404 Not Found: the page is missing, a wrong or deleted URL. Harmless in small numbers.
• 403 Forbidden: the server refused access, usually a permissions or blocking issue rather than a missing page.
• 500 and 503: a server fault or a server that is temporarily overloaded or down.

A single 404 is nothing to worry about. A page that should exist returning 404, or any page returning 500, is a live problem. The first thing we check when a client's site misbehaves is the status code. The first digit alone tells us whether to look at the URL, the redirect, or the server.

How do you check your site's status codes?

You check status codes in three places, from easiest to most technical: Google Search Console, your browser's developer tools, and a direct request. Each shows the same codes from a different angle.

Google Search Console reports codes across your whole site and flags pages that return 404 or server errors, so you can fix them before they cost rankings. It is the view that matters most for SEO.

Your browser's developer tools, under the Network tab, show the code for every file on the page you are viewing. For a single URL, a command-line tool like curl or an online HTTP header checker returns just the status line.

Frequently asked questions

What is the most common HTTP status code?

200 OK is the most common, returned every time a page or file loads successfully. You never see it, because nothing breaks. The codes people notice, like 404 or 500, are the exceptions, not the rule. A healthy site answers almost every request with a quiet 200.

Does an HTTP status code affect SEO?

Yes, some codes affect SEO directly. Google's crawling documentation treats a 301 as a strong signal that the new URL should replace the old one. A 404 removes a page from the index if it was indexed, and repeated 5xx server errors make Google slow its crawling and eventually drop pages. A 200 is neutral and expected. Google reads these codes to decide what to keep in its index.

What is the difference between a 4xx and a 5xx error?

A 4xx is a client-side error, meaning the request was faulty, like a missing URL (404) or a blocked visitor (403). A 5xx is a server-side error, meaning the server failed while trying to respond, like a crash (500) or an overload (503). MDN defines the 4xx range as client errors and the 5xx range as server errors, so the first digit tells you which side to fix.

What does a 200 status code mean?

200 OK means the request succeeded and the server returned the page or file as expected. It is the code behind every normal page load, sent silently in the status line. You will not see it on screen, because a 200 is exactly what the browser wanted, so it simply shows the page.

Where can I see the status code for a page?

Open your browser's developer tools, go to the Network tab, and reload the page; each file lists its status code. For your whole site at once, Google Search Console reports codes and flags errors. For a single URL, an online HTTP header checker or the curl command returns the status line directly.

Reading the code before you panic

Storming Solutions builds custom-coded websites for Malaysian businesses from Kuala Lumpur, maintains existing sites, and runs SEO, AEO, and GEO. Reading a status code correctly is the difference between a five-minute fix and a wasted afternoon. We would rather a client read the first digit than assume every red screen means the site is gone.

Seeing an error code you do not recognize? Send us the URL on WhatsApp for a quick read, or talk to us about web development.