WordPress RPC Ping Services List

Learn how to update WordPress ping services to notify search engines and aggregators whenever new content is published. Boost your site's visibility with this step-by-step guide.

You hit publish and you want Google to see the post today, not sometime next week. Back in the blog-heavy 2000s, ping services were how you nudged the world. WordPress would fire off a notification to a list of servers every time you posted, and those servers passed the word along to search engines and blog directories.

Let’s be honest up front: that era is mostly over. Most of the classic XML-RPC ping services are long defunct. Google Blog Search, which powered a lot of these endpoints, shut down years ago. So treat the list below as a historical starting point, not a magic SEO switch.

WordPress still ships the feature. It lives under Settings > Writing in a box called Update Services. Pinging is harmless and optional, so if you want to keep the old behavior, here’s how:

1. Open your WordPress admin dashboard.
2. Go to Settings > Writing.
3. Scroll to the Update Services section.
4. Paste the list of ping services below into the text box.
5. Click Save Changes.

http://rpc.twingly.com
http://api.feedster.com/ping
http://api.moreover.com/RPC2
http://api.moreover.com/ping
http://www.blogdigger.com/RPC2
http://www.blogshares.com/rpc.php
http://www.blogsnow.com/ping
http://www.blogstreet.com/xrbin/xmlrpc.cgi
http://bulkfeeds.net/rpc
http://www.newsisfree.com/xmlrpctest.php
http://ping.blo.gs/
http://ping.feedburner.com
http://ping.syndic8.com/xmlrpc.php
http://ping.weblogalot.com/rpc.php
http://rpc.blogrolling.com/pinger/
http://rpc.technorati.com/rpc/ping
http://rpc.weblogs.com/RPC2
http://www.feedsubmitter.com
http://blo.gs/ping.php
http://www.pingerati.net
http://www.pingmyblog.com
http://geourl.org/ping
http://ipings.com
http://www.weblogalot.com/ping
http://rpc.pingomatic.com/
http://blogsearch.google.com/ping/RPC2
http://ping.feedburner.com
http://rpc.blogbuzzmachine.com/RPC2
http://rpc.weblogs.com/RPC2
http://ping.fc2.com/
http://blogs.yandex.ru/
http://rpc.bloggerei.de/
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.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.it/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://ping.blogs.yandex.ru/RPC2
http://ping.rss.drecom.jp/
http://rpc.bloggerei.de/ping/
http://rpc.odiogo.com/ping/
http://rpc.weblogs.com/RPC2
http://blog.goo.ne.jp/XMLRPC
http://mod-pubsub.org/kn_apps/blogchatt
http://ping.amagle.com/
http://ping.bloggers.jp/rpc/
http://ping.exblog.jp/xmlrpc
http://ping.weblogalot.com/rpc.php
http://www.blogdigger.com/RPC2

Do ping services still matter?

Not much, and you should know why before you rely on them. Search engines don’t wait for a ping anymore. They discover new content through XML sitemaps, which WordPress generates automatically for you since version 5.5, plus the links between your own pages and, for Google specifically, Google Search Console. If you want a new post crawled fast, the real move is to open Search Console, run the URL Inspection tool, and request indexing. That’s the workflow Google documents, not pinging.

A dead ping endpoint won’t hurt your site. WordPress just fails the request quietly and moves on. So keeping the list is fine if you’re nostalgic or you still get value from one of the aggregators that happens to be alive. Just don’t expect it to move your rankings.

Bottom line

Set up a sitemap, connect Search Console, and write things people link to. That’s what gets you indexed today. The ping list above is a relic worth keeping around as a curiosity, not a strategy.