Forum Moderators: open
[google.com...]
Just a few tips. :)
Other than that, I might guess that somewhere, there is a 302 pointed towards your site...which might account for the title, etc.
The thing that makes me think it's a glitch on their end, is the http response code stuff in many of the pages in their cache that have the 302 title...seems to be a bug, because that header info normally wouldn't be part of a web page.
Status: HTTP/1.0 302 Moved temporarily
Location: [somwhereelse.net...]
The examples that are listed at google return "302 Found". This is the first mistake. The second error is every additional information that comes after the location line. They all have additional header fields like content-type and content-length. Google reads behind the loaction line and if it finds somethin more, it thinks, it's a normal page ... not a redirect. This seems to be buggy but it is the RFC standard how headers should look like.
The request, as in this example, would be fore 'http*//www.some-site.com/' and then, the server gives back a 302 for the site, with the new location being http*//www.some-other-site.com/
HTTP/1.1 302 Found
Date: Fri, 22 Nov 2002 19:07:38 GMT
Server: Apache/1.3.26 (Unix) PHP/4.2.2 Chili!Soft-ASP/3.6.2 FrontPage/5.0.2.2510
Location: http*//www.some-other-site.com/
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
131
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="http://www.some-other-site.com">here</A>.<P>
<HR>
<ADDRESS>Apache/1.3.26 Server at www.some-site.com Port 80</ADDRESS>
</BODY></HTML>
One of the first ones I see in Google work for a web browser (such as IE) but they are malformed, with two meta tags above the http response code.
So it is a malformed web server - in the case of one site I found.
However, another site I saw listed in that same result set on Google did have the correct http response code formatting so it is either a misconfigured web server, or Google's mistake. :)
Check your header with the tool over at Search Engine World [searchengineworld.com] and you should be able to see if it's right or if it was indeed Google's mistake.
Cheers.
