<?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: Cool Plugin for Changing Font Faces on the Fly</title>
	<atom:link href="http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 11:53:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: david</title>
		<link>http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/comment-page-1/#comment-596</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 18 Aug 2008 14:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dewpointproductions.com/seo_blog/?p=140#comment-596</guid>
		<description>@DG
Point well taken, except the cold-hearted part.</description>
		<content:encoded><![CDATA[<p>@DG<br />
Point well taken, except the cold-hearted part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DG</title>
		<link>http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/comment-page-1/#comment-595</link>
		<dc:creator>DG</dc:creator>
		<pubDate>Mon, 18 Aug 2008 02:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.dewpointproductions.com/seo_blog/?p=140#comment-595</guid>
		<description>That's pretty cold-hearted of you to leave this post up.

You put the entire "I'm sorry" at the end, after a long explanation of how bad this plugin is.

You should put the "I'm sorry this post was wrong" at the BEGINNING of the post, so that all the new people stumbling on this post when searching for the cool plugin won't get the wrong impression from the dis you posted.</description>
		<content:encoded><![CDATA[<p>That&#8217;s pretty cold-hearted of you to leave this post up.</p>
<p>You put the entire &#8220;I&#8217;m sorry&#8221; at the end, after a long explanation of how bad this plugin is.</p>
<p>You should put the &#8220;I&#8217;m sorry this post was wrong&#8221; at the BEGINNING of the post, so that all the new people stumbling on this post when searching for the cool plugin won&#8217;t get the wrong impression from the dis you posted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Zappone</title>
		<link>http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/comment-page-1/#comment-585</link>
		<dc:creator>Dan Zappone</dc:creator>
		<pubDate>Tue, 12 Aug 2008 14:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.dewpointproductions.com/seo_blog/?p=140#comment-585</guid>
		<description>Ugh... well the code tags didn't work out very well in my last comment.</description>
		<content:encoded><![CDATA[<p>Ugh&#8230; well the code tags didn&#8217;t work out very well in my last comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Zappone</title>
		<link>http://www.dewpointproductions.com/seo_blog/wordpress/deadly-search-engine-optimization-plugin-for-wordpress/comment-page-1/#comment-584</link>
		<dc:creator>Dan Zappone</dc:creator>
		<pubDate>Tue, 12 Aug 2008 14:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.dewpointproductions.com/seo_blog/?p=140#comment-584</guid>
		<description>Just a quick note.  First, thanks for the plug. :-)

The JavaScript behind FLIR is by Cory Mawhorter.  I am working with him to create the WordPress plugin - so all the really cool credit goes to him.

Also if you take a look at the source for a page that FLIR is running on you will see that you header tags are still there - which search engines will see.  The image replacement takes place on the client side using JavaScript so no matter what happens - say JavaScript is turned off - you still get your page.  for example I have FLIR running on 23Systems and it will render images for the header &lt;code&gt;&lt;/code&gt; and &lt;code&gt;&lt;/code&gt; but if you look at the source you will see (and so should search engines this:

&lt;code&gt;
		&#160;
		&lt;a href="http://www.23systems.net/"&gt;23Systems Web Devsign&lt;/a&gt;
		Custom website design and development
&lt;/code&gt;

So it shouldn't impact your SEO even is the search engines are rendering the JavaScript.</description>
		<content:encoded><![CDATA[<p>Just a quick note.  First, thanks for the plug. <img src='http://www.dewpointproductions.com/seo_blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>The JavaScript behind FLIR is by Cory Mawhorter.  I am working with him to create the WordPress plugin - so all the really cool credit goes to him.</p>
<p>Also if you take a look at the source for a page that FLIR is running on you will see that you header tags are still there - which search engines will see.  The image replacement takes place on the client side using JavaScript so no matter what happens - say JavaScript is turned off - you still get your page.  for example I have FLIR running on 23Systems and it will render images for the header <code></code> and <code></code> but if you look at the source you will see (and so should search engines this:</p>
<p><code><br />
		&nbsp;<br />
		<a href="http://www.23systems.net/">23Systems Web Devsign</a><br />
		Custom website design and development<br />
</code></p>
<p>So it shouldn&#8217;t impact your SEO even is the search engines are rendering the JavaScript.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
