<?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: Online Newsletters: How to Present Links?</title>
	<atom:link href="http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/</link>
	<description>Amy Gahran's news and musings on how we communicate in the online age.</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:36:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Seshu</title>
		<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/comment-page-1/#comment-52845</link>
		<dc:creator>Seshu</dc:creator>
		<pubDate>Mon, 16 Jan 2006 23:43:12 +0000</pubDate>
		<guid isPermaLink="false">#comment-52845</guid>
		<description>Amy

To answer Christian&#039;s question about having a non-descript snipped URL (such as Snurl.com or TinyURL.com), I use http://urlx.org/ (this a similar online service that allows for the first part of the URL to give the user some indication of where on the Internet you are being taken. Give it a whirl!

Seshu</description>
		<content:encoded><![CDATA[<p>Amy</p>
<p>To answer Christian&#8217;s question about having a non-descript snipped URL (such as Snurl.com or TinyURL.com), I use <a href="http://urlx.org/" rel="nofollow">http://urlx.org/</a> (this a similar online service that allows for the first part of the URL to give the user some indication of where on the Internet you are being taken. Give it a whirl!</p>
<p>Seshu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alicia McBride</title>
		<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/comment-page-1/#comment-52080</link>
		<dc:creator>Alicia McBride</dc:creator>
		<pubDate>Fri, 13 Jan 2006 20:24:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-52080</guid>
		<description>Thanks for the suggestions on this issue - I&#039;m responsible for sending the e-newsletters for my organization and I&#039;ve been looking for ideas about best practices on doing links for a while. Judging from the e-newsletters I receive, there&#039;s no consensus on the best way to do links.

Our audience tends to be older and have older machines and email setups - so in our HTML email I usually leave the URLs visible but clickable.  Aesthetically it bothers me but anecdotally we hear from people when we embed the links that they can&#039;t get them to work and without a URL they can&#039;t cut and paste something into a browser.  It seems like overkill to both embed the link and list the URL, so we just leave the URLs hanging out.</description>
		<content:encoded><![CDATA[<p>Thanks for the suggestions on this issue &#8211; I&#8217;m responsible for sending the e-newsletters for my organization and I&#8217;ve been looking for ideas about best practices on doing links for a while. Judging from the e-newsletters I receive, there&#8217;s no consensus on the best way to do links.</p>
<p>Our audience tends to be older and have older machines and email setups &#8211; so in our HTML email I usually leave the URLs visible but clickable.  Aesthetically it bothers me but anecdotally we hear from people when we embed the links that they can&#8217;t get them to work and without a URL they can&#8217;t cut and paste something into a browser.  It seems like overkill to both embed the link and list the URL, so we just leave the URLs hanging out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Figart</title>
		<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/comment-page-1/#comment-51901</link>
		<dc:creator>Mark Figart</dc:creator>
		<pubDate>Thu, 12 Jan 2006 16:03:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-51901</guid>
		<description>I personally prefer to see links embedded in HTML-based emails.  Unfortunately, such links are often overlooked in scenarios where the majority of readers are not web savvy.  So if the purpose of a link is specific and important -- more than just an item of convenience -- then we find it sometimes pays to also include the url, spelled out in its entirety.  Whether the url is displayed beside the embedded link -- in parenthesis, for example -- or some other way, it can make a big difference in click-through percentages.</description>
		<content:encoded><![CDATA[<p>I personally prefer to see links embedded in HTML-based emails.  Unfortunately, such links are often overlooked in scenarios where the majority of readers are not web savvy.  So if the purpose of a link is specific and important &#8212; more than just an item of convenience &#8212; then we find it sometimes pays to also include the url, spelled out in its entirety.  Whether the url is displayed beside the embedded link &#8212; in parenthesis, for example &#8212; or some other way, it can make a big difference in click-through percentages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy Gahran</title>
		<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/comment-page-1/#comment-51895</link>
		<dc:creator>Amy Gahran</dc:creator>
		<pubDate>Thu, 12 Jan 2006 14:33:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-51895</guid>
		<description>That&#039;s a good point, Christian.

Well, for years when I was manually producing the content for my Contentious e-mail alerts, I included SnipURL redirects instead of full-length URLs to avoid presenting links that would break across lines in e-mail readers and therefore fail to function.

That didn&#039;t seem to hurt my readership at all. With each e-mail alert, I&#039;d get lots of clickthroughs. 

I do know that most of the people who get my e-mail alerts tend to be one the nongeeky end of the spectrum -- that&#039;s why the prefer e-mail alerts to feeds. However, I don&#039;t know how typical their behavior is. Most of those people signed up for my e-mail alerts years ago and I&#039;ve built a history of trust with them.

If you think your e-mail newsletter audience might be concerned about the safety of clicking on redirect URLs, then clarify in the newsletter header what they are. For instance, your header could say, &quot;I used the SnipURL service to create URLs that are short enough to work well in your e-mail reader. However, these links will take you to the correct destination. They are not spam or viruses.&quot;

... I dunno, what do you think about this approach?

- Amy Gahran</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good point, Christian.</p>
<p>Well, for years when I was manually producing the content for my Contentious e-mail alerts, I included SnipURL redirects instead of full-length URLs to avoid presenting links that would break across lines in e-mail readers and therefore fail to function.</p>
<p>That didn&#8217;t seem to hurt my readership at all. With each e-mail alert, I&#8217;d get lots of clickthroughs. </p>
<p>I do know that most of the people who get my e-mail alerts tend to be one the nongeeky end of the spectrum &#8212; that&#8217;s why the prefer e-mail alerts to feeds. However, I don&#8217;t know how typical their behavior is. Most of those people signed up for my e-mail alerts years ago and I&#8217;ve built a history of trust with them.</p>
<p>If you think your e-mail newsletter audience might be concerned about the safety of clicking on redirect URLs, then clarify in the newsletter header what they are. For instance, your header could say, &#8220;I used the SnipURL service to create URLs that are short enough to work well in your e-mail reader. However, these links will take you to the correct destination. They are not spam or viruses.&#8221;</p>
<p>&#8230; I dunno, what do you think about this approach?</p>
<p>- Amy Gahran</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Spannagel</title>
		<link>http://www.contentious.com/2006/01/11/online-newsletters-how-to-present-links/comment-page-1/#comment-51777</link>
		<dc:creator>Christian Spannagel</dc:creator>
		<pubDate>Thu, 12 Jan 2006 06:54:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-51777</guid>
		<description>Hi Amy! I fully agree with you. 

Perhaps some readers are afraid of clicking on a tinyurl-link, because they don&#039;t know which page they are forwared to (in days of spam, viruses and trojan horses, you have to be careful :-) ).

Do you have experiences with tiny links? Or do you know how people can be assured that the link is ok?

Have a nice day,

  Christian</description>
		<content:encoded><![CDATA[<p>Hi Amy! I fully agree with you. </p>
<p>Perhaps some readers are afraid of clicking on a tinyurl-link, because they don&#8217;t know which page they are forwared to (in days of spam, viruses and trojan horses, you have to be careful <img src='http://www.contentious.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  ).</p>
<p>Do you have experiences with tiny links? Or do you know how people can be assured that the link is ok?</p>
<p>Have a nice day,</p>
<p>  Christian</p>
]]></content:encoded>
	</item>
</channel>
</rss>

