The request sent by the client, browser or robot was received correctly, can be understood by the server and accepted by it.<\/p>\n
Types of 200 codes<\/h2>\n\n
![\"Thumbs](\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/200ok-http-code.jpg\")
<\/p>\n
As with all server-specific response codes, the first digit specifies the type of response. With the number 2, it identifies that we are in front of a correct request response.<\/p>\n
Within the 200 codes, there are several types depending on the server’s response to the correct request:<\/p>\n
200 code: OK<\/h3>\n
When the server responds to a successful request by returning the page requested on the web, we say that we are dealing with a 200 ok response code.<\/p>\n
The user will be seeing the page he requested without any problems and for SEO we will have a correct behavior between the client and the server.<\/p>\n
201 code: Created<\/h3>\n
It occurs when, upon a request by the client, spider or browser, the server correctly processes the request and creates a new resource.<\/p>\n
202 code: Accepted<\/h3>\n
We obtain a code 202 with a successful response when the server accepts the request, pending its processing. The request is accepted for processing but processing has not been completed.<\/p>\n
These are the cases in which the petition may not be resolved because it may find as a reason for not processing it that it was not permitted or was prohibited when the processing took place. We will also see it when the server receives a complex request and does not want to spend hours waiting for a response.<\/p>\n
203 code: Non authoritative information<\/h3>\n
We found this code 203 when the server receives the request correctly from the client, it accepts it and serves that information but it does it from another source, from another server.<\/p>\n
204 code: No content<\/h3>\n
We will have a server response code 204 when the server accepts and processes the client’s request, but it does not have the content. It may even contain in the response the HTTP header, but not the content of the page itself.<\/p>\n
205 code: Reset content<\/h3>\n
When the server accepts the request but does not have the content because the client has reset the view, 205 code occurs, with a content reload message. The browser has to re-initialize the page from which the request was made.<\/p>\n
We find the forms as an example in this respect, when the data is filled in and must be deleted once it has been sent. In this case, when sending, the page is reloaded and retrieved without this data.<\/p>\n
206 code: Partial content<\/h3>\n
The server receives and correctly processes the client’s request, but can only provide part of the requested content, as requested by the client, browser or bot. We see it when the content of the page is requested partially, for example when we ask it to show us the content without JavaScript, where it will show partially the same without the part we do not want to receive.<\/p>\n
207 code: Multi-Status<\/em><\/h3>\nIt is the response code provided by the server when its response to the received request consists of an .XLM file in which different different responses are specified. The file will contain as many responses as requests made by the client.<\/p>\n
208 code: Already Reported<\/em><\/h3>\nWe are talking about DAV elements, this response code is produced when the listing has already been notified so they are going to be listed again.<\/p>\n\n\n
We are talking about DAV elements, this response code is produced when the listing has already been notified so they are going to be listed again.<\/p>\n\n
![\"\"](\"https:\/\/www.humanlevel.com\/wp-content\/uploads\/HL20-SEO-1-e1770805082974.png\" "\\"HL20-SEO\\"")
\n<\/section>\n\n","protected":false},"excerpt":{"rendered":"