Setelah sebelumnya ku bahas XML-RPC Ping Services for SEO yang menerangkan tentng penggunaan rpc ping di website yang menggunakan wordpres, mungkin banyak pertanyaan tentang banyaknya ping (multiple ping) dan kinerja dari website kita sendiri, seperti comment dari teman kita
Mo nanya kang…. ?…
Apa wordpress gak malah pusiiing…kang…
kalau banyak kayak gitu…?
BTW pantes di coba …. 
thanks for sharing.
Maka, disini akan kuberikan aternatif wordpress plugin untuk service ping tersebut, biar mempermudahkan kita untuk penambahan dan pengurangan service ping tersebut.
Install plugin, activation by email, check email, click link activate
verify ping
Setelah melakukan verify dan activate (step 2), kita akan mendapatkan default service ping dari maxblogpress yang sebelumnya telah ku masukkan di /wp-admin/options-writing.php dan ini merupakan synchronized dari situ. Ping tersebut yaitu :
http://api.moreover.com/ping
http://api.my.yahoo.com/RPC2
http://api.my.yahoo.com/rss/ping
http://blogping.unidatum.com/RPC2/
http://blogsearch.google.co.id/ping/RPC2
http://blogsearch.google.com/ping/RPC2
http://cullect.com/feed/ping
http://ping.bitacoras.com
http://ping.feedburner.com
http://ping.syndic8.com/xmlrpc.php
http://rpc.blogrolling.com/pinger/
http://rpc.icerocket.com:10080/
http://rpc.pingomatic.com/
http://rpc.technorati.com/rpc/ping
http://rpc.weblogs.com/RPC2
http://topicexchange.com/RPC2
http://www.blogdigger.com/RPC2
http://www.blogoole.com/ping/
http://www.blogpeople.net/servlet/weblogUpdates
http://www.popdex.com/addsite.php
http://www.wasalive.com/ping/
http://www.weblogues.com/RPC/
http://xping.pubsub.com/ping
activated
Services ping akan otomatis melakukan ping ketika kita publish new posts atau drafts. Danketika kita publish future posts atau edit previously published posts, maka akan menggunakan WordPress default.
Pada plugin ini, kita bisa melihat ping log untuk melihat lastes action performed plugin ini.
update :
Setelah kupublish pots ini, maka di ping log terdapat :
03-20-2009 09:54:22 - Pinging (new post: “Ping Optimizer in Wordpress with MaxBlogPress Ping Optimizer Plugin”)
» http://api.moreover.com/ping could not be pinged. Error message: “parse error. not well formed”
» http://api.my.yahoo.com/RPC2 was successfully pinged (extended format)
» http://api.my.yahoo.com/rss/ping could not be pinged. Error message: “transport error - HTTP status code was not 200″
» http://blogping.unidatum.com/RPC2/ could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
» http://blogsearch.google.co.id/ping/RPC2 was successfully pinged (extended format)
» http://blogsearch.google.com/ping/RPC2 was successfully pinged (extended format)
» http://cullect.com/feed/ping could not be pinged. Error message: “transport error - HTTP status code was not 200″
» http://ping.bitacoras.com could not be pinged. Error message: “El ping no es válido porque tu bitácora no figura en el directorio de Bitacoras.com, pero puedes darte de alta manualmente en http://bitacoras.com. Gracias por interesarte.”
» http://ping.feedburner.com was successfully pinged (extended format)
» http://ping.syndic8.com/xmlrpc.php was successfully pinged (extended format)
» http://rpc.blogrolling.com/pinger/ was successfully pinged
» http://rpc.icerocket.com:10080/ was successfully pinged
» http://rpc.pingomatic.com/ was successfully pinged (extended format)
» http://rpc.technorati.com/rpc/ping was successfully pinged (extended format)
» http://rpc.weblogs.com/RPC2 was successfully pinged (extended format)
» http://topicexchange.com/RPC2 was successfully pinged (extended format)
» http://www.blogdigger.com/RPC2 was successfully pinged
» http://www.blogoole.com/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200″
» http://www.blogpeople.net/servlet/weblogUpdates was successfully pinged (extended format)
» http://www.popdex.com/addsite.php was successfully pinged (extended format)
» http://www.wasalive.com/ping/ was successfully pinged (extended format)
» http://www.weblogues.com/RPC/ could not be pinged. Error message: “transport error - could not open socket: 0 php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution”
» http://xping.pubsub.com/ping was successfully pinged (extended format)
Dari log inilah kita dapat me manage ping service yang telah kita masukkan yaitu dengan me remove ping warna merah atau memberbaiki linknya atau menambahi ping service lainnya lagi.
on March 19, 2009 @ 9:26 pm
Subscribe to the feed version of catatanku» catatanku - Blog Catatanku ariefew in a feed reader.
