As we all know that 2xx, 3xx, 4xx, and 5xx errors have been playing a major role in SEO, and SERPs yesterday google just tweeted about the impact on your SEO work that could lead to new errors and coverage issues in your webmaster.
A recent tweet suggests Google’s Gary Illyes had a hand in putting this document together and all issues mentioned on this page generate a corresponding error or warning in Search Console’s Crawl Stats report. Much of this may be familiar to you already, but it couldn’t hurt to refresh your knowledge of status codes with the most recently available information.
How HTTP status codes and DNS errors affect Google Search
Google’s new document covers the top 20 status codes that Googlebot encounters on the web, and the most prominent network and DNS errors.
HTTP status codes are generated by the server hosting a site when content is requested by a browser or crawler.
For example, if a browser requests content that’s no longer hosted on the server, then a 404 (page not found) status code will be generated.
The first number of the status code indicates what category it belongs to.
All 2xx codes refer to successful crawling.
All 3xx codes refer to redirects, and so on.
While there are many changes we can have the basics of all the codes and get the knowledge of the same from each category necessary from an SEO point of view.
HTTP 2xx (success)
These codes mean Googlebot can crawl the content and pass it on to the indexing pipeline. Google makes a point of noting that an HTTP 2xx status code doesn’t guarantee to index, it simply means there were no errors encountered.
The exception is a 204(no Content) status code, which means the page was successfully accessed but no content was found.
Google may show a soft 404 in Search Console for pages serving a 204 code.
HTTP 3xx (redirects)
Not all redirects are equal.
An HTTP 301(moved permanently) status code sends a stronger signal than a 302 (found), 303(see other), or 307(Temporary redirect – Equivalent to 302) code in terms of which URL should be considered canonical.
A 304 status code signals to Google that the content is the same as last time it was crawled. It has no effect on indexing, but may cause the signals for the URL to be recalculated.
What happens if the redirect doesn’t work?
Googlebot follows up to 10 redirect hops before it stops trying.
If the content isn’t received within 10 hops, Search Console will show a redirect error in the site’s Index Coverage report.
HTTP 4xx (client errors)
Pages that return a 4xx status code are not considered for indexing in Google’s search results.
All 4xx errors, except 429, are treated the same. They signal to Googlebot that the content doesn’t exist. If the content previously existed, the URL will be removed from Google’s search index.
A 429 status code means Googlebot couldn’t access a URL because the server is overloaded. Those URLs will be preserved in Google’s index.
HTTP 5xx (server errors)
5xx server errors prompt Googlebot to temporarily slow down with crawling.
Previously indexed URLs which now have a server error will eventually be dropped if they continue to serve a 5xx status code.
For more detail about these server errors, and information on DNS and server errors, see the full Google help document.
Hope you liked the content share it with your community to support the excitement to get new content every week.
