Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

HTTP Status Code

The numeric code a web server returns with every response, saying whether the request succeeded, was redirected or failed and why.
SEOtechnologyUpdated

Definition

An HTTP status code is the numeric part of a server's response that tells the client, whether a browser or a crawler, what happened to its request. Codes are grouped into classes, and four of them matter in everyday marketing work:

  • Success. The request worked and the content follows. This is what every live, indexable page should return.
  • Redirection. The content lives at another address, given in the response. Permanent and temporary redirects are separate codes, and the difference changes how search engines treat the old URL.
  • Client errors. The request cannot be met as asked. Not found and gone are the two that matter most: the first says there is nothing here, the second that something was here and has been removed deliberately.
  • Server errors. The server failed, through a crash, an overload or a timeout. They say nothing about whether the page exists.

In practice: where marketers meet status codes

Status codes come up whenever URLs change or end. A site migration or a restructure needs every old URL mapped to a permanent redirect or a deliberate removal, which the redirect map template records row by row, with the code and the reason for any exception. Pages that are built to end, such as listings, events and job posts, need a code chosen for each outcome: the guide to expired pages keeps the code in step with the decision, success for kept pages, a permanent redirect for pages with a true equivalent, and not found or gone for removed ones.

Codes are also a release risk. A change to error handling can make missing pages return success and real pages return errors, so the SEO release checks request a set of sample URLs after each deployment and compare their codes with the expected ones. Platforms matter too: the guide to choosing a CMS for SEO asks for real status codes, so that a missing article returns not found rather than a success page announcing it has gone.

What search engines do with each class

The site's crawling and indexing guide summarises Google's documented behaviour. A successful page is fetched and considered for the index. A permanent redirect passes the old URL's signals to the destination, which is indexed instead; Google's page on redirects describes a permanent server-side redirect as a strong signal that the target should be canonical, and a temporary one as a weak signal that may keep the original indexed for a while. A not-found or gone page drops out of the index once the code is re-confirmed. Persistent server errors slow crawling and can eventually drop pages.

Because crawlers see codes that a quick browser check does not, server logs are the most complete record of what they received. The tutorial on log file analysis counts crawler requests by template and status, which is where spikes in errors, long redirect chains and requests to long-removed URLs show up.

Illustrative example — not a real result

A ticket site stops pretending past events exist

Kindlerow Event Tickets kept every past event page live, returning 200 with a short "this event is over" message. Search Console reported 1,260 of them as soft 404s, and the server logs showed crawlers spending about a third of their requests on ended events. The team set a rule by event type: recurring events now answer with a 301 to the page for the next date, and one-off events that will not return answer with a 410 and leave the sitemap and internal links. Three months later the soft 404 count had fallen to 40, and crawler requests to current events had roughly doubled.

A 301 Redirect is the permanent redirect code, the one used when a page moves for good. A Soft 404 is the mismatch this page warns about: a page that says it does not exist while its code says success. Returning a success code is one of the conditions of Indexability, and on large sites the codes crawlers receive shape Crawl Budget, since errors, redirect chains and soft errors all consume requests that could have gone to live pages.

Common confusions

  • Not found and gone are the same. Both remove a page, but gone states that the removal is deliberate.
  • Redirecting every dead page to the homepage is safe. A redirect to an unrelated page is treated like a soft not-found page, not a transfer of value.
  • A temporary redirect is fine for a permanent move. It is a weaker signal and may keep the old URL indexed for longer.
  • The page looks fine, so the code is fine. What a visitor sees and what the server answers can differ; only the response, or the logs, show the code.
  • Server errors mean the page is gone. They mean the server failed; repeated, they reduce crawling and can cost indexing until fixed.

More terms to look up

Where this term is used

Sources

  1. Redirects and Google Search — Google Search Central

Related