SEO

Status Code

Also called HTTP status code, response code

The three-digit answer a server gives to every request, saying whether the page was found, moved, missing or broken.

Quick facts: Status Code

Category
SEO
Also called
HTTP status code, response code
Level
Beginner
Affects
Crawling, indexing, redirects, error reporting
Where to see it
Screaming Frog, Search Console URL Inspection, browser developer tools
In this article4
  1. How a status code works
  2. Why status codes matter
  3. Common mistakes with status codes
  4. How to act on it

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.

Do and do not

Do

  • Learn the four families before the individual numbers
  • Check codes with a crawler, not a browser
  • Re-check every code after a launch or migration

Do not

  • Serve a success code on a page that failed
  • Ignore server errors because the site came back
  • Assume a redirect reached its destination in one hop

Questions people ask about this

Which status codes should I actually worry about?

Three groups. Server errors in the 5xx family, because repeated ones make crawlers slow down and visitors leave. Redirect chains in the 3xx family, because each extra hop wastes crawling and slows the page. And pages that return success while showing an error message, because search engines have no way to know the content is worthless.

How do I check the status code of a page?

A browser is the wrong tool, because it quietly follows redirects and shows you the final page. Use a crawler such as Screaming Frog, the URL Inspection tool in Search Console, or the network tab in your browser's developer tools, where every hop and its code are listed in order.

Does a status code affect rankings directly?

Not as a scoring factor, but it decides what a search engine does with the URL, which amounts to the same thing. A successful response can be indexed and ranked, a permanent redirect passes the old page's standing on, a missing page eventually drops out, and repeated server errors reduce how often your site is crawled.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.