HTTP Status Codes Reference

Look up a status code to see what it means, when servers send it and, for the ones that matter for SEO, how search engines treat it.

  • Free, no account needed
  • Runs in your browser: nothing you enter is sent to us
  • Updated November 19, 2026
42

1xx · Informational

100 Continue

The server received the request headers; the client can send the body.

101 Switching Protocols

The server agrees to switch protocols, for example to WebSocket.

103 Early Hints

Preliminary headers (often preload links) sent before the final response.

2xx · Success

200 OK

The request succeeded and the response contains the result.

Search engines: The normal status for a page that should be indexed.

201 Created

The request created a new resource, usually after a POST.

202 Accepted

The request was accepted for processing, which has not finished yet.

204 No Content

Success, with nothing to return.

Search engines: A page returning 204 has no content to index.

206 Partial Content

Part of a resource was returned, for a range request (video, resumable downloads).

3xx · Redirection

301 Moved Permanently

The resource has a new permanent address, given in the Location header.

Search engines: The standard redirect when a page moves for good: search engines treat it as a strong signal to index the new address.

302 Found

The resource is temporarily at another address.

Search engines: Use for temporary moves. If a 302 stays in place a long time, search engines may treat it like a permanent redirect.

303 See Other

The client should fetch another address with GET, typically after a form submission.

304 Not Modified

The cached copy is still valid; nothing new is sent.

Search engines: Normal for repeat crawls; it saves crawl bandwidth.

307 Temporary Redirect

Like 302, but the request method and body must not change.

Search engines: Treated as a temporary redirect.

308 Permanent Redirect

Like 301, but the request method and body must not change.

Search engines: Treated as a permanent redirect, like 301.

4xx · Client error

400 Bad Request

The server cannot process the request because it is malformed.

401 Unauthorized

Authentication is required (despite the name, it means "not authenticated").

Search engines: Pages behind a login return 401 or 403 and are not indexed.

403 Forbidden

The server understood the request but refuses it.

Search engines: Not indexed. Accidental 403s on public pages (firewalls, bot protection) can remove pages from search.

404 Not Found

Nothing exists at this address.

Search engines: Normal for deleted pages. Search engines drop 404 URLs from the index over time; they do not harm the rest of the site.

405 Method Not Allowed

The address exists but does not accept this method (for example POST).

406 Not Acceptable

No representation matches the Accept headers the client sent.

408 Request Timeout

The client took too long to send the request.

409 Conflict

The request conflicts with the current state of the resource.

410 Gone

The resource was removed on purpose and will not come back.

Search engines: A clearer "removed for good" than 404; pages may drop out of the index slightly faster.

411 Length Required

The request must state its Content-Length.

413 Content Too Large

The request body is larger than the server accepts (for example an upload).

414 URI Too Long

The address is longer than the server can handle.

415 Unsupported Media Type

The request body is in a format the server does not accept.

418 I'm a teapot

An April Fools' joke from RFC 2324, reserved but not used for real responses.

422 Unprocessable Content

The request is well-formed but its content is invalid (validation errors).

425 Too Early

The server will not risk processing a request that might be replayed.

428 Precondition Required

The server requires a conditional request to avoid lost updates.

429 Too Many Requests

The client sent too many requests in a given time (rate limiting).

Search engines: If crawlers get 429 often, they slow down crawling. Persistent 429s can lead to pages being dropped.

431 Request Header Fields Too Large

The request headers (often cookies) are too large.

451 Unavailable For Legal Reasons

The resource is blocked for legal reasons (RFC 7725).

499 Client Closed Request (non-standard)

Used by some servers (nginx) when the client disconnected before the response.

5xx · Server error

500 Internal Server Error

Something went wrong on the server and it has no more specific code.

Search engines: Repeated 5xx errors make crawlers slow down and can remove pages from the index if they last.

501 Not Implemented

The server does not support the functionality required.

502 Bad Gateway

A proxy or gateway got an invalid response from the server behind it.

Search engines: Treated like other 5xx errors: temporary, but harmful if it lasts.

503 Service Unavailable

The server is temporarily overloaded or down for maintenance.

Search engines: The right code for planned maintenance, ideally with a Retry-After header. Crawlers come back later; long outages can still cause drops.

504 Gateway Timeout

A proxy or gateway did not get a response in time from the server behind it.

505 HTTP Version Not Supported

The server does not support the HTTP version used.

511 Network Authentication Required

You must log in to the network first (captive portals in hotels, airports).

How to use this tool

  1. Type a code or a word (for example "redirect" or 404).
  2. Open a code to read the details.

How it works

Definitions follow RFC 9110 (HTTP Semantics) and the IANA HTTP Status Code Registry. SEO notes describe how major search engines publicly document their handling of redirects and errors.

Limitations

  • Some services use non-standard codes (for example 499 or 520–527 at certain CDNs); those are noted as non-standard where listed.