HTTP Status Codes
Look up what each status code means
All processing happens locally in your browser. Your data is never uploaded to a server.
Look up what each status code means
All processing happens locally in your browser. Your data is never uploaded to a server.
Informational: request received, still processing
Success: the request was handled
Redirection: further action is needed
Client error: the request is at fault
Server error: the server failed
The status code is the first thing a server returns and it decides how browsers and crawlers treat the response. For SEO, watch the 301 vs 302 distinction and how you serve 404 and 410.
Continue
Headers received; the client should continue with the body
Switching Protocols
Server agrees to switch protocols, typically to WebSocket
Early Hints
Sends hints early so the browser can preload resources
OK
Success — the body contains what was asked for
SEO note: Required for a page to be indexed
Created
Created a new resource, usually after a POST
Accepted
Accepted for processing, but not finished yet
No Content
Success with no response body
Partial Content
Returns part of the resource, used for range requests
Moved Permanently
Permanent redirect to a new location
SEO note: Passes ranking signals to the new URL — use it for real moves
Found
Temporary redirect; the old URL stays valid
SEO note: Crawlers keep the old URL indexed, so don't use it for permanent moves
See Other
Fetch another URL with GET, typical after a form post
Not Modified
Unchanged — use your cached copy
SEO note: More hits means less crawl budget spent
Temporary Redirect
Temporary redirect that preserves the HTTP method
Permanent Redirect
Permanent redirect that preserves the HTTP method
Bad Request
Malformed request — the server can't parse it
Unauthorized
Authentication required or invalid
Payment Required
Reserved for payment-gated resources; rarely used
Forbidden
Understood but refused — you lack permission
SEO note: Crawlers treat a 403 as content they may not have
Not Found
Nothing found at this URL
SEO note: URLs that stay 404 are dropped from the index
Method Not Allowed
This method isn't allowed on this URL
Request Timeout
The client took too long to send the request
Conflict
Conflicts with the current state of the resource
Gone
Permanently deleted and will not return
SEO note: Gets a page removed from the index faster than a 404
Payload Too Large
The request body exceeds the server's limit
Unsupported Media Type
The body's media type isn't supported
Unprocessable Content
Well-formed but semantically wrong, e.g. validation failed
Too Many Requests
Rate limited — too many requests
SEO note: Rate limiting crawlers by mistake cuts your crawl rate
Unavailable For Legal Reasons
Blocked for legal reasons
Client Closed Request
Client disconnected before the response (Nginx)
Internal Server Error
A generic server-side failure
SEO note: Sustained 500s visibly hurt rankings
Not Implemented
The server doesn't support this method
Bad Gateway
The gateway got an invalid upstream response
Service Unavailable
Temporarily unavailable — overloaded or in maintenance
SEO note: Use it with Retry-After during maintenance — safer than a 404
Gateway Timeout
The gateway timed out waiting upstream
HTTP Version Not Supported
The HTTP version used isn't supported
Web Server Is Down
The origin refused Cloudflare's connection
Connection Timed Out
Cloudflare could not reach the origin in time