How a status code works
Every request to a website gets two things back: a status code and, usually, some content. The code is a three-digit number the server sends before anything else, and it is the server’s summary of what just happened. Browsers act on it silently, which is why most people never see one until something breaks.
The first digit is the part worth learning, because it sorts every code into a family:
- 2xx — it worked. The page exists and here it is.
- 3xx — it moved. Go to this other address instead, either permanently or for now.
- 4xx — you asked for something wrong. The address does not exist, or you are not allowed to see it.
- 5xx — the server broke. The request may be fine; the server could not answer it.
Within each family the specific number narrows it down. In the 3xx family, a 301 says the move is permanent while a 302 says it is temporary, and search engines treat those two very differently.
Why status codes matter
Search engines decide what to do with a URL almost entirely on its code. A successful response gets read and considered for the index. A permanent redirect passes the old URL’s standing to the new one. A missing page eventually drops out. A server error, repeated, makes a crawler back off and try your site less often.
They also make debugging quick, because they separate problems that look identical to a visitor. A page that will not load might be missing, might be blocked, or might be a server that fell over. The code tells you which, and therefore who needs to fix it.
Common mistakes with status codes
The most damaging one is a page that says everything is fine when it is not. A shop that returns a friendly “product not found” screen with a success code has created a soft 404: search engines keep the URL, keep visiting it, and may index a page with nothing on it.
The second is checking codes in a browser. The browser follows redirects for you and shows you the destination, so a chain of hops looks like a single working page. Use a tool that reports the whole sequence.
The third is treating a server error as somebody else’s problem because the site came back. Intermittent 5xx responses during peak hours are a real signal, and they are common on cheap shared hosting.
How to act on it
Crawl the site and read the code for every URL, including the ones in your sitemap and the ones your menu links to. Redirects should go to a live page in one hop, missing pages should say they are missing, and successful pages should genuinely have content.
Then keep watching. Search Console reports what crawlers met on their last visit, and it is worth checking after every launch, migration or theme change — those are the moments when a working site quietly starts answering with the wrong number. Sorting that out is routine technical SEO work, and it is cheap compared with what a broken redirect map costs.
