<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Webmaster Central has Problems with 301&#8217;s to a New Domain</title>
	<atom:link href="http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/</link>
	<description>Michael Gray rants on SEO the internet and  media</description>
	<lastBuildDate>Sun, 25 Oct 2009 18:58:50 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Vanessa Fox</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58517</link>
		<dc:creator>Vanessa Fox</dc:creator>
		<pubDate>Mon, 03 Sep 2007 16:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58517</guid>
		<description>This is really a matter of incorrect wording of the error message. What it means to say is that the system has detected that the URLs submitted redirect, so FYI, if you didn&#039;t know that, here&#039;s the heads up in case you want to submit the target URLs instead.

The Googlebot can access the redirects just fine.</description>
		<content:encoded><![CDATA[<p>This is really a matter of incorrect wording of the error message. What it means to say is that the system has detected that the URLs submitted redirect, so FYI, if you didn&#8217;t know that, here&#8217;s the heads up in case you want to submit the target URLs instead.</p>
<p>The Googlebot can access the redirects just fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lakerscore</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58272</link>
		<dc:creator>lakerscore</dc:creator>
		<pubDate>Fri, 24 Aug 2007 15:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58272</guid>
		<description>I see googlebot visit my site in my logs about 5 times a day, BUT good old webmaster tools hasn&#039;t updated since July 30th.

I understand that it updates sporadically, but c&#039;mon its almost 30 days....

thats why i stick to the old school -- log files...

webmaster tools is starting to o piss me off...</description>
		<content:encoded><![CDATA[<p>I see googlebot visit my site in my logs about 5 times a day, BUT good old webmaster tools hasn&#8217;t updated since July 30th.</p>
<p>I understand that it updates sporadically, but c&#8217;mon its almost 30 days&#8230;.</p>
<p>thats why i stick to the old school &#8212; log files&#8230;</p>
<p>webmaster tools is starting to o piss me off&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EGM</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58222</link>
		<dc:creator>EGM</dc:creator>
		<pubDate>Wed, 22 Aug 2007 16:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58222</guid>
		<description>I had this issue with a very large project I am working on. My take was not that Google was objecting to the idea of multiple redirects on a single URL (I didn&#039;t have any of those...one 301 redirect for each URL). Instead, they took a look at our site map with all the old URL&#039;s and once it hit a bunch of 301&#039;s in a row, I think it just said &quot;Hold on here. You need to redo your sitemap. Too many 301 redirects in there.&quot;

When we recreated the sitemap with the new URL&#039;s the error message disappeared.

Maybe it was a fluke. Your mileage may vary.</description>
		<content:encoded><![CDATA[<p>I had this issue with a very large project I am working on. My take was not that Google was objecting to the idea of multiple redirects on a single URL (I didn&#8217;t have any of those&#8230;one 301 redirect for each URL). Instead, they took a look at our site map with all the old URL&#8217;s and once it hit a bunch of 301&#8217;s in a row, I think it just said &#8220;Hold on here. You need to redo your sitemap. Too many 301 redirects in there.&#8221;</p>
<p>When we recreated the sitemap with the new URL&#8217;s the error message disappeared.</p>
<p>Maybe it was a fluke. Your mileage may vary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sharp</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58198</link>
		<dc:creator>Adam Sharp</dc:creator>
		<pubDate>Tue, 21 Aug 2007 15:38:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58198</guid>
		<description>Interesting stuff Jay, especially the robots.txt thing.  Never thought about that before.</description>
		<content:encoded><![CDATA[<p>Interesting stuff Jay, especially the robots.txt thing.  Never thought about that before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aaron wall</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58168</link>
		<dc:creator>aaron wall</dc:creator>
		<pubDate>Mon, 20 Aug 2007 06:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58168</guid>
		<description>You didn&#039;t get the memo Michael? 

If you are a (non corporate) SEO and rebrand a site it is a shady redirect. Google recently killed over 10,000 organic links I built for one of my sites.</description>
		<content:encoded><![CDATA[<p>You didn&#8217;t get the memo Michael? </p>
<p>If you are a (non corporate) SEO and rebrand a site it is a shady redirect. Google recently killed over 10,000 organic links I built for one of my sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Larson</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58164</link>
		<dc:creator>Matt Larson</dc:creator>
		<pubDate>Mon, 20 Aug 2007 01:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58164</guid>
		<description>Amen -</description>
		<content:encoded><![CDATA[<p>Amen -</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Morris</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58156</link>
		<dc:creator>Brad Morris</dc:creator>
		<pubDate>Sun, 19 Aug 2007 19:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58156</guid>
		<description>I&#039;ve encountered this same error message, but with 302s and not 301s. I cleaned up the 302s and that cleared everything up perfectly. Not sure what to make of this though.

Post your progress, I&#039;d like to  know what happens</description>
		<content:encoded><![CDATA[<p>I&#8217;ve encountered this same error message, but with 302s and not 301s. I cleaned up the 302s and that cleared everything up perfectly. Not sure what to make of this though.</p>
<p>Post your progress, I&#8217;d like to  know what happens</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David LaFerney</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58115</link>
		<dc:creator>David LaFerney</dc:creator>
		<pubDate>Sat, 18 Aug 2007 01:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58115</guid>
		<description>I&#039;ve been having the exact same issue, except I&#039;m just trying to spin off some poorly related content to end up with 2 more focused sites.  I think in my case Jay Harper has it nailed.  My automatically generated sitemap is still pointing to the original locations on the old site.  I guess I just need to dig through it manually.  At least now I know what&#039;s up.  Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been having the exact same issue, except I&#8217;m just trying to spin off some poorly related content to end up with 2 more focused sites.  I think in my case Jay Harper has it nailed.  My automatically generated sitemap is still pointing to the original locations on the old site.  I guess I just need to dig through it manually.  At least now I know what&#8217;s up.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bl.asphemo.us</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58111</link>
		<dc:creator>bl.asphemo.us</dc:creator>
		<pubDate>Fri, 17 Aug 2007 19:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58111</guid>
		<description>I was getting the same warning a few weeks ago on some of my domains. I was able to clear it up pretty quickly and easily, but I must admit I was and still am curious about what &quot;too many&quot; equates to, exactly.</description>
		<content:encoded><![CDATA[<p>I was getting the same warning a few weeks ago on some of my domains. I was able to clear it up pretty quickly and easily, but I must admit I was and still am curious about what &#8220;too many&#8221; equates to, exactly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Harper</title>
		<link>http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/comment-page-1/#comment-58103</link>
		<dc:creator>Jay Harper</dc:creator>
		<pubDate>Fri, 17 Aug 2007 12:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.wolf-howl.com/case-study/webmaster-central-has-problems-with-301s-to-a-new-domain/#comment-58103</guid>
		<description>Are you saying that the sitemap for domain #1 has URLs pointing to domain #2? If so, that&#039;s the problem. Sitemaps can only contain URLs that are in the same directory they are or &quot;beneath&quot; them in the directory structure of the site that they&#039;re served from - URLs from other domains don&#039;t meet those criteria.

The error Google is throwing makes it sound like the sitemap for domain #1 has URLs for domain #1 but those URLs result in redirects to domain #2. In that case one redirect is too many because the redirect turns the valid URL into a URL that isn&#039;t valid for the sitemap since the sitemap can&#039;t contain URLs from other domains.

All you can do in a situation like this is have a sitemap on the new domain, no sitemap on the old domain, 301s in place on the old domain, and wait for googlebot to crawl all of your pages and find the redirects. I&#039;m pretty sure there&#039;s no way to seed the process and make it go any faster.

One additional caveat is to make sure the robots.txt file for the old domain isn&#039;t redirected if you implement a &quot;redirect everything&quot; approach. You can get some pretty odd things happening if it is redirected.</description>
		<content:encoded><![CDATA[<p>Are you saying that the sitemap for domain #1 has URLs pointing to domain #2? If so, that&#8217;s the problem. Sitemaps can only contain URLs that are in the same directory they are or &#8220;beneath&#8221; them in the directory structure of the site that they&#8217;re served from &#8211; URLs from other domains don&#8217;t meet those criteria.</p>
<p>The error Google is throwing makes it sound like the sitemap for domain #1 has URLs for domain #1 but those URLs result in redirects to domain #2. In that case one redirect is too many because the redirect turns the valid URL into a URL that isn&#8217;t valid for the sitemap since the sitemap can&#8217;t contain URLs from other domains.</p>
<p>All you can do in a situation like this is have a sitemap on the new domain, no sitemap on the old domain, 301s in place on the old domain, and wait for googlebot to crawl all of your pages and find the redirects. I&#8217;m pretty sure there&#8217;s no way to seed the process and make it go any faster.</p>
<p>One additional caveat is to make sure the robots.txt file for the old domain isn&#8217;t redirected if you implement a &#8220;redirect everything&#8221; approach. You can get some pretty odd things happening if it is redirected.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
