<?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: Moving your site, how Google handled mine</title>
	<atom:link href="http://www.seoidiot.co.uk/moving-your-site-how-google-handled-mine/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seoidiot.co.uk/moving-your-site-how-google-handled-mine/</link>
	<description>SEO Consultant - SEOidiots SEO Blackhat Blog</description>
	<lastBuildDate>Wed, 13 Jan 2010 22:12:53 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SEOidiot</title>
		<link>http://www.seoidiot.co.uk/moving-your-site-how-google-handled-mine/comment-page-1/#comment-30906</link>
		<dc:creator>SEOidiot</dc:creator>
		<pubDate>Mon, 03 Nov 2008 14:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.seoidiot.co.uk/?p=398#comment-30906</guid>
		<description>I havent tried it on something of quite that scale, have done many thousands of pages and mostly Google has been well behaved.

There are no guarantees though and they do at times make a real illogical hash of the process. Not much you can do but start the process and hope..

Crap advice I know but blame Google for being crap...

On a site with that size its perhaps better to do it in sections and concentrate on the 5% of the content that actually makes a difference I suppose...</description>
		<content:encoded><![CDATA[<p>I havent tried it on something of quite that scale, have done many thousands of pages and mostly Google has been well behaved.</p>
<p>There are no guarantees though and they do at times make a real illogical hash of the process. Not much you can do but start the process and hope..</p>
<p>Crap advice I know but blame Google for being crap&#8230;</p>
<p>On a site with that size its perhaps better to do it in sections and concentrate on the 5% of the content that actually makes a difference I suppose&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SomePerson</title>
		<link>http://www.seoidiot.co.uk/moving-your-site-how-google-handled-mine/comment-page-1/#comment-30893</link>
		<dc:creator>SomePerson</dc:creator>
		<pubDate>Mon, 27 Oct 2008 03:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.seoidiot.co.uk/?p=398#comment-30893</guid>
		<description>My 301 redirect almost killed me.  We took every precaution, consulted with an eternal SEO consultant just to make sure.  We read and researched.  Our site has several million pages- so it is not customary, and much of the literature on 301 redirect; ie: how long Google takes to re-index the new domain is based on small and medium sites.  In short, the redirect was a disaster, with google delisting the old domain almost immediately, and then very slowly indexing the new domain, tens of thousands of pages at a time.  That may seem fast, but we had millions in the index.  At that pace, it was going to take us two years to get anywhere close to the pages we had back.

In short, I will never do a 301 again on a large site.</description>
		<content:encoded><![CDATA[<p>My 301 redirect almost killed me.  We took every precaution, consulted with an eternal SEO consultant just to make sure.  We read and researched.  Our site has several million pages- so it is not customary, and much of the literature on 301 redirect; ie: how long Google takes to re-index the new domain is based on small and medium sites.  In short, the redirect was a disaster, with google delisting the old domain almost immediately, and then very slowly indexing the new domain, tens of thousands of pages at a time.  That may seem fast, but we had millions in the index.  At that pace, it was going to take us two years to get anywhere close to the pages we had back.</p>
<p>In short, I will never do a 301 again on a large site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
