For the past week or so, I have decided to go through my sites and find out whats working for me and whats not!
And one of the first things I found was *a lot* of the ping sites I had in my wordpress ping list where not working anymore.
So I decided to go through my big list of ping servers and find out what was working and whats wasn’t.
A couple of things jumped out straight away:
1. Both technorati and Yahoo.com are no longer accepting pings.
Technorati has this announcement on their website (http://technorati.com/ping/) and the yahoo server, that most of us use for ping is no longer active.
So I would suggest you edit your ping list and remove those two sites, and all variations of them.
Even two of the Google ping servers (.ie and .in no longer accept pings)
So after many days of testing sites, I have eventually come up with a ping list that now contains sites that work (ie: the domains are still valid, and the ping servers report something meaningful).
Out of my list of over 150 ping sites, I ended up with the following list of 83 servers:
| http://api.moreover.com/RPC2 |
| http://audiorpc.weblogs.com/RPC2 |
| http://blog.goo.ne.jp/XMLRPC |
| http://blogsearch.google.ae/ping/RPC2 |
| http://blogsearch.google.at/ping/RPC2 |
| http://blogsearch.google.be/ping/RPC2 |
| http://blogsearch.google.bg/ping/RPC2 |
| http://blogsearch.google.ca/ping/RPC2 |
| http://blogsearch.google.ch/ping/RPC2 |
| http://blogsearch.google.cl/ping/RPC2 |
| http://blogsearch.google.co.cr/ping/RPC2 |
| http://blogsearch.google.co.hu/ping/RPC2 |
| http://blogsearch.google.co.id/ping/RPC2 |
| http://blogsearch.google.co.il/ping/RPC2 |
| http://blogsearch.google.co.jp/ping/RPC2 |
| http://blogsearch.google.co.ma/ping/RPC2 |
| http://blogsearch.google.co.nz/ping/RPC2 |
| http://blogsearch.google.co.th/ping/RPC2 |
| http://blogsearch.google.co.uk/ping/RPC2 |
| http://blogsearch.google.co.ve/ping/RPC2 |
| http://blogsearch.google.co.za/ping/RPC2 |
| http://blogsearch.google.com.ar/ping/RPC2 |
| http://blogsearch.google.com.au/ping/RPC2 |
| http://blogsearch.google.com.br/ping/RPC2 |
| http://blogsearch.google.com.co/ping/RPC2 |
| http://blogsearch.google.com.do/ping/RPC2 |
| http://blogsearch.google.com.mx/ping/RPC2 |
| http://blogsearch.google.com.my/ping/RPC2 |
| http://blogsearch.google.com.pe/ping/RPC2 |
| http://blogsearch.google.com.sa/ping/RPC2 |
| http://blogsearch.google.com.sg/ping/RPC2 |
| http://blogsearch.google.com.tr/ping/RPC2 |
| http://blogsearch.google.com.tw/ping/RPC2 |
| http://blogsearch.google.com.ua/ping/RPC2 |
| http://blogsearch.google.com.uy/ping/RPC2 |
| http://blogsearch.google.com.vn/ping/RPC2 |
| http://blogsearch.google.com/ping/RPC2 |
| http://blogsearch.google.de/ping/RPC2 |
| http://blogsearch.google.es/ping/RPC2 |
| http://blogsearch.google.fi/ping/RPC2 |
| http://blogsearch.google.fr/ping/RPC2 |
| http://blogsearch.google.gr/ping/RPC2 |
| http://blogsearch.google.hr/ping/RPC2 |
| http://blogsearch.google.ie/ping/RPC2 |
| http://blogsearch.google.jp/ping/RPC2 |
| http://blogsearch.google.lt/ping/RPC2 |
| http://blogsearch.google.nl/ping/RPC2 |
| http://blogsearch.google.pl/ping/RPC2 |
| http://blogsearch.google.pt/ping/RPC2 |
| http://blogsearch.google.ro/ping/RPC2 |
| http://blogsearch.google.ru/ping/RPC2 |
| http://blogsearch.google.se/ping/RPC2 |
| http://blogsearch.google.sk/ping/RPC2 |
| http://blogsearch.google.us/ping/RPC2 |
| http://coreblog.org/ping/ |
| http://feedsky.com/api/RPC2 |
| http://hamo-search.com/ping.php |
| http://ping.bitacoras.com |
| http://ping.blo.gs/ |
| http://ping.bloggers.jp/rpc/ |
| http://ping.blogoon.net/ |
| http://ping.blogs.yandex.ru/RPC2 |
| http://ping.fc2.com/ |
| http://ping.feedburner.com |
| http://ping.feedburner.com/ |
| http://ping.kutsulog.net/ |
| http://ping.myblog.jp/ |
| http://ping.rootblog.com/rpc.php |
| http://ping.snap.com/ping/RPC2 |
| http://ping.syndic8.com/xmlrpc.php |
| http://ping.weblogalot.com/rpc.php |
| http://rpc.blogbuzzmachine.com/RPC2 |
| http://rpc.bloggerei.de/ping/ |
| http://rpc.blogrolling.com/pinger/ |
| http://rpc.icerocket.com:10080/ |
| http://rpc.reader.livedoor.com/ping |
| http://rpc.weblogs.com/RPC2 |
| http://wasalive.com/ping/ |
| http://www.blogdigger.com/RPC2 |
| http://www.blogoole.com/ping/ |
| http://www.blogoon.net/ping/ |
| http://xping.pubsub.com/ping/ |
| http://zhuaxia.com/rpc/server.php |
You can include Ping-O-matic.com if you wish, but I have found pingomatic to be unreliable at times, so I basically ignore it and post directly to the sites that matter.
Tags: google, ping, ping server, pinging, pingomatic, pings, xmlrpc
Hi Bruce, thanks for providing this up to date list. Just what I was looking for. Great stuff!
However, thought I would let you know I loaded it into Excel spreadsheet, sorted alphabetically, then used the Data>Remove Duplicates option and it removed several duplicate entries.
Also did you do any checking for duplicate pings, e.g. where rpc.pingomatic.com might already ping some of the entries in your list? Just asking.
Cheers
Jim
Hi Jim,
Thanks for the heads up about duplicates, but maybe I’m going blind or something but I can’t see any. Even Excel reports that there are no duplicates..
So if you could tell me whcih one are duplicated, I’ll remove any errors.
Personally I have found pingomatic to be a somewhat of a problamatic service. I know others swear by it, so its just my personal opnion. So I have deliberatley left Pingomatic out of the list, but I cinclude it my own list just for completelness (if there is such as word)
thanks for the heads up
Bruce
Hi Bruce,
I think I might have pasted in some additional URLs from another source and that probably confused me, but you’ve got Feedburner.com in there twice (with/without slash).
You said you don’t include Pingomatic, so when you say you post to the sites that matter, do you mean they are included in your list, or you do them manually elsewhere?
When pinging I got errors on Coreblog, Feedsky, Bitacoras, Rootblog, Snap, Weblogalot, Wasalive, Blogdigger, Blogoole, Blogoon, mostly as transport error – HTTP status code was not 200.
I’m using the WordPress plugin Ultimate Plugins Smart Update Pinger which logs status.
Cheers
Jim
Excellent list!
A nice alternative to Ping-O-Matic is Feed Shark.
I’ve been using Feed Shark for quite a while now without any problems.
http://feedshark.brainbliss.com
I have a nice little plugin for WordPress users that reports if you have duplicates in you ping list. You can find it on the Spunky Jones SEO Optimization Blog in the WordPress plugin section. It is call the “ping list checker”.
Question: Do you get more traffic pinging all of the blogsearch.google.com services? I have never did that and would like to hear if it makes a big difference?
By the way, nice list of ping services.
I created an easy to use pinger of those which worked.
So thanks for providing nice list. You can try pinger here
http://pingerfinger.com/
[...] Is Your Ping List a Waste of Time? [...]
[...] If you don’t want to use the default pingomatic that comes with WordPress , why not add this list instead. It will ping all these sites individually. Go to settings – Writing and scroll down to the bottom, take out pingomatic and add the list that you find here. http://www.websitesecrets101.com/is-your-ping-list-a-waste-of-time#dRIQ1Z5VxWox [...]
I have a common problem
http://1470.net/api/ping could not be pinged. Error message: “transport error – HTTP status code was not 200″
» http://api.feedster.com/ping could not be pinged. Error message: “transport error – could not open socket: 110 Connection timed out”
» http://api.moreover.com/ping could not be pinged. Error message: “parse error. not well formed”
does anyone else get these? What do they mean, and how can we fix?