<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DeveloperSide.NET Blog &#187; GoogleBot</title>
	<atom:link href="http://www.devside.net/blog/tag/googlebot/feed" rel="self" type="application/rss+xml" />
	<link>http://www.devside.net/blog</link>
	<description>Linux, Windows, MacOS? Who cares. Just give me something that works!</description>
	<lastBuildDate>Mon, 19 Sep 2011 20:58:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Googlebot Likes 404s</title>
		<link>http://www.devside.net/blog/googlebot-404</link>
		<comments>http://www.devside.net/blog/googlebot-404#comments</comments>
		<pubDate>Tue, 30 Jan 2007 04:17:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[GoogleBot]]></category>

		<guid isPermaLink="false">http://www.devside.net/blog/googlebot-404</guid>
		<description><![CDATA[I&#8217;ve been playing around with the Google Webmaster Tools and have noticed one thing on the site verification process, that is not present on the Diagnostics/Crawl Errors tab&#8230;

Last attempt [date]: We&#8217;ve detected that your 404 (file not found) error page returns a status of 200 (Success) in the header.
Google will be unable to verify your [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been playing around with the Google Webmaster Tools and have noticed one thing on the site verification process, that is not present on the Diagnostics/Crawl Errors tab&#8230;</p>
<blockquote><p>
Last attempt [date]: We&#8217;ve detected that your 404 (file not found) error page returns a status of 200 (Success) in the header.</p></blockquote>
<p>Google will be unable to verify your site [for this service] if it is setup in a way where all URLs that do not exist, redirect back to the main page. But more importantly, from the look of things, this also has an effect of receiving a penalty and/or keeping your site out of the Google index.</p>
<p>DynamicSide.NET was like that, and Enotarize.com was even worse, not redirecting back, but rather just displaying the main page on any and all URLs [what can I say, its a very simple site, pre-beta].</p>
<p>And I was wondering why I have not been seeing much traffic on those two from Google search.</p>
<p>With DynamicSide.NET, there seemed to be some type of a penalty [nothing under the webmaster tools, but I have a feeling something is going on]. And with Enotarize.com, it looked like it was not being indexed at all, for some time. I&#8217;m sure that also had/has an effect on DeveloperSide.NET, as I&#8217;m linking back to both sites.</p>
<p>On another note, content that did exist on your site at one point, that has been removed, <strong>should</strong> return HTTP Status code &#8216;410&#8242; &#8220;gone&#8221;, over the &#8216;404&#8242; &#8220;not-found&#8221;.</p>
<p>And what about a situation where content has moved URLs, yet there is no simple way for you to redirect&#8230; A good example of this situation is under our Forums, with the switch from phpBB to SMF. They both have non-compatible ways of associating URLs to posts and topics. Right now I&#8217;m just redirecting everything hitting the old phpBB &#8216;viewtopic.php&#8217; URLs to the main forum URL. Perhaps I should be using a &#8216;303&#8242; &#8220;see-other&#8221; code&#8230;</p>
<p><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html">Status Code Definitions</a><br />
<a href="http://www.google.com/support/webmasters/bin/answer.py?answer=35769">Webmaster Guidelines</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.devside.net/blog/googlebot-404/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

