<?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: SMPR Questions</title>
	<atom:link href="http://miketoner.com/2008/09/smpr-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://miketoner.com/2008/09/smpr-questions/</link>
	<description>At the intersection of Content, Design &#38; Delivery.</description>
	<lastBuildDate>Mon, 09 Jan 2012 21:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Noah Mallin</title>
		<link>http://miketoner.com/2008/09/smpr-questions/comment-page-1/#comment-85</link>
		<dc:creator>Noah Mallin</dc:creator>
		<pubDate>Wed, 10 Sep 2008 14:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://miketoner.com/?p=53#comment-85</guid>
		<description>From my experience - For the first question e-mails are tricky because some mailboxes will throw anything with multimedia embedded etc. into junk mail. Generally speaking I&#039;d say to go with something more stripped down and embed links to the good stuff.

For question 2, as you said the primary purpose of your press release is to spark a journalist to re-use your content in their own story not so much to republish verbatim. SMPR does add another wrinkle in that a well optimized SMPR release can generate traffic and bypass the journalist entirely.</description>
		<content:encoded><![CDATA[<p>From my experience &#8211; For the first question e-mails are tricky because some mailboxes will throw anything with multimedia embedded etc. into junk mail. Generally speaking I&#8217;d say to go with something more stripped down and embed links to the good stuff.</p>
<p>For question 2, as you said the primary purpose of your press release is to spark a journalist to re-use your content in their own story not so much to republish verbatim. SMPR does add another wrinkle in that a well optimized SMPR release can generate traffic and bypass the journalist entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Walker</title>
		<link>http://miketoner.com/2008/09/smpr-questions/comment-page-1/#comment-84</link>
		<dc:creator>James Walker</dc:creator>
		<pubDate>Wed, 10 Sep 2008 13:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://miketoner.com/?p=53#comment-84</guid>
		<description>Don&#039;t think the SMPR should be inserted into the email. You never know what kind of email filter the reciever has which may just flag your email as junk or spam. 

Probably better to include a couple lines of text explaining what&#039;s going on with a link to the release.

Also, I know very few journalists and bloggers who will run things as is. Bullets are great because they&#039;re easy to scan for the key info you&#039;re interested in. With bulleted facts and quotes, I think you do increase the chance that they&#039;ll get used in posts and stories. It&#039;s so easy for the writer to pull out a bullet and insert it into their piece.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t think the SMPR should be inserted into the email. You never know what kind of email filter the reciever has which may just flag your email as junk or spam. </p>
<p>Probably better to include a couple lines of text explaining what&#8217;s going on with a link to the release.</p>
<p>Also, I know very few journalists and bloggers who will run things as is. Bullets are great because they&#8217;re easy to scan for the key info you&#8217;re interested in. With bulleted facts and quotes, I think you do increase the chance that they&#8217;ll get used in posts and stories. It&#8217;s so easy for the writer to pull out a bullet and insert it into their piece.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

