Tweet
When it comes to server issues, many of us would rather not get into the down-and-dirty details. But knowing the basics of server response codes -- and when to use them correctly -- is critical for any competitive Webmaster or search marketer.
Every time a user or search engine spider visits a Web page, the server that page resides on returns a code. These codes show whether the page loaded correctly, was moved, or if there’s a problem. Understanding these Web server responses to user and search engine requests is a critical aspect of SEO and Web site usability. Relay the wrong response, and you could create a world of hurt for your Web site in the search engines, or have some dissatisfied users on your hands.
Basic Server Response Codes
There are many different response codes, many that you will most likely never have to worry about. But there are a few that will keep coming up, which have the potential to make your life easier or more difficult. Here are the definitions of the basic server response codes.
200 — OK. The request has succeeded.
301 — Moved Permanently.
302 — Found.
404 — Not Found.
For more information and definitions on server response, check out the status code definitions on the W3.orgsite.
Common Pitfalls
Below are some of the common pitfalls in using server response codes, as this relates to search engine optimization:
Using 302 temporary redirects when the change is permanent.
Custom 404 pages resolving to a 200 OK server response.
Sometimes, the search engines aren’t as good as advertised in following redirects.
Canonical issues.
Every time a user or search engine spider visits a Web page, the server that page resides on returns a code. These codes show whether the page loaded correctly, was moved, or if there’s a problem. Understanding these Web server responses to user and search engine requests is a critical aspect of SEO and Web site usability. Relay the wrong response, and you could create a world of hurt for your Web site in the search engines, or have some dissatisfied users on your hands.
Basic Server Response Codes
There are many different response codes, many that you will most likely never have to worry about. But there are a few that will keep coming up, which have the potential to make your life easier or more difficult. Here are the definitions of the basic server response codes.
200 — OK. The request has succeeded.
301 — Moved Permanently.
302 — Found.
404 — Not Found.
For more information and definitions on server response, check out the status code definitions on the W3.orgsite.
Common Pitfalls
Below are some of the common pitfalls in using server response codes, as this relates to search engine optimization:
Using 302 temporary redirects when the change is permanent.
Custom 404 pages resolving to a 200 OK server response.
Sometimes, the search engines aren’t as good as advertised in following redirects.
Canonical issues.
Comment