What HTTP Status Codes Mean and Which Ones Matter
A reader emailed me in September because his hosting support had replied to a ticket with the sentence "the origin is returning a 502, please check your application." He had no idea what that meant and neither did the person who built the...

A reader emailed me in September because his hosting support had replied to a ticket with the sentence "the origin is returning a 502, please check your application." He had no idea what that meant and neither did the person who built the site for him. His shop had been down for eleven hours while the two of them traded emails.
That number was the most useful thing in the whole exchange. HTTP status codes are the short answer a server gives to every single request, and once you can read the common ones you stop guessing about whether a problem is your pages, your host, or something in between. There are 63 of them defined. You need about ten.
Where the number comes from and how to see it
Every time a browser asks for something, a page, an image, a font, the server answers with a three digit number before it sends any content. The browser usually hides it. If the number is 200 you see the page and never think about it. If it is 404 you see whatever error page the site has, and the number sits quietly behind that.
Three ways to read it yourself, in order of how often I use them:
Open your browser developer tools with F12, click the Network tab, reload the page. Every request appears in a list with its status in a column. This is the fastest way to find the one broken image on a page that otherwise looks fine.
For a single URL, a free online header checker will show you the code and any redirects it passed through. Useful because it sees your site the way a visitor with an empty cache does, not the way your own browser does after fifty visits.
From a terminal, curl -I followed by the address prints the headers alone. I keep this one for checking a site before the DNS has fully moved.
The five families, in one sentence each
Codes are grouped by their first digit, and knowing the group is often enough to know whose problem it is.
1xx means the server is still thinking and has sent a note to say so. You will almost never see one. 2xx means success. 3xx means the thing has moved and here is where to. 4xx means the request itself was wrong, which usually points at your pages or your links. 5xx means the request was fine but the server failed, which usually points at your host or your application.
That last distinction is the one worth internalising. A page of 404s is a content problem and you can fix it this afternoon. A page of 500s is an infrastructure problem and no amount of editing your text will help.
The ten codes that come up on small sites
| Code | Name | What it usually means on your site |
|---|---|---|
| 200 | OK | Normal. The page exists and was sent. |
| 301 | Moved permanently | You changed a URL and set up a redirect. Search engines pass the old page's ranking signals along. |
| 302 | Found | A temporary move. Often used by mistake where a 301 was meant. |
| 304 | Not modified | The visitor already has this file cached and nothing changed. A good sign, not an error. |
| 403 | Forbidden | The file is there but something refuses access. Usually file permissions or a security plugin. |
| 404 | Not found | Nothing at that address. Most of these are harmless. |
| 410 | Gone | Deleted on purpose and never coming back. Stronger than a 404. |
| 429 | Too many requests | Rate limiting. A plugin, a bot or your own monitoring hitting too hard. |
| 500 | Internal server error | Your application broke. On WordPress, usually a plugin or theme conflict. |
| 502 and 504 | Bad gateway, gateway timeout | Something in front of your server could not get an answer from it in time. |
The two in the last row are the pair that caused that eleven hour outage. A 502 or 504 nearly always means a proxy or a CDN asked your actual server for the page and either got nonsense back or got nothing within the timeout, commonly 30 or 60 seconds. On shared hosting it often means PHP workers are exhausted. That is a host side conversation, and quoting the exact code gets you a faster answer than describing the symptom.
One more worth knowing because it is not standard: 503, service unavailable. This is the correct code to serve during planned maintenance, ideally with a Retry-After header saying how long. Search engines treat a short 503 as "come back later" and leave your rankings alone. A maintenance page served as a 200 tells them your real content has been replaced by the words "back soon", which is worse.
The advice I would push back on
Every SEO tool will hand you a list of 404s and imply that each one is damage waiting to be repaired. People then spend an evening creating redirects for all of them, usually pointing everything at the homepage because there is no obvious match.
That is the one move I would actively avoid. Redirecting an unrelated old address to your homepage produces what Google calls a soft 404: the response says 200 but the content has nothing to do with what was asked for. The page gets dropped from the index anyway, and now you also have a redirect rule nobody will remember in a year.
A 404 is a correct, honest answer to a request for something that does not exist. Mine come almost entirely from two sources: scanners probing for /wp-login.php on a site that does not run WordPress, and a typo somebody made in a forum post in 2021. Neither deserves my time.
The 404s that do matter are the ones your own pages link to, because those are visitors hitting a dead end inside your site. Those are worth finding and fixing properly, which is a different job from bulk redirecting, and our guide on finding and fixing broken links covers how to separate the two. When a page genuinely has moved, the method in our notes on setting up 301 redirects is the right answer, one URL to one sensible destination.
Reading codes when something is actually wrong
Here is the sequence I run when a site misbehaves, and it takes about four minutes.
Check the homepage first with a header checker. If it answers 200, the server is alive and the problem is narrower than you feared. If it answers 5xx, stop investigating your content and look at the host.
Then open developer tools on the broken page and scan the Network tab for any status that is not 200 or 304. Broken layouts almost always come from a stylesheet or script returning 404 after a file was moved or renamed. Broken images the same.
If you see a long chain in the 3xx column, two or three redirects to reach one page, flatten it. Each hop costs real time, usually 100 to 300 milliseconds on mobile, and chains have a habit of turning into loops after the next change.
If you see 403 on files that used to work, suspect permissions or a security plugin before anything else. A WordPress firewall blocking its own admin AJAX endpoint is a classic, and the symptom is features that silently do nothing.
Lastly, do not rely on noticing codes by hand. A free monitor checking your homepage every five minutes will tell you about a 500 before a customer does, and setting one up takes about ten minutes following our walkthrough on free uptime monitoring for a small website.
FAQ
Are 404 errors bad for SEO?
Not in themselves. Google has said repeatedly that 404s are a normal part of the web and do not drag down the rest of a site. The cost is a visitor who reached a dead end, so the ones linked from your own pages are the ones to fix.
What is the difference between a 301 and a 302?
A 301 says the move is permanent and search engines should transfer ranking signals to the new address. A 302 says it is temporary and the old URL should stay indexed. Use 301 unless you genuinely plan to move the page back.
Why does my site show 200 for a page that says not found?
Because the error message is being served as ordinary content. That is a soft 404, and it happens with some page builders and badly configured redirects. The fix is to make the server return a real 404 or 410 for those addresses.
Should I worry about 304 responses in my logs?
No, they are a sign caching is working. A 304 means the visitor's browser already had the file and the server confirmed it had not changed, which saves bandwidth and loads faster than sending it again.
More in Web Basics
Web Basics
What Website Bandwidth Limits Actually Mean for You
Your host emails to say you have used 82 percent of your monthly bandwidth, and it is only the 14th.
What Is a Favicon and How to Add One to Your Website
Your website looks finished, but in the browser tab it still shows a blank grey page icon, or worse, the logo of the website...
Web Basics
What Is a CDN and Does Your Small Website Need One
Your site loads quickly when you test it at home, but a visitor on the other side of the world says it takes four or five...