200 OK
The request succeeded, and the response holds whatever was asked for. By far the most common status code.
- Class
- 2xx Successful. The request was received, understood and accepted.
- Defined in
- RFC 9110
When a server sends it
For every request that went as intended and has something to return: the page or the file for a GET, the outcome of the action for a POST. A HEAD request gets the same headers without the body.
What to do with it
Nothing is wrong with the request. If the page still isn't what you expected, the fault is in the content.
That happens more often than it should. An error page or an "item not found" message that is sent with a 200 misleads every program that goes by the code: caches keep it, monitoring stays green, crawlers index it. If you build the site, send the status that matches what the page says.
Not to be confused with
| 204 No Content | Success as well, with nothing to send back. |
|---|---|
| 201 Created | Success that made something new. |
| 304 Not Modified | No body, because the copy the client already has is still good. |
How Google treats it
Google may index what it receives with a 200, though that is not guaranteed. A page that says "not found", or is empty, while returning 200 is reported in Search Console as a soft 404.
All codes are on the list of HTTP status codes, which can be searched by number and by word.