<?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: New Project! wpSEO &#8211; Professional Plugin For Search Engine Optimization In WordPress</title>
	<atom:link href="http://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/feed/" rel="self" type="application/rss+xml" />
	<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/</link>
	<description>My Mind is not Pigeonholed, neither is my Website</description>
	<lastBuildDate>Sun, 02 Feb 2020 16:29:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ownermylife</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-14820</link>
		<dc:creator>ownermylife</dc:creator>
		<pubDate>Thu, 25 Aug 2011 01:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-14820</guid>
		<description>WPSEO is one of the best Plugins . I like it

Thank you for post.</description>
		<content:encoded><![CDATA[<p>WPSEO is one of the best Plugins . I like it</p>
<p>Thank you for post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mysuperwoofer</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-13740</link>
		<dc:creator>mysuperwoofer</dc:creator>
		<pubDate>Sun, 18 Jul 2010 04:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-13740</guid>
		<description>thanks very much for the seo tip and wordpress plugin. I like very much. it is greatly help my seo job</description>
		<content:encoded><![CDATA[<p>thanks very much for the seo tip and wordpress plugin. I like very much. it is greatly help my seo job</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-12815</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 18 May 2009 15:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-12815</guid>
		<description>Hey Maik, thanks a lot for the compliment. DANKE!</description>
		<content:encoded><![CDATA[<p>Hey Maik, thanks a lot for the compliment. DANKE!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maik</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-12813</link>
		<dc:creator>Maik</dc:creator>
		<pubDate>Sat, 16 May 2009 23:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-12813</guid>
		<description>WPSEO is one of the best Plugins and really a must have for any WP User</description>
		<content:encoded><![CDATA[<p>WPSEO is one of the best Plugins and really a must have for any WP User</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-12723</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Fri, 03 Apr 2009 11:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-12723</guid>
		<description>hi, finally the custom fields used by wpseo for manual description, keywords and title are hidden from the post editor!  however, wp_postmeta table still contains a lot of clutter from previous versions of the plugin, and editing old posts will still show redundant custom field information.  the following mysql will fix this (i&#039;m disappointed this wasn&#039;t rolled into some kind of db-upgrade process for ppl coming from older versions):

delete from wp_postmeta where meta_key = &#039;keywords&#039; and meta_value = &#039;&#039;;
delete from wp_postmeta where meta_key = &#039;description&#039; and meta_value = &#039;&#039;;
delete from wp_postmeta where meta_key = &#039;title&#039; and meta_value = &#039;&#039;;
update wp_postmeta set meta_key = &#039;_wpseo_edit_keywords&#039; where meta_key = &#039;keywords&#039;;
update wp_postmeta set meta_key = &#039;_wpseo_edit_description&#039; where meta_key = &#039;description&#039;;
update wp_postmeta set meta_key = &#039;_wpseo_edit_title&#039; where meta_key = &#039;title&#039;;</description>
		<content:encoded><![CDATA[<p>hi, finally the custom fields used by wpseo for manual description, keywords and title are hidden from the post editor!  however, wp_postmeta table still contains a lot of clutter from previous versions of the plugin, and editing old posts will still show redundant custom field information.  the following mysql will fix this (i&#8217;m disappointed this wasn&#8217;t rolled into some kind of db-upgrade process for ppl coming from older versions):</p>
<p>delete from wp_postmeta where meta_key = &#8216;keywords&#8217; and meta_value = &#8221;;<br />
delete from wp_postmeta where meta_key = &#8216;description&#8217; and meta_value = &#8221;;<br />
delete from wp_postmeta where meta_key = &#8216;title&#8217; and meta_value = &#8221;;<br />
update wp_postmeta set meta_key = &#8216;_wpseo_edit_keywords&#8217; where meta_key = &#8216;keywords&#8217;;<br />
update wp_postmeta set meta_key = &#8216;_wpseo_edit_description&#8217; where meta_key = &#8216;description&#8217;;<br />
update wp_postmeta set meta_key = &#8216;_wpseo_edit_title&#8217; where meta_key = &#8216;title&#8217;;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-8687</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Fri, 09 Jan 2009 22:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-8687</guid>
		<description>Hey Oliver, my pleasure :) 

To your first question, we will work on this to implement it into a future version. 

The bug is fixed, thanks for pointing it out. It&#039;s already included in the current download file.</description>
		<content:encoded><![CDATA[<p>Hey Oliver, my pleasure <img src='https://notaniche.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>To your first question, we will work on this to implement it into a future version. </p>
<p>The bug is fixed, thanks for pointing it out. It&#8217;s already included in the current download file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-8658</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Thu, 08 Jan 2009 19:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-8658</guid>
		<description>Thanks for your detailed answer.
I just installed wpSEO and already got the license key from Sergej and i&#039;m quite impressed by the huge amount of options.
Is it possible to define a custom format for page titles or can i just use the pre-defined?

And a small &quot;bug&quot; (well it&#039;s not a real bug but i don&#039;t think it should work that way): If the question mark which links to the manual is in the same line as the checkbox, the checkbox changes its status if i click on the &quot;?&quot;. I would either change that behaviour or move the &quot;?&quot; in a new line.

Greets,
Oliver</description>
		<content:encoded><![CDATA[<p>Thanks for your detailed answer.<br />
I just installed wpSEO and already got the license key from Sergej and i&#8217;m quite impressed by the huge amount of options.<br />
Is it possible to define a custom format for page titles or can i just use the pre-defined?</p>
<p>And a small &#8220;bug&#8221; (well it&#8217;s not a real bug but i don&#8217;t think it should work that way): If the question mark which links to the manual is in the same line as the checkbox, the checkbox changes its status if i click on the &#8220;?&#8221;. I would either change that behaviour or move the &#8220;?&#8221; in a new line.</p>
<p>Greets,<br />
Oliver</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-8640</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 07 Jan 2009 21:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-8640</guid>
		<description>Hey Oliver,

sorry for my late response, but there are quite a lot differences:

An included XML file with recommended options.
Export and import of settings
Use of manually entered metadata from &quot;All in One SEO Pack&quot;
Fully documented
Clean up after uninstall the plugin
WordPress 2.7 ready: Design and as well as technical
Position of meta data at top of the source code
Clean and user friendly interface
Safety conscious programming
Absolutely no additional database queries
Quick &amp; Dirty: activate, import options, done!
Prompt adjustment to new WordPress releases
Continuous and professional further development
Great variety of preferences with more than 70 settings
Reliable and fast support via email

And many more features and advantages!

But I would suggest you should try it out and convince yourself, let me know if you have any questions or suggestions for the plugin. 

Check also the screenshot, there you can see all settings you can make.
http://download.ebiene.de/wpseo/screenshot/wpseo_en.png

Enjoy and let us know how you like it</description>
		<content:encoded><![CDATA[<p>Hey Oliver,</p>
<p>sorry for my late response, but there are quite a lot differences:</p>
<p>An included XML file with recommended options.<br />
Export and import of settings<br />
Use of manually entered metadata from &#8220;All in One SEO Pack&#8221;<br />
Fully documented<br />
Clean up after uninstall the plugin<br />
WordPress 2.7 ready: Design and as well as technical<br />
Position of meta data at top of the source code<br />
Clean and user friendly interface<br />
Safety conscious programming<br />
Absolutely no additional database queries<br />
Quick &#038; Dirty: activate, import options, done!<br />
Prompt adjustment to new WordPress releases<br />
Continuous and professional further development<br />
Great variety of preferences with more than 70 settings<br />
Reliable and fast support via email</p>
<p>And many more features and advantages!</p>
<p>But I would suggest you should try it out and convince yourself, let me know if you have any questions or suggestions for the plugin. </p>
<p>Check also the screenshot, there you can see all settings you can make.<br />
<a href="http://download.ebiene.de/wpseo/screenshot/wpseo_en.png" rel="nofollow">http://download.ebiene.de/wpse.....seo_en.png</a></p>
<p>Enjoy and let us know how you like it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>https://notaniche.com/new-project-wpseo-professional-plugin-for-search-engine-optimization-in-wordpress/1040/comment-page-1/#comment-8575</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Tue, 06 Jan 2009 14:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://notaniche.com/?p=1040#comment-8575</guid>
		<description>Hello Alex,
i just installed the &quot;All in One SEO Pack&quot; plugin a few days ago on my blog. Would you mind explaining the key differences between that and yours?

Greets,
Oliver</description>
		<content:encoded><![CDATA[<p>Hello Alex,<br />
i just installed the &#8220;All in One SEO Pack&#8221; plugin a few days ago on my blog. Would you mind explaining the key differences between that and yours?</p>
<p>Greets,<br />
Oliver</p>
]]></content:encoded>
	</item>
</channel>
</rss>
