Hi all. I've been thinking about RSS a ton recently in relation to back-links. I know many people use RSS from their blogs as a way to build links in addition to the normal syndication objecctive. They normally run around and register their RSS feed in as many free RSS directories as possible. There are two main benefits to this approach: 1) People may come by your feed and decide to subscribe to it directly. 2) At *some* rss directory sites, your feed is actually rendered as an HTML page on their domain - thus providing back-links to your blog/site. I've researched this a bunch and have a guarded list of the RSS directory sites that render your feed as an HTML page - you probably do also. The few of these that actually have high page rank are extremely valuable. They can be used in many interesting ways for SEO... Good stuff. But here's what I've been thinking. Why are there not RSS networks? Perhaps there are but I don't know about them. By RSS network, I mean a site where you can register your RSS feed and have each entry shipped out to a different website with a static html page for that specific entry. In other words, if your current RSS file had 10 entries in it, by registering in one single place, you could get 10 different back-links - 1 per entry in your RSS feed. Since each page will have the content from your rss entry on it, it can be keyword rich and the backlink will be relevant. Does this exist? Has anyone seen such a thing? If not - I am thinking about building one. The only problem I see is that, at the beginning, the sites would not carry any page rank. So there would need to be some form of link trade involved. Question: If you were able to get 10 back-links from different class C IP sites from a single RSS registration, would that be worth paying a small amount for (like a few bucks)? If not: Would the same service be worth building a link for? Perhaps it could work this way. You register your RSS, but it is not syndicated to the RSS network until you build 3 inbound links to one of the sites in the network. These could be from other blogs (not the source of the feed to avoid reciprocal linking) or from social bookmark sites - whatever. Fair? If interested in this idea, leave a note here. I have all the pieces I need to build this in about 4 hours. But without a group of people interested in launching it - it's not worth doing. Cheers.
I would consider it but I would wait until i saw some page rank. This would signal that Google is approving it in my mind. (happy to hear your thoughts) Also, I've seen this mentioned on other threads - I'm not convinced a separate C class actually provides a benefit anymore after asking in several forums. That said, I can't prove it. Are you sure that separate C class is still important. Thanks and good luck with your project.
Thanks for the thoughts... To answer your question: I don't really know if different class C's are important any more. But I know it *can't* hurt. On your other point re: Poor page rank at the beginning - Yeah, that's the problem with all new projects. Although, I pushed a site up to PR7 in 6 months last year, so I was thinking I could use the same approach here if there was interest. Any other thoughts on the RSS network idea?
There are a huge number of RSS search engines and directories the majority of which display the feeds as HTML. Here is a list of places you can submit your RSS feed to: http://www.rss-specifications.com/rss-submission.htm You may want to occassionally use links back to your website in the description of the feed items as well.
Yes. Yes.. Thanks... I will review your list and compare to mine... BUT - This discussion here is about a NETWORK of RSS sites... If you read above, I'm talking about a method by which your feed would be taken in at one site, and then each entry sent to different sites for back-links. The idea here is that it would save TONS of time because you don't need to run around and register at each of these sites.
They did something similar with downloadable software. They created a standard called "PAD" which was an XML file that contained all of the software's information (name, version, file size, description etc...) the idea was that it would save developers time submitting to all the download sites by using a PAD repository. There was a fair amount of adoption, but there were also a lot of unforseen problems that came up as a result. The repository would have to have a way to easily group or categorize the feeds.