<?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: Blogger to WordPress: No Sunday Drive</title>
	<atom:link href="http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/</link>
	<description>Kent Newsome on technology, music and life</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TD</title>
		<link>http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/comment-page-1/#comment-4735</link>
		<dc:creator>TD</dc:creator>
		<pubDate>Sat, 29 Sep 2007 13:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2831#comment-4735</guid>
		<description>Kent, try this:http://underscorebleach.net/jotsheet/2006/05/move-blogger-to-wordpressJust came across it and it seems to solve the concerns you had.</description>
		<content:encoded><![CDATA[<p>Kent, try this:<a href="http://underscorebleach.net/jotsheet/2006/05/move-blogger-to-wordpressJust" rel="nofollow">http://underscorebleach.net/jotsheet/2006/05/move-blogger-to-wordpressJust</a> came across it and it seems to solve the concerns you had.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shig Odani</title>
		<link>http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/comment-page-1/#comment-4736</link>
		<dc:creator>Shig Odani</dc:creator>
		<pubDate>Wed, 19 Apr 2006 03:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2831#comment-4736</guid>
		<description>Hi, you can actually do a 301 re-direct for each individual post, which will tell the engines that the page has changed URLs, and you shouldn&#039;t lose your spot in the rankings. I&#039;ve blogged about the steps for moving from Typepad to Wordpress here:http://shig.odani.com/2006/02/25/typepad-to-wordpress/</description>
		<content:encoded><![CDATA[<p>Hi, you can actually do a 301 re-direct for each individual post, which will tell the engines that the page has changed URLs, and you shouldn&#8217;t lose your spot in the rankings. I&#8217;ve blogged about the steps for moving from Typepad to WordPress here:<a href="http://shig.odani.com/2006/02/25/typepad-to-wordpress/" rel="nofollow">http://shig.odani.com/2006/02/25/typepad-to-wordpress/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/comment-page-1/#comment-4737</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Mon, 20 Mar 2006 19:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2831#comment-4737</guid>
		<description>Kent,Currently, the only non-technical methods I&#039;ve found for moving people over to your WordPress blog, are the following:1) Leave your blogger posts/pages precisely where they are, but add a meta refresh tag, that automatically send people to your new blog.THE PROBLEM: You will not be able to refresh to the post, itsself, unless you edit each and every blogger post page, by hand, and insert the appropriate URL.  The meta refresh is mainly to move people to your main URL.  This option is best for people switching from a .blogspot.com domain, to their own.2) Re-do your blogger template, and republish.  The template should remove everything but the post, itsself (no sidebars, etc..), and across the very top of the page a notice like &quot;ATTENTION: This blog has moved to WordPress.  After reading the post, please click HERE to continue to the new system&quot; or similar.  Also, remove comment links and place a notice asking people to move to the new system, to comment.THE PROBLEM:  Well, it looks strange, and it may not make a difference.The best solution I&#039;ve come up with is the following:1) Leave your blogger pages in place.2) Set up WordPress, and install the Google SiteMaps plugin, and sign up for the program.3) Wait three to six months, and ALL of your posts will be indexed by Google, on your WordPress URLs.  You may then start to delete your blogger pages.3.5) Technically, you can delete your blogger pages the instant you see your WordPress URLs start to place in the search engine rankings, as the entries in your WordPress blog (even the ones imported from Google), would still be considered &quot;newer&quot; content, and would - therefore - rank higher in the SERPs than the blogger ones.  In reality, it would take only about a month or so, with the Google Sitemaps program.3.6) This is only viable for Google. heh.I&#039;ll look into the technical method info at some point, and see if can&#039;t figure out an easier way of doing it.</description>
		<content:encoded><![CDATA[<p>Kent,Currently, the only non-technical methods I&#8217;ve found for moving people over to your WordPress blog, are the following:1) Leave your blogger posts/pages precisely where they are, but add a meta refresh tag, that automatically send people to your new blog.THE PROBLEM: You will not be able to refresh to the post, itsself, unless you edit each and every blogger post page, by hand, and insert the appropriate URL.  The meta refresh is mainly to move people to your main URL.  This option is best for people switching from a .blogspot.com domain, to their own.2) Re-do your blogger template, and republish.  The template should remove everything but the post, itsself (no sidebars, etc..), and across the very top of the page a notice like &#8220;ATTENTION: This blog has moved to WordPress.  After reading the post, please click HERE to continue to the new system&#8221; or similar.  Also, remove comment links and place a notice asking people to move to the new system, to comment.THE PROBLEM:  Well, it looks strange, and it may not make a difference.The best solution I&#8217;ve come up with is the following:1) Leave your blogger pages in place.2) Set up WordPress, and install the Google SiteMaps plugin, and sign up for the program.3) Wait three to six months, and ALL of your posts will be indexed by Google, on your WordPress URLs.  You may then start to delete your blogger pages.3.5) Technically, you can delete your blogger pages the instant you see your WordPress URLs start to place in the search engine rankings, as the entries in your WordPress blog (even the ones imported from Google), would still be considered &#8220;newer&#8221; content, and would &#8211; therefore &#8211; rank higher in the SERPs than the blogger ones.  In reality, it would take only about a month or so, with the Google Sitemaps program.3.6) This is only viable for Google. heh.I&#8217;ll look into the technical method info at some point, and see if can&#8217;t figure out an easier way of doing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fly Girl</title>
		<link>http://www.newsome.org/2006/03/blogger-to-wordpress-no-sunday-drive/comment-page-1/#comment-4738</link>
		<dc:creator>Fly Girl</dc:creator>
		<pubDate>Mon, 20 Mar 2006 16:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://clients.emmense.com/newsome/?p=2831#comment-4738</guid>
		<description>I&#039;m in the same boat!  Only it sounds like I have even less technical &quot;chops&quot; than you.When I ask people about options, it seems that all I get as a response is that I shouldn&#039;t have used Blogger in the first place.  Definitely not a helpful response.I&#039;d love to know if you find any options.</description>
		<content:encoded><![CDATA[<p>I&#8217;m in the same boat!  Only it sounds like I have even less technical &#8220;chops&#8221; than you.When I ask people about options, it seems that all I get as a response is that I shouldn&#8217;t have used Blogger in the first place.  Definitely not a helpful response.I&#8217;d love to know if you find any options.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

