Forum Moderators: open

Message Too Old, No Replies

Server Response 206

Could this be affecting search engines ability to grab page?

         

bears5122

6:21 pm on Oct 13, 2005 (gmt 0)

10+ Year Member



Over the past week or two we've noticed a site have its homepage de-listed in MSN, as well as lose its cache in Yahoo and Google. Barring the unlikely coincidence that all 3 search engines have penalized the homepage of a perfectly clean site, I'm thinking of a technical problem that could be causing this.

The only thing I've seen is when going to #*$!, it returns a 206 response code. Most sites return 200. Is there any reason for this and would it have an effect on the search engines ability to pull the content from a page? I'm lost at why they all seem to have problems picking up this page.

pageoneresults

7:31 pm on Oct 13, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



it returns a 206 response code. Most sites return 200. Is there any reason for this and would it have an effect on the search engines ability to pull the content from a page?

Hmmm, I've done a lot of server header checking over the years and can't say I've ever seen a 206 response code returned. Do you know why the server is returning a 206 instead of a 200?

Status Code Definitions [w3.org]

10.2.7 206 Partial Content
The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.

bears5122

7:54 pm on Oct 13, 2005 (gmt 0)

10+ Year Member



Running a server header check I get a 200 code. However, using a whois lookup I get 206. I'm grasping at straws here but I'm trying to find any technical glitch that could be causing this.

pageoneresults

8:07 pm on Oct 13, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



However, using a whois lookup I get 206.

Are you getting that response with other Whois tools?

The server has fulfilled the partial GET request for the resource.

A Whois tool may be performing the partial GET request hence the reason for the 206.