<?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: WordPress 2.82 May Hurt Rankings</title>
	<atom:link href="http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 00:02:58 +0000</lastBuildDate>
	<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: Twitter for Business</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-52766</link>
		<dc:creator>Twitter for Business</dc:creator>
		<pubDate>Sat, 07 Nov 2009 23:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-52766</guid>
		<description>I&#039;ve just stumbled across this site and, as a WP user I&#039;m stunned by the amount of SEO issues this raises.

Have we heard any news from WP about this issue? If we&#039;ve lost traffic and rankings, is there any way of restoring them.

Matt</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just stumbled across this site and, as a WP user I&#8217;m stunned by the amount of SEO issues this raises.</p>
<p>Have we heard any news from WP about this issue? If we&#8217;ve lost traffic and rankings, is there any way of restoring them.</p>
<p>Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-52315</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Tue, 27 Oct 2009 13:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-52315</guid>
		<description>This is an insane decision by someone - WordPress  2.85 (upgraded) is now reporting 404 for either a single changed permalink, or changing permalinks site-wide.</description>
		<content:encoded><![CDATA[<p>This is an insane decision by someone &#8211; WordPress  2.85 (upgraded) is now reporting 404 for either a single changed permalink, or changing permalinks site-wide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50478</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 14 Aug 2009 15:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50478</guid>
		<description>Sorry, but that&#039;s really old - In this really short video i demonstrated that &lt;a href=&quot;http://www.pdxtc.com/wpblog/wordpress/wordpress-2-82-changing-url-is-bad/&quot; rel=&quot;nofollow&quot;&gt;the 301 was working&lt;/a&gt; -</description>
		<content:encoded><![CDATA[<p>Sorry, but that&#8217;s really old &#8211; In this really short video i demonstrated that <a href="http://www.pdxtc.com/wpblog/wordpress/wordpress-2-82-changing-url-is-bad/" target="_blank" >the 301 was working</a> -</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50477</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 14 Aug 2009 15:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50477</guid>
		<description>Sorry I never answered this - Well I can&#039;t speak for that version, and have none to test any more, but it seems to me that I remember it being &quot;right&quot; earlier than that... Huh.

Anyone know what version it was where they introduced the feature called - &quot;You don&#039;t have to edit .htaccess anymore when you change a post category or edit a permalink&quot;.</description>
		<content:encoded><![CDATA[<p>Sorry I never answered this &#8211; Well I can&#8217;t speak for that version, and have none to test any more, but it seems to me that I remember it being &#8220;right&#8221; earlier than that&#8230; Huh.</p>
<p>Anyone know what version it was where they introduced the feature called &#8211; &#8220;You don&#8217;t have to edit .htaccess anymore when you change a post category or edit a permalink&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50476</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 14 Aug 2009 15:30:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50476</guid>
		<description>Absolutely, Ben, the issue certainly can be worked around, but it shouldn&#039;t have to be - especially since it all worked correctly just a few versions ago.

The vast majoriy of people won&#039;t / don&#039;t even know there IS a problem, much less will they take the time to edit their .htaccess or install a plugin.</description>
		<content:encoded><![CDATA[<p>Absolutely, Ben, the issue certainly can be worked around, but it shouldn&#8217;t have to be &#8211; especially since it all worked correctly just a few versions ago.</p>
<p>The vast majoriy of people won&#8217;t / don&#8217;t even know there IS a problem, much less will they take the time to edit their .htaccess or install a plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Cook</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50475</link>
		<dc:creator>Ben Cook</dc:creator>
		<pubDate>Fri, 14 Aug 2009 15:16:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50475</guid>
		<description>Yeah, really serving up 200&#039;s for old links is even worse than 302&#039;s.

The issue can still be remedied by a) not changing your link structure b) using an .htaccess file to control the redirects c) using a plugin such as redirection to create the proper redirects on a page level basis.</description>
		<content:encoded><![CDATA[<p>Yeah, really serving up 200&#8242;s for old links is even worse than 302&#8242;s.</p>
<p>The issue can still be remedied by a) not changing your link structure b) using an .htaccess file to control the redirects c) using a plugin such as redirection to create the proper redirects on a page level basis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50474</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 14 Aug 2009 14:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50474</guid>
		<description>They&#039;re at 2.84 now, and it&#039;s still not &quot;right&quot; in my opinion - old permalinks now return 200&#039;s!</description>
		<content:encoded><![CDATA[<p>They&#8217;re at 2.84 now, and it&#8217;s still not &#8220;right&#8221; in my opinion &#8211; old permalinks now return 200&#8242;s!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wen Hosting Reviews</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50473</link>
		<dc:creator>Wen Hosting Reviews</dc:creator>
		<pubDate>Fri, 14 Aug 2009 12:18:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50473</guid>
		<description>Nice man.  I tried them and got the results as you have stated.  Will they rectify that in the next edition?</description>
		<content:encoded><![CDATA[<p>Nice man.  I tried them and got the results as you have stated.  Will they rectify that in the next edition?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DanOfSoCal</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50355</link>
		<dc:creator>DanOfSoCal</dc:creator>
		<pubDate>Wed, 12 Aug 2009 14:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50355</guid>
		<description>Be careful with your bets. If you&#039;re not pulling in any traffic to begin with, then you won&#039;t lose any traffic when switching to WP 2.82. :-)</description>
		<content:encoded><![CDATA[<p>Be careful with your bets. If you&#8217;re not pulling in any traffic to begin with, then you won&#8217;t lose any traffic when switching to WP 2.82. <img src='http://www.pdxtc.com/wpblog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Cook</title>
		<link>http://www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/comment-page-1/#comment-50015</link>
		<dc:creator>Ben Cook</dc:creator>
		<pubDate>Mon, 03 Aug 2009 21:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pdxtc.com/wpblog/?p=1290#comment-50015</guid>
		<description>Ok, I&#039;ve just performed a test using a WP 2.7.1 install (I have no idea why I still have one of those) and can verify that it too is serving up 302 errors.

There is NO reason not to upgrade to the newest version and I would recommend a plugin if you&#039;d like to automate the process of creating 301 redirects when your permalink structure (or any URL for that matter) changes.</description>
		<content:encoded><![CDATA[<p>Ok, I&#8217;ve just performed a test using a WP 2.7.1 install (I have no idea why I still have one of those) and can verify that it too is serving up 302 errors.</p>
<p>There is NO reason not to upgrade to the newest version and I would recommend a plugin if you&#8217;d like to automate the process of creating 301 redirects when your permalink structure (or any URL for that matter) changes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/feed/ ) in 0.96586 seconds, on Feb 10th, 2012 at 12:12 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 9:05 am UTC -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- Quick Cache Is Fully Functional :-) ... A Quick Cache file was just served for (  www.pdxtc.com/wpblog/search-engines/wp-2-82-may-harm-rankings/feed/ ) in 0.00026 seconds, on Feb 11th, 2012 at 4:59 am UTC. -->
