GitHubDownload ZIP
301 chain301 chain
Permanent redirects stacked one after another.
Found by Redirect checker →
302302
A temporary redirect on a page that moved for good.
Found by Redirect checker →
Technical SEOUpdated

HTTP status code

In short

An HTTP status code is a standardized server response that tells a client whether a request succeeded, redirected, failed or requires authentication.

Mechanism and decision

HTTP status codes report the outcome of one request: success (2xx), redirection (3xx), client error (4xx) or server error (5xx). A route can behave differently by method, host, protocol, authentication state or cache, so a code needs its exact request context.

Define a route contract: successful public pages return success, permanent moves redirect directly, absent content returns an honest missing response, and temporary outages are not disguised as permanent errors.

The diagram traces one request through a server to the 2xx, 3xx, 4xx and 5xx response families.

What you can control

A status describes a request outcome; it does not alone explain indexation, visibility or user satisfaction.

Practical workflow

  1. Request the intended host, protocol and method.
  2. Follow redirects and record every hop and Location header.
  3. Compare status with rendered content and index policy.
  4. Re-crawl representative routes after the rule change.

FAQ

Yes. The response status is independent of the design. A missing-page template returning 200 can be treated as a soft 404.
Check both the redirect status and Location header, then the final destination’s response.