What are Status Codes?
HTTP status codes are responses from a server to a request made by a user, browser, or search engine bot. When a server delivers a status code, it comes in the form of 3-digit response status code.
The response status code defines the state of a webpage when a URL is pinged and provides search engines supplemental information around the webpage, which may impact a page’s SEO. Response codes guide how search engines rank web pages within organic search and how users interact with web pages.
Common Status Codes
- 1xx’s Informational Response: the request was received and is continuing to process
- 2xx’s Success: the request was successfully received by the server
- 3xx’s Redirection: the request resulted in a redirect and you’re being taken elsewhere
- 4xx’s Client Error: the request for the page was invalid and resulted in an error; that is a requested page doesn’t exist
- 5xx’s Server Error: the server failed to fulfill the request
Most Significant Status Codes for SEO
HTTP Status Code 200 – OK
This status code is the most ideal response from your server. It tells both search engines and users that a webpage was found and the request is valid. Upon retrieving the webpage, search authority can be passed on to 200 OK Status Code URLs.
HTTP Status Code 301 – Moved Permanently
When a location has permanently changed to a new URL, a 301 Moved Permanently status code should be implemented. As URLs accrued search authority / equity, you’ll want to pass on that equity to its new location. A 301 status code tells search engines that because a location has moved permanently, all search authority should be transferred to its new location. This status code is predominantly used during page transitions and redirect mapping.
HTTP Status Code 302 – Moved Temporarily
Similar to a 301 Moved Permanently status code, a 302 status code tells search engines that a location has moved. However, a 302 status code tells search engines that a location has moved temporarily. This impacts the manner in which search engine authority or link juice is passed. A temporary redirect doesn’t transfer all search engine equity to its location as the search engine is told the redirect is temporary.
HTTP Status Code 404 – Not Found
The 404 Not Found status code tells search engines that the server couldn’t recognize the request, which resulted in an 404 error. You can test this by creating a fake URL on your website and trying to access. Because the location doesn’t exist, the server will not be able to fulfill the request and responds with a 404 Not Found status code.
To resolve this issue, you have to understand what is being requested, whether there was user error or a page is no longer available, and what should be done (should a 404 page be created, should a redirect be implemented, should a page be fixed?).
HTTP Status Code 410 – Gone
A 410 Gone status code is more permanent than a 404 Not Found status code. It tells search engines that a webpage is no longer available from a server. Search engine authority to any webpage that has a 410 status code is nulled and no longer supports a site.
HTTP Status Code 500 – Internal Server Error
Instead of an issue with the webpage, a 500 Internal Server error is an issue with the server. If the 500 status code continues, there could be detrimental effects to organic search performance.
HTTP Status Code 503 – Service Unavailable
A 503 Service Unavailable error is an issue with the server. If a server is either overwhelmed or offline, a 503 status code tells search engines and bots that there has been an issue. Similar to 500 status codes, if the 503 status code continues, there could be detrimental effects to organic search performance.
How to identify Status Codes
Web Crawler: Screaming Frog
My preferred way to identify status codes in bulk is with the use of a web crawler. The web crawler I recommend is Screaming Frog as it offers a robust suite of features that identify SEO elements on any given webpage, including status codes.
Below is a screenshot of how Screaming Frog identifies a status code for a post I recently redirected.
Chrome Extension: Redirect Path
If you’re reviewing URLs individually on a browser, it might be more efficient to review a status code as a page is being loaded.
I use Google Chrome as my primary browser and, with it, I use the Redirect Path Chrome extension to review a page’s status code.
Once installed, it pings a webpage and retrieves its status code. Below is a screenshot of how the extension depicts the redirect path of the URL example I used above.
HTTP Headers: Chrome DevTools
Another way to review a web page’s status code is by reviewing its HTTP header.
If you’re using Google Chrome, you can use DevTools to review a web page’s Network Activity.
This Google Chrome feature logs activity between a browser and a server. As such, it is also able to retrieve status code information for a web page.
Below is a screenshot of how you’d be able to find the status code via Network Activity
Summary
HTTP status codes might be overwhelming at first but as you become more familiar with their significance, you’ll find it becomes increasingly easier to work with and identify.
Because a website’s work is never done, as you continue to build out your site, you might find that reviewing and fixing non-200 status code pages becomes a standard practice in your optimizations.
