<?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: On backlinking (or &#8220;internal linking&#8221;)</title>
	<atom:link href="http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/</link>
	<description>Editor and technology critic in the midst of founding a new content startup.</description>
	<pubDate>Thu, 04 Dec 2008 21:25:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-RC1-10026</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Internal Linking Explained</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-49389</link>
		<dc:creator>Internal Linking Explained</dc:creator>
		<pubDate>Sun, 21 Oct 2007 00:53:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-49389</guid>
		<description>[...] Taken Over Annoying Internal Linking Trend Sleazy Linkers Lose An Ally Linking: a plea to bloggers On backlinking (or “internal linking”) Bloggers Double Linking When complaining about internal links don’t forget Wikipedia Never Fool [...]</description>
		<content:encoded><![CDATA[<p>[...] Taken Over Annoying Internal Linking Trend Sleazy Linkers Lose An Ally Linking: a plea to bloggers On backlinking (or “internal linking”) Bloggers Double Linking When complaining about internal links don’t forget Wikipedia Never Fool [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dagens, 14/09 / mblogg.se</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46831</link>
		<dc:creator>Dagens, 14/09 / mblogg.se</dc:creator>
		<pubDate>Fri, 14 Sep 2007 13:41:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46831</guid>
		<description>[...] On backlinking (or “internal linking”) [...]</description>
		<content:encoded><![CDATA[<p>[...] On backlinking (or “internal linking”) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Block</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46803</link>
		<dc:creator>Ryan Block</dc:creator>
		<pubDate>Fri, 14 Sep 2007 05:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46803</guid>
		<description>Fred, that's actually not so. There are sometimes counter examples, but statistically more than 50% of our links in our posts are outbound.</description>
		<content:encoded><![CDATA[<p>Fred, that&#8217;s actually not so. There are sometimes counter examples, but statistically more than 50% of our links in our posts are outbound.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46775</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Thu, 13 Sep 2007 19:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46775</guid>
		<description>I was sort of buying your explanation until the last sentence: "Obviously not, that’s why the majority of links in our content point outward, not inward." On the current Engadget front page, there are 16 outbound links, and 27 internal links. You're free to link to whomever and whatever you want, of course, but that last sentence doesn't appear to be true. I've developed a sort of mental block with Engadget posts - links within the body of the post are always internal, and at least half the time just links to tags or searches, so I just ignore them.</description>
		<content:encoded><![CDATA[<p>I was sort of buying your explanation until the last sentence: &#8220;Obviously not, that’s why the majority of links in our content point outward, not inward.&#8221; On the current Engadget front page, there are 16 outbound links, and 27 internal links. You&#8217;re free to link to whomever and whatever you want, of course, but that last sentence doesn&#8217;t appear to be true. I&#8217;ve developed a sort of mental block with Engadget posts - links within the body of the post are always internal, and at least half the time just links to tags or searches, so I just ignore them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zhasper</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46747</link>
		<dc:creator>Zhasper</dc:creator>
		<pubDate>Thu, 13 Sep 2007 12:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46747</guid>
		<description>I've re-read comment #1, and I'm wrong about what Luis was referring to. I think I'm correct about what other people are upset about though.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve re-read comment #1, and I&#8217;m wrong about what Luis was referring to. I think I&#8217;m correct about what other people are upset about though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James D Kirk</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46731</link>
		<dc:creator>James D Kirk</dc:creator>
		<pubDate>Thu, 13 Sep 2007 06:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46731</guid>
		<description>Thanks Ryan for your follow up to Louis' post. I posted at his site that I thought a lot of the internal linking was all about increasing ones page rank in the SE's. I still believe that, and while I'm not as versed on the minutia of what is a "Best Practices" of linking, one only has to do a link report on this page to see that you have a 34 to 31 internal to external ration of links. I'd think that to be a good balance. 
@Veronica, I also agree that quality back links can be helpful and one of those reasons I prefer to read a story online with all the hyper linking possibilities versus reading a paper or magazine article. I don't however know how happy I'd be to click an internal link and be taken to a search results page.

Nonetheless, my main take aways are that internal linking, when done prudently and to add value to a story, are great and acceptable. I am also going to do my best to start incorporating the [VIA source_link] as well. I already perform little screen grabs of some important element from a source site (something like their logo, or if they have a remarkable image for a given story) and make sure I am linking that back to the story as well.</description>
		<content:encoded><![CDATA[<p>Thanks Ryan for your follow up to Louis&#8217; post. I posted at his site that I thought a lot of the internal linking was all about increasing ones page rank in the SE&#8217;s. I still believe that, and while I&#8217;m not as versed on the minutia of what is a &#8220;Best Practices&#8221; of linking, one only has to do a link report on this page to see that you have a 34 to 31 internal to external ration of links. I&#8217;d think that to be a good balance.<br />
@Veronica, I also agree that quality back links can be helpful and one of those reasons I prefer to read a story online with all the hyper linking possibilities versus reading a paper or magazine article. I don&#8217;t however know how happy I&#8217;d be to click an internal link and be taken to a search results page.</p>
<p>Nonetheless, my main take aways are that internal linking, when done prudently and to add value to a story, are great and acceptable. I am also going to do my best to start incorporating the [VIA source_link] as well. I already perform little screen grabs of some important element from a source site (something like their logo, or if they have a remarkable image for a given story) and make sure I am linking that back to the story as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zhasper</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46729</link>
		<dc:creator>Zhasper</dc:creator>
		<pubDate>Thu, 13 Sep 2007 06:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46729</guid>
		<description>generally speaking we expect them to understand the jist of what we’re talking about 

I understand that you're talking about the gist... but what's a spelling mistake between friends?

I think you're misunderstanding what people are upset about. Take, as an example, your &lt;a href="http://www.engadget.com/2007/09/13/sandisk-to-benefit-alzheimers-association-with-purple-flash-sto/" rel="nofollow"&gt;story about Sandisk donating to the Alzheimers Association&lt;/a&gt;. You don't even have to click on that link to know where it goes, because it describes itself.

In contrast, your story has a link on the word "Sandisk". Given that it's a story about Sandisk, and given that the link is on the word "Sandisk", I'd assume that the link takes me to Sandisk's website. Given your claim above that your internal links are to useful previous editorial, I'd expect it to link to a previous useful editorial. But, it does neither - it just links to all stories you've ever written tagged with Sandisk.

You're not conforming to they way most people use links, and because of that, your site doesn't do what I expect, and because of that, I have a poor user experience on your site.

You're not conforming to your own claims about how your site behaves - if it did conform to your claims, that user experience would be marginally better than what actually happens.

This is why I don't bother reading your site. Any interesting news you have gets reposted elsewhere, on sites that have links that do what I expect and don't take me to useless index pages.</description>
		<content:encoded><![CDATA[<p>generally speaking we expect them to understand the jist of what we’re talking about </p>
<p>I understand that you&#8217;re talking about the gist&#8230; but what&#8217;s a spelling mistake between friends?</p>
<p>I think you&#8217;re misunderstanding what people are upset about. Take, as an example, your <a href="http://www.engadget.com/2007/09/13/sandisk-to-benefit-alzheimers-association-with-purple-flash-sto/" rel="nofollow">story about Sandisk donating to the Alzheimers Association</a>. You don&#8217;t even have to click on that link to know where it goes, because it describes itself.</p>
<p>In contrast, your story has a link on the word &#8220;Sandisk&#8221;. Given that it&#8217;s a story about Sandisk, and given that the link is on the word &#8220;Sandisk&#8221;, I&#8217;d assume that the link takes me to Sandisk&#8217;s website. Given your claim above that your internal links are to useful previous editorial, I&#8217;d expect it to link to a previous useful editorial. But, it does neither - it just links to all stories you&#8217;ve ever written tagged with Sandisk.</p>
<p>You&#8217;re not conforming to they way most people use links, and because of that, your site doesn&#8217;t do what I expect, and because of that, I have a poor user experience on your site.</p>
<p>You&#8217;re not conforming to your own claims about how your site behaves - if it did conform to your claims, that user experience would be marginally better than what actually happens.</p>
<p>This is why I don&#8217;t bother reading your site. Any interesting news you have gets reposted elsewhere, on sites that have links that do what I expect and don&#8217;t take me to useless index pages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davis Freeberg</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46723</link>
		<dc:creator>Davis Freeberg</dc:creator>
		<pubDate>Thu, 13 Sep 2007 02:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46723</guid>
		<description>I think that you're brave for addressing the criticism, but don't think you should dismiss it quite so quickly.  It's true that Engadget has always linked back to their own content, but in the past it was less frequent and was only for relevant articles that directly addressed the issue being discussed.  

I don't know when the "keyword" links started showing up, but started noticing them right before AOL took over.  If you can't at least point to something specific in the story, it seems kind of lazy to offer a catch all under the disguise of "background link." 

As an example, today Engadget linked to the term "Ice Cream" in a story.  The link sends your readers to an Engadget search result for any story that has ever used the term ice cream.  The 2nd link in the article to another specific Engadget ice cream story I get, but is the search results link really background for your smarter than average readers or is this really just smart SEO?  I think it's a distraction at the bare minimum.  

I couldn't find an archive of your 2003/04 content on the site, but if you look at the 04' results on archive.org and count the self links, you can tell that they were there, but only to stories that added value.  At initial glance it looks like in 04', Engadget was putting in about one link back to their site on every other post.

http://web.archive.org/web/20040815005612/http://engadget.com/

Now, it's at least two (or three) links per article and one of those links usually goes to a keyword search result, instead of to a specific piece of content that helps puts the story being discussed into perspective.

I don't really care who you guys want to link to and you do publish so much content that it's nice to be able to travel deeper and deeper into your commentary, but it's kind of obnoxious when you click a link and there is no real payoff for the reader.  If this helps pay for the content, than so be it, but I don't think that you should cite precedence as a reason to avoid taking a more serious look at the practice.  

Before linking to anything, the author should be at least taking the time to ask themselves if it adds to the story or not.  If it doesn't then why not leave it out or find a specific Engadget story that discusses the topic?  Engadget has a lot of great content and linking back to it does help me to catch stuff that I've missed, but it's the links that are choosen by an editor that provide real value, if I want to see search results, I've got computers that can help me find them.</description>
		<content:encoded><![CDATA[<p>I think that you&#8217;re brave for addressing the criticism, but don&#8217;t think you should dismiss it quite so quickly.  It&#8217;s true that Engadget has always linked back to their own content, but in the past it was less frequent and was only for relevant articles that directly addressed the issue being discussed.  </p>
<p>I don&#8217;t know when the &#8220;keyword&#8221; links started showing up, but started noticing them right before AOL took over.  If you can&#8217;t at least point to something specific in the story, it seems kind of lazy to offer a catch all under the disguise of &#8220;background link.&#8221; </p>
<p>As an example, today Engadget linked to the term &#8220;Ice Cream&#8221; in a story.  The link sends your readers to an Engadget search result for any story that has ever used the term ice cream.  The 2nd link in the article to another specific Engadget ice cream story I get, but is the search results link really background for your smarter than average readers or is this really just smart SEO?  I think it&#8217;s a distraction at the bare minimum.  </p>
<p>I couldn&#8217;t find an archive of your 2003/04 content on the site, but if you look at the 04&#8242; results on archive.org and count the self links, you can tell that they were there, but only to stories that added value.  At initial glance it looks like in 04&#8242;, Engadget was putting in about one link back to their site on every other post.</p>
<p><a href="http://web.archive.org/web/20040815005612/http://engadget.com/" rel="nofollow">http://web.archive.org/web/20040815005612/http://engadget.com/</a></p>
<p>Now, it&#8217;s at least two (or three) links per article and one of those links usually goes to a keyword search result, instead of to a specific piece of content that helps puts the story being discussed into perspective.</p>
<p>I don&#8217;t really care who you guys want to link to and you do publish so much content that it&#8217;s nice to be able to travel deeper and deeper into your commentary, but it&#8217;s kind of obnoxious when you click a link and there is no real payoff for the reader.  If this helps pay for the content, than so be it, but I don&#8217;t think that you should cite precedence as a reason to avoid taking a more serious look at the practice.  </p>
<p>Before linking to anything, the author should be at least taking the time to ask themselves if it adds to the story or not.  If it doesn&#8217;t then why not leave it out or find a specific Engadget story that discusses the topic?  Engadget has a lot of great content and linking back to it does help me to catch stuff that I&#8217;ve missed, but it&#8217;s the links that are choosen by an editor that provide real value, if I want to see search results, I&#8217;ve got computers that can help me find them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: veronica</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46687</link>
		<dc:creator>veronica</dc:creator>
		<pubDate>Wed, 12 Sep 2007 21:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46687</guid>
		<description>In the case of Engadget, I actually find backlinking to be incredibly useful. Since there's so much content and information, I often find it hard to keep up, so when I land on a particular story the backlinking enables me to get the full scoop. I don't HAVE to use Google, or further search Engadget, to get the background information.</description>
		<content:encoded><![CDATA[<p>In the case of Engadget, I actually find backlinking to be incredibly useful. Since there&#8217;s so much content and information, I often find it hard to keep up, so when I land on a particular story the backlinking enables me to get the full scoop. I don&#8217;t HAVE to use Google, or further search Engadget, to get the background information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eliot</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46681</link>
		<dc:creator>Eliot</dc:creator>
		<pubDate>Wed, 12 Sep 2007 20:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46681</guid>
		<description>I've noticed Engadget linking to a lot of tag pages. I don't mind this with something as ubiquitous as the Xbox 360. When Sony launches a new model in some obscure laptop line though I think I'd prefer it go to a definitive post about the line instead of posts tagged as part of that line.  Sometimes it's just a toss up though: Do I want to see all Santa Rosa laptops or the definitive post on why I should care about Santa Rosa.

Lack of outbound linking? Meh. Engadget is the best resource when it comes to most of these topics. I think I'd be more annoyed if I had to trudge through someone elses site when all I'm doing is investigating a secondary link.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve noticed Engadget linking to a lot of tag pages. I don&#8217;t mind this with something as ubiquitous as the Xbox 360. When Sony launches a new model in some obscure laptop line though I think I&#8217;d prefer it go to a definitive post about the line instead of posts tagged as part of that line.  Sometimes it&#8217;s just a toss up though: Do I want to see all Santa Rosa laptops or the definitive post on why I should care about Santa Rosa.</p>
<p>Lack of outbound linking? Meh. Engadget is the best resource when it comes to most of these topics. I think I&#8217;d be more annoyed if I had to trudge through someone elses site when all I&#8217;m doing is investigating a secondary link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internal/Double Linking is a Bad Practice : The Last Podcast</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46671</link>
		<dc:creator>Internal/Double Linking is a Bad Practice : The Last Podcast</dc:creator>
		<pubDate>Wed, 12 Sep 2007 19:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46671</guid>
		<description>[...] 2: Ryan Block of Engadget also added some of his own [...]</description>
		<content:encoded><![CDATA[<p>[...] 2: Ryan Block of Engadget also added some of his own [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Gray</title>
		<link>http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/comment-page-1/#comment-46669</link>
		<dc:creator>Louis Gray</dc:creator>
		<pubDate>Wed, 12 Sep 2007 19:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.ryanblock.com/2007/09/on-backlinking-or-internal-linking/#comment-46669</guid>
		<description>Ryan, thanks for your response and your notes. I have seen Engadget's linkage at the bottom, and while your site was lumped in with Mashable in this case, it was their story primarily that pushed me to respond.

My Engadget fandom doesn't fade due to a definition of backlinks by any means, and I understand the "It's an easy Google" comment. Your readers know apple.com and google.com and xbox.com for sure. But I don't know if when they click on Apple or Google or Xbox within Engadget that they are looking for prior coverage. It's also more of an issue with new companies who I haven't heard of except through Engadget, where I will need to go to Google instead of right to their site from yours than it is with the aforementioned leaders.

I appreciate the discussion and hope to see more opinions and conversation. And... keep up the great work.</description>
		<content:encoded><![CDATA[<p>Ryan, thanks for your response and your notes. I have seen Engadget&#8217;s linkage at the bottom, and while your site was lumped in with Mashable in this case, it was their story primarily that pushed me to respond.</p>
<p>My Engadget fandom doesn&#8217;t fade due to a definition of backlinks by any means, and I understand the &#8220;It&#8217;s an easy Google&#8221; comment. Your readers know apple.com and google.com and xbox.com for sure. But I don&#8217;t know if when they click on Apple or Google or Xbox within Engadget that they are looking for prior coverage. It&#8217;s also more of an issue with new companies who I haven&#8217;t heard of except through Engadget, where I will need to go to Google instead of right to their site from yours than it is with the aforementioned leaders.</p>
<p>I appreciate the discussion and hope to see more opinions and conversation. And&#8230; keep up the great work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
