Testing the Sphere related content widget
About social widgets, notice also that I have added the Sphere related content widget. This widget will show you external content related to the article you just read. Logically, you will find this widget in the “Read also” section below.
There are 2 reasons why I installed this widget. First is: some of you, dear readers, are coming here through Sphere. That is how I heard of it. Secondly, I like the name. It is related to ThinkoSphere, isn’t it ? However, I am only trying out the widget so do not hesitate to leave a comment to tell me what you think about this widget and the other ones. My impressions so far are that it slows down your blog but that is working correctly even if sometimes you really wonder why the hell this is meant to be related to your content !
Posted in Marketing | 3 comments | atom
Trackbacks
Use the following link to trackback from your own site:
http://harryseldon.thinkosphere.com/trackbacks?article_id=35
home
about
archives

Hi Harry - just wanted to give a shout that Searchles just came out with a contextual Related Content widget that actually analyzes your text to match related posts from your archive - Sphere brings in outside links, yes? We’d love to have you test it out and let us know what you think. We just added SEO advantages to installation too!
http://searchles.com/misc/platform
Cheers, Kim
@Kim, as you may notice, I removed the widget. My main concern was the loading time. It was not that bad but as it looks like only a few people were using it I preferred to remove it.
The fact that Sphere was bringing outside link was not a problem for me, as long as it is actually related content which was not always obvious.
I will have a look at searchles, if it can help in SEO it is good to take, as long as it does not kill the loading time.
Hi Harry, I am also from Searchles, and I just wanted to let you know that our widget should have very little effect on your load time. We use a CDN to cache the javascript and flash files, and then we actively cache all xml content to a CDN as well. So after the first time a widget loads on a particular page, every subsequent hit will be entirely served from a CDN, which makes it very fast to load.