<?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: Engaging in ‘high risk’ activity — moving my blog</title>
	<atom:link href="http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/</link>
	<description>Lifestyle Technology In Plain English</description>
	<lastBuildDate>Thu, 18 Mar 2010 15:59:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bgrier</title>
		<link>http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/comment-page-1/#comment-360</link>
		<dc:creator>bgrier</dc:creator>
		<pubDate>Thu, 15 May 2008 04:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/#comment-360</guid>
		<description>Hi Jamie, thanks for the thoughtful suggestions!

I was thinking 301s would work, but hadn&#039;t started exploring them yet, nor had any idea on how to implement them. The htaccess advice is helpful, and likely the way I&#039;ll go.</description>
		<content:encoded><![CDATA[<p>Hi Jamie, thanks for the thoughtful suggestions!</p>
<p>I was thinking 301s would work, but hadn’t started exploring them yet, nor had any idea on how to implement them. The htaccess advice is helpful, and likely the way I’ll go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Grove - How Not To Write</title>
		<link>http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/comment-page-1/#comment-359</link>
		<dc:creator>Jamie Grove - How Not To Write</dc:creator>
		<pubDate>Thu, 15 May 2008 01:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bradgrier.com/2008/05/14/engaging-in-high-risk-activity-moving-my-blog/#comment-359</guid>
		<description>Hi, Brad.

One thing you&#039;ll want to do is set up 301 redirects for all of the existing pages on yoursite.  The 301 redirect will tell search engines that your content has permanently moved to a new home.  This will enable you to maintain the link-love gained from other sites as well as keeping the age of your pages intact.

Looks like you&#039;re using Apache for the web server so this is pretty easy.  You just add a few simple lines to the .htaccess file in you root web content directory (Google htaccess 301 redirect for an example).

As an alternative, you could also install the Redirection plugin for WordPress.  This will allow you to set up redirects right inside WordPress admin.  However, it means you also need to leave WordPress on the old site...

The htaccess redirect is probably the best option, especially if you are moving the whole site complete and leaving nothing behind.</description>
		<content:encoded><![CDATA[<p>Hi, Brad.</p>
<p>One thing you’ll want to do is set up 301 redirects for all of the existing pages on yoursite.  The 301 redirect will tell search engines that your content has permanently moved to a new home.  This will enable you to maintain the link-love gained from other sites as well as keeping the age of your pages intact.</p>
<p>Looks like you’re using Apache for the web server so this is pretty easy.  You just add a few simple lines to the .htaccess file in you root web content directory (Google htaccess 301 redirect for an example).</p>
<p>As an alternative, you could also install the Redirection plugin for WordPress.  This will allow you to set up redirects right inside WordPress admin.  However, it means you also need to leave WordPress on the old site…</p>
<p>The htaccess redirect is probably the best option, especially if you are moving the whole site complete and leaving nothing behind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
