<?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"
	>
<channel>
	<title>Comments on: Fixing the SERPs When Changing Permalink Structure in WordPress</title>
	<atom:link href="http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html</link>
	<description>Web 2.0 from a Web Purist and J2EE Developer</description>
	<pubDate>Sat, 31 Jul 2010 19:12:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: SolReka - Solar Cooking and Alternative Energy News</title>
		<link>http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html#comment-1273</link>
		<dc:creator>SolReka - Solar Cooking and Alternative Energy News</dc:creator>
		<pubDate>Tue, 17 Jun 2008 11:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericdelabar.com/?p=29#comment-1273</guid>
		<description>&lt;strong&gt;Rel=&#8221;nofollow&#8221; removed. Leave comments and get rewarded with a better Page Rank - PR...&lt;/strong&gt;


By default, wordpress automatically adds nofollow into all links added in a wordpress blog. The reason for this is to stop spammers having their wicked way and pulling in loads of traffic from your blog. But why have the nofollow in every link if the ...</description>
		<content:encoded><![CDATA[<p><strong>Rel=&#8221;nofollow&#8221; removed. Leave comments and get rewarded with a better Page Rank - <span class="caps">PR</span>&#8230;</strong></p>
<p>By default, wordpress automatically adds nofollow into all links added in a wordpress blog. The reason for this is to stop spammers having their wicked way and pulling in loads of traffic from your blog. But why have the nofollow in every link if the&nbsp;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SolReka</title>
		<link>http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html#comment-1272</link>
		<dc:creator>SolReka</dc:creator>
		<pubDate>Tue, 17 Jun 2008 11:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericdelabar.com/?p=29#comment-1272</guid>
		<description>Great post, I have always wondered about redirecting old url's.

I guess good housekeeping from the start makes life much easier in the long run, ie set up permalinks at the start of blog / web site build.

PS Added your trackback Eric to my site

Many thanks for the great tips</description>
		<content:encoded><![CDATA[<p>Great post, I have always wondered about redirecting old url&#8217;s.</p>
<p>I guess good housekeeping from the start makes life much easier in the long run, ie set up permalinks at the start of blog / web site build.</p>
<p><span class="caps">PS</span> Added your trackback Eric to my site</p>
<p>Many thanks for the great&nbsp;tips</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html#comment-675</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 08 Apr 2008 16:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericdelabar.com/?p=29#comment-675</guid>
		<description>&lt;p&gt;I thought the same thing, but I'm assuming since under the covers all WordPress URL requests are rewritten to &lt;code&gt;index.php&lt;/code&gt; I don't think it can be done with a plug-in.  (Unless the plugin writes the &lt;code&gt;.htaccess&lt;/code&gt; file, which in my mind is a bit of a security concern.)&lt;/p&gt;
&lt;p&gt;I've considered using a more generic redirect with a regular expression to map &lt;code&gt;?p=##&lt;/code&gt; to something like &lt;code&gt;/post/##&lt;/code&gt; and then using a plug-in like &lt;a href="http://www.deanlee.cn/wordpress/permalinks-migration-plugin/" rel="nofollow"&gt;Dean's Permalink Redirection Plugin&lt;/a&gt; to  redirect &lt;code&gt;/post/##&lt;/code&gt; to the desired URL structure, but I'm not sure of the SEO implications of multiple 301 redirects.&lt;/p&gt;
&lt;p&gt;I suppose it would also be possible to get all of your indexed URLs from Google using a "site:" query and some XSLT and run the results through a script of some sort to change that into the apache redirect lines an prepend them to the &lt;code&gt;.htaccess&lt;/code&gt; file.  The script would have to be pretty complex though in order to map the numeric id to a WordPress page slug.&lt;/p&gt;
&lt;p&gt;This begs to become a utility of some sort, but was a bit to complex of a solution for the 15 or so redirects I had to make.  Sorry for the lack of a real solution, but maybe I can whip something up for a future post when I have a few spare minutes!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I thought the same thing, but I&#8217;m assuming since under the covers all WordPress <span class="caps">URL</span> requests are rewritten to <code>index.php</code> I don&#8217;t think it can be done with a plug-in.  (Unless the plugin writes the <code>.htaccess</code> file, which in my mind is a bit of a security&nbsp;concern.)</p>
<p>I&#8217;ve considered using a more generic redirect with a regular expression to map <code>?p=##</code> to something like <code>/post/##</code> and then using a plug-in like <a href="http://www.deanlee.cn/wordpress/permalinks-migration-plugin/" rel="nofollow">Dean&#8217;s Permalink Redirection Plugin</a> to  redirect <code>/post/##</code> to the desired URL structure, but I&#8217;m not sure of the SEO implications of multiple 301&nbsp;redirects.</p>
<p>I suppose it would also be possible to get all of your indexed URLs from Google using a &#8220;site:&#8221; query and some <span class="caps">XSLT</span> and run the results through a script of some sort to change that into the apache redirect lines an prepend them to the <code>.htaccess</code> file.  The script would have to be pretty complex though in order to map the numeric id to a WordPress page&nbsp;slug.</p>
<p>This begs to become a utility of some sort, but was a bit to complex of a solution for the 15 or so redirects I had to make.  Sorry for the lack of a real solution, but maybe I can whip something up for a future post when I have a few spare&nbsp;minutes!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.ericdelabar.com/2008/04/fixing-the-serps-when-changing-permalink-structure.html#comment-674</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 08 Apr 2008 15:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.ericdelabar.com/?p=29#comment-674</guid>
		<description>This seems like a good solution, right up until you have to manually create 310 redirects for every post. This begs automation.  So how can you create these redirect entries automatically?

...Mike</description>
		<content:encoded><![CDATA[<p>This seems like a good solution, right up until you have to manually create 310 redirects for every post. This begs automation.  So how can you create these redirect entries automatically?&nbsp;&#8230;Mike</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.203 seconds -->
