<?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: Social Sharing: How To Optimize Page Titles To Generate More Clickable Links To Your Website	</title>
	<atom:link href="https://www.searchenginepeople.com/blog/social-sharing-optimization.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html?utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Canada&#039;s Search and Social Media Authority</description>
	<lastBuildDate>Fri, 31 May 2013 16:01:30 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Kristof		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71288</link>

		<dc:creator><![CDATA[Kristof]]></dc:creator>
		<pubDate>Tue, 12 Apr 2011 01:13:24 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71288</guid>

					<description><![CDATA[Dr. Michael -- a quick update regarding SEO benefit from using shorlinks; SearchEngineJournal posted this article, &quot;Google Clarifies URL Shortening’s Impact on SEO&quot; http://bit.ly/dPgPWL

In short, Google treats shortlinks as being a link for the sake of pagerank – to the destination.]]></description>
			<content:encoded><![CDATA[<p>Dr. Michael &#8212; a quick update regarding SEO benefit from using shorlinks; SearchEngineJournal posted this article, &#8220;Google Clarifies URL Shortening’s Impact on SEO&#8221; <a href="http://bit.ly/dPgPWL" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://bit.ly/dPgPWL</a></p>
<p>In short, Google treats shortlinks as being a link for the sake of pagerank – to the destination.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kristof		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71253</link>

		<dc:creator><![CDATA[Kristof]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 18:50:56 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71253</guid>

					<description><![CDATA[Hi Dr. Michael - Thanks for your comment, you bring up a lot of different points.

I agree, it&#039;s both shorter and less confusing to use a non &quot;www&quot; address. It&#039;s just a matter of choosing to use it and including the proper code in the site htaccess file to ensure everything points to the right place. It always amazes me how many sites don&#039;t make a conscience decision about which one to use, and then one or the other leads to an error page or doesn&#039;t connect at all.

Stuffing a domain with keywords does make it longer and can look spammy but exact domain matches do have there good points. Here are a few articles on the subject. Take a read and decide for yourself.

&quot;Branded vs Keyword-Rich Domain Names&quot;
http://bit.ly/fBs582

&quot;Should You Buy An Exact Match Domain Name?&quot;
http://bit.ly/ejP1E7

&quot;Why exact domain matches rank so well&quot;
http://selnd.com/e83D2I

As Ruud mentioned above, there are scripts available (like lessn) to create your own URL shortener, but you can always use your own domain through bit.ly with less setup and get analytics too. But whether you roll your own of use a custom domain name through a service, both will help with increasing brand awareness. For example, the short URL for the last article listed above is for Search Engine Land.

I don&#039;t see a downside in using a URL shortener through another service in creating links, even if it goes through their site first. A shortened URL main purposes if to reduce number of characters used in social media sharing. And, if you look at this article &quot;How Is Twitter Impacting Search and SEO?&quot; http://bit.ly/f9qbYr you&#039;ll see that regardless of who the link is through, Google is taking note.

Thanks for your thoughts on this.]]></description>
			<content:encoded><![CDATA[<p>Hi Dr. Michael &#8211; Thanks for your comment, you bring up a lot of different points.</p>
<p>I agree, it&#8217;s both shorter and less confusing to use a non &#8220;www&#8221; address. It&#8217;s just a matter of choosing to use it and including the proper code in the site htaccess file to ensure everything points to the right place. It always amazes me how many sites don&#8217;t make a conscience decision about which one to use, and then one or the other leads to an error page or doesn&#8217;t connect at all.</p>
<p>Stuffing a domain with keywords does make it longer and can look spammy but exact domain matches do have there good points. Here are a few articles on the subject. Take a read and decide for yourself.</p>
<p>&#8220;Branded vs Keyword-Rich Domain Names&#8221;<br />
<a href="http://bit.ly/fBs582" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://bit.ly/fBs582</a></p>
<p>&#8220;Should You Buy An Exact Match Domain Name?&#8221;<br />
<a href="http://bit.ly/ejP1E7" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://bit.ly/ejP1E7</a></p>
<p>&#8220;Why exact domain matches rank so well&#8221;<br />
<a href="http://selnd.com/e83D2I" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://selnd.com/e83D2I</a></p>
<p>As Ruud mentioned above, there are scripts available (like lessn) to create your own URL shortener, but you can always use your own domain through bit.ly with less setup and get analytics too. But whether you roll your own of use a custom domain name through a service, both will help with increasing brand awareness. For example, the short URL for the last article listed above is for Search Engine Land.</p>
<p>I don&#8217;t see a downside in using a URL shortener through another service in creating links, even if it goes through their site first. A shortened URL main purposes if to reduce number of characters used in social media sharing. And, if you look at this article &#8220;How Is Twitter Impacting Search and SEO?&#8221; <a href="http://bit.ly/f9qbYr" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://bit.ly/f9qbYr</a> you&#8217;ll see that regardless of who the link is through, Google is taking note.</p>
<p>Thanks for your thoughts on this.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dr. Michael Haley		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71230</link>

		<dc:creator><![CDATA[Dr. Michael Haley]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 16:32:55 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71230</guid>

					<description><![CDATA[I agree the URL&#039;s will be converted more and more in social media (and more). but just in case, I choose to use the http://drhaley.com (without the www) because it is shorter. Maybe we should all make that the preferred form of our URL&#039;s for creating backlinks and the like. Also, one of your examples references an article that says it is not smart to stuff keywords into domains. Stuffing keywords into the TLD name also makes it longer - which again is a problem. It probably makes sense to have a short URL and then use your own &quot;pretty link&quot; or the likes of - instead of link shorteners. If you think about it, everytime you use a shortlink you are actually making a link to someone elses domain - which probably has no SEO benefit to you. To drive the point home, I just made the pretty link: http://drhaley.com/1 which is only long because I have a long URL. It took me 20 charachters + 1 for the space after it. But I can keep the part after the slash quite short because only I use this link shortening service... not the whole world! Everyone with their own domain can choose to do the same thing making their short url&#039;s point to their own domain. What do you think?]]></description>
			<content:encoded><![CDATA[<p>I agree the URL&#8217;s will be converted more and more in social media (and more). but just in case, I choose to use the <a href="http://drhaley.com" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://drhaley.com</a> (without the www) because it is shorter. Maybe we should all make that the preferred form of our URL&#8217;s for creating backlinks and the like. Also, one of your examples references an article that says it is not smart to stuff keywords into domains. Stuffing keywords into the TLD name also makes it longer &#8211; which again is a problem. It probably makes sense to have a short URL and then use your own &#8220;pretty link&#8221; or the likes of &#8211; instead of link shorteners. If you think about it, everytime you use a shortlink you are actually making a link to someone elses domain &#8211; which probably has no SEO benefit to you. To drive the point home, I just made the pretty link: <a href="http://drhaley.com/1" rel="ugc nofollow external noopener noreferrer" data-wpel-link="external" target="_blank" class="ext-link">http://drhaley.com/1</a> which is only long because I have a long URL. It took me 20 charachters + 1 for the space after it. But I can keep the part after the slash quite short because only I use this link shortening service&#8230; not the whole world! Everyone with their own domain can choose to do the same thing making their short url&#8217;s point to their own domain. What do you think?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kristof		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71221</link>

		<dc:creator><![CDATA[Kristof]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 13:48:26 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71221</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71116&quot;&gt;Annemarie Cross&lt;/a&gt;.

Hi Annemarie - thank you for your kind comment.

Although I knew about auto linking, it didn&#039;t really hit me until I saw the adverse effect it can have. When I tweeted an article from SEOBook.com, I noticed the domain in the page title was written as two words &quot;SEO Book.com&quot;, and the Book.com was auto linking to Barnes and Noble. Probably not what the author intended.

I&#039;m looking forward to reading your blog.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71116" data-wpel-link="internal">Annemarie Cross</a>.</p>
<p>Hi Annemarie &#8211; thank you for your kind comment.</p>
<p>Although I knew about auto linking, it didn&#8217;t really hit me until I saw the adverse effect it can have. When I tweeted an article from SEOBook.com, I noticed the domain in the page title was written as two words &#8220;SEO Book.com&#8221;, and the Book.com was auto linking to Barnes and Noble. Probably not what the author intended.</p>
<p>I&#8217;m looking forward to reading your blog.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ruud Hein		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71213</link>

		<dc:creator><![CDATA[Ruud Hein]]></dc:creator>
		<pubDate>Mon, 11 Apr 2011 13:23:34 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71213</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71116&quot;&gt;Annemarie Cross&lt;/a&gt;.

What I love from bit.ly, too, is that you can use your own domain name for it. I bought ruudhe.in for example. True, there are scripts out there that let you do the same thing but this is a no-hassle, free solution.

Thanks for dropping by Annemarie. Nice blog you have going yourself; loved the time management posts.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71116" data-wpel-link="internal">Annemarie Cross</a>.</p>
<p>What I love from bit.ly, too, is that you can use your own domain name for it. I bought ruudhe.in for example. True, there are scripts out there that let you do the same thing but this is a no-hassle, free solution.</p>
<p>Thanks for dropping by Annemarie. Nice blog you have going yourself; loved the time management posts.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Annemarie Cross		</title>
		<link>https://www.searchenginepeople.com/blog/social-sharing-optimization.html/comment-page-1#comment-71116</link>

		<dc:creator><![CDATA[Annemarie Cross]]></dc:creator>
		<pubDate>Sun, 10 Apr 2011 20:38:01 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=12963#comment-71116</guid>

					<description><![CDATA[A great article Michael! I use bit.ly as well - I love the tracking feature to see how many people are clicking and sharing. 

As you have mentioned, branding is vital and following your great instructions will allow us to share great content while also building brand awareness.

Great stuff!]]></description>
			<content:encoded><![CDATA[<p>A great article Michael! I use bit.ly as well &#8211; I love the tracking feature to see how many people are clicking and sharing. </p>
<p>As you have mentioned, branding is vital and following your great instructions will allow us to share great content while also building brand awareness.</p>
<p>Great stuff!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
