<?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: Long Tail vs. Short Tail Keywords Inside Your Social Media Campaigns</title>
	<atom:link href="http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/</link>
	<description>What to do in Social Media when - Shift Happens</description>
	<lastBuildDate>Thu, 16 Jun 2011 13:58:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Michael Fraietta</title>
		<link>http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/comment-page-1/#comment-197</link>
		<dc:creator>Michael Fraietta</dc:creator>
		<pubDate>Tue, 23 Mar 2010 22:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremysaid.com/?p=319#comment-197</guid>
		<description>Jeremy, thanks for mentioning Filtrbox (Jive Software) in your post. Don&#039;t forget the &quot;should not contain&quot; box and how useful that can be.  For example:&lt;br&gt;&lt;br&gt;Jive + (software OR community OR 2.0 OR enterprise OR &quot;internal collaboration&quot;) - [But Should NOT contain] &quot;Jive ass turkey&quot; &quot;Jive records&quot;&lt;br&gt;&lt;br&gt;Nice post.&lt;br&gt;&lt;br&gt;Michael Fraietta&lt;br&gt;Director of Social Media at Jive Software&lt;br&gt;@MichaelFraietta</description>
		<content:encoded><![CDATA[<p>Jeremy, thanks for mentioning Filtrbox (Jive Software) in your post. Don&#39;t forget the &#8220;should not contain&#8221; box and how useful that can be.  For example:</p>
<p>Jive + (software OR community OR 2.0 OR enterprise OR &#8220;internal collaboration&#8221;) &#8211; [But Should NOT contain] &#8220;Jive ass turkey&#8221; &#8220;Jive records&#8221;</p>
<p>Nice post.</p>
<p>Michael Fraietta<br />Director of Social Media at Jive Software<br />@MichaelFraietta</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fraietta</title>
		<link>http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/comment-page-1/#comment-188</link>
		<dc:creator>Michael Fraietta</dc:creator>
		<pubDate>Tue, 23 Mar 2010 17:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremysaid.com/?p=319#comment-188</guid>
		<description>Jeremy, thanks for mentioning Filtrbox (Jive Software) in your post. Don&#039;t forget the &quot;should not contain&quot; box and how useful that can be.  For example:&lt;br&gt;&lt;br&gt;Jive + (software OR community OR 2.0 OR enterprise OR &quot;internal collaboration&quot;) - [But Should NOT contain] &quot;Jive ass turkey&quot; &quot;Jive records&quot;&lt;br&gt;&lt;br&gt;Nice post.&lt;br&gt;&lt;br&gt;Michael Fraietta&lt;br&gt;Director of Social Media at Jive Software&lt;br&gt;@MichaelFraietta</description>
		<content:encoded><![CDATA[<p>Jeremy, thanks for mentioning Filtrbox (Jive Software) in your post. Don&#39;t forget the &#8220;should not contain&#8221; box and how useful that can be.  For example:</p>
<p>Jive + (software OR community OR 2.0 OR enterprise OR &#8220;internal collaboration&#8221;) &#8211; [But Should NOT contain] &#8220;Jive ass turkey&#8221; &#8220;Jive records&#8221;</p>
<p>Nice post.</p>
<p>Michael Fraietta<br />Director of Social Media at Jive Software<br />@MichaelFraietta</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian McDonald</title>
		<link>http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/comment-page-1/#comment-187</link>
		<dc:creator>Brian McDonald</dc:creator>
		<pubDate>Mon, 22 Mar 2010 21:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremysaid.com/?p=319#comment-187</guid>
		<description>Great post.  I&#039;ve read it twice as there are some good starting points to developing your SEO strategy.</description>
		<content:encoded><![CDATA[<p>Great post.  I&#39;ve read it twice as there are some good starting points to developing your SEO strategy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 1918</title>
		<link>http://www.jeremysaid.com/long-tail-vs-short-tail-keywords-inside-your-social-media-campaigns/comment-page-1/#comment-186</link>
		<dc:creator>1918</dc:creator>
		<pubDate>Sun, 21 Mar 2010 19:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremysaid.com/?p=319#comment-186</guid>
		<description>I started working on a keyword strategy last week that will incorporate both long and short-tail keyword phrases.&lt;br&gt;&lt;br&gt;One of the things we&#039;ll be trying to accomplish is build up a reservoir of keywords that we can then start to salt our product descriptions with. The idea being that some social media buzz may lead to searches. By targeting certain combinations, we can try to sculpt the searches people will type, and thus be optimized for less competitive terms where we win easily.&lt;br&gt;&lt;br&gt;I can&#039;t comment on it&#039;s success yet, but ask me next month :-)</description>
		<content:encoded><![CDATA[<p>I started working on a keyword strategy last week that will incorporate both long and short-tail keyword phrases.</p>
<p>One of the things we&#39;ll be trying to accomplish is build up a reservoir of keywords that we can then start to salt our product descriptions with. The idea being that some social media buzz may lead to searches. By targeting certain combinations, we can try to sculpt the searches people will type, and thus be optimized for less competitive terms where we win easily.</p>
<p>I can&#39;t comment on it&#39;s success yet, but ask me next month <img src='http://www.jeremysaid.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

