Overcoming Feedburner’s Ping Service Limitation

September 16, 2008, filed under Quick Internet Tips


By default, Feedburner limits ping services to 11 maximum. They are Technorati, My Yahoo, Bloglines, Newsgator, Google’s Ping Service, Ping-o-matic and 14 more options. What if you want to use them all instead of just the 11 services allowed?

I recently realized this when I made a separate feed subscription for each category in HomeBiz Recource. For each category, you can have each 11 ping services. So let’s say you have 2 categories with their own feeds and 1 main feed for the main blog, you can have more ping services! :)

Here’s some example:

http://www.homebiz.bukiki.com/feed —>11 services, 6 default + 5 optionals (service A, B, C, D, E)

http://www.homebiz.bukiki.com/category/blogging/feed —>11 services, 6 default + 5 optionals (service F, G, H, I, J)

http://www.homebiz.bukiki.com/category/quicktips/feed —>11 services, 6 default + 5 optionals (service K, B, H, D, A)

So if you post an article in the blogging category, Feedburner will ping to the 6 default services plus A, B, C, D, E, F, G, H, I, J. Am I right? :)

Read more:
Resolving The Feed Too Large Error Just now I reviewed my web crawl errors using Google...
Feed Error! Source Feed is Too Large… …maximum size is 512K. This is the error I was...
Blogging – HomeBiz Resource Auto Theme Change Solution After my recent post on how I thought the problem...
How to Display Only Posts from Certain Categories on Your Mainpage and Feeds The hack will enable you to select which categories will...

Tell others about the article!

Add to Mixx!

Fast and semi auto bookmark to 45 social bookmarking services!
Let me send you free updates!

What people say

»


Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!
 

Author / Blog Name
E-mail (optional)
URI
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.



<<         >>

|