WPFuture

Simplifying WordPress!

WordPress Ping List for faster indexing

· · Leave a Comment

WordPress Ping Update Service plays a very important role in Website SEO. It will help the WordPress site owners to notify all the major search engines and web directories about your new updated blog post or page.

No one likes the slow process of Google to crawl and index the blog post. If you are an impatient blogger like me and want to index your blog post faster then you are in the right place. Gone are days when you need to wait for search engines to crawl and index your blog post or page. The old process was so slow.

Now you can use WordPress Ping Update Services to index your blog post faster.

How do WordPress Ping Update Services work?

Whenever you publish a new blog post/page or modify a previous blog post/page, it sends pings to all the XML-RPC ping services which are listed under your WordPress site Update Services.

WordPress Update Services is a great functionality to extend your blog reach to search engines but you need a good WordPress Ping List to get the better results.

In this post, Not only I’m going to share my Secret WordPress Ping List for better SEO but also share the way to update WordPress Ping List.

Here is the working WordPress Ping List. This is the same list of Ping Services which I’m using here at WPFuture and many other blogs.

http://rpc.pingomatic.com
http://rpc.twingly.com
http://rpc.icerocket.com:10080/
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
http://rpc.blogrolling.com/pinger/
http://rpc.technorati.com/rpc/ping
http://rpc.weblogs.com
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://blogsearch.google.com/ping/RPC2
http://1470.net/api/ping
http://bblog.com/ping.php
http://bitacoras.net/ping
http://blog.goo.ne.jp/XMLRPC
http://blogdb.jp/xmlrpc
http://blogmatcher.com/u.php
http://coreblog.org/ping/
http://mod-pubsub.org/kn_apps/blogchatt
http://www.lasermemory.com/lsrpc/
http://ping.amagle.com/
http://ping.bitacoras.com
http://ping.bloggers.jp/rpc/
http://ping.cocolog-nifty.com/xmlrpc
http://ping.blogmura.jp/rpc/
http://ping.exblog.jp/xmlrpc
http://ping.myblog.jp
http://ping.rootblog.com/rpc.php
http://ping.weblogs.se/
http://pingoat.com/goat/RPC2
http://rcs.datashed.net
http://rcs.datashed.net/RPC2/
http://rpc.blogbuzzmachine.com/RPC2
http://topicexchange.com
http://topicexchange.com/RPC2
http://trackback.bakeinu.jp/bakeping.php
http://www.a2b.cc/setloc/bp.a2b
http://www.bitacoles.net/ping.php
http://www.blogoole.com/ping/
http://www.blogoon.net/ping/
http://www.blogpeople.net/servlet/weblogUpdates
http://www.blogroots.com/tb_populi.blog?id=1
http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php
http://www.newsisfree.com/RPCCloud
http://www.popdex.com/addsite.php
http://www.snipsnap.org/RPC2
http://www.weblogues.com/RPC/
http://xmlrpc.blogg.de
http://xping.pubsub.com/ping/
http://rpc.copygator.com/ping/
http://blogs.yandex.ru/
http://ping.blogs.yandex.ru/RPC2
http://ping.fc2.com/
http://rpc.bloggerei.de/
http://ping.rss.drecom.jp/
http://rpc.bloggerei.de/ping/
http://rpc.odiogo.com/ping/
http://www.modpubsub.org/kn_apps/blogchatter/ping.php
http://effbot.org/rpc/ping.cgi
http://audiorpc.weblogs.com/RPC2
http://bing.com/webmaster/ping.aspx
http://blog.with2.net/ping.php
http://blog.youdao.com/ping/RPC2
http://blogping.unidatum.com/RPC2
http://catapings.com/ping.php
http://ping.bitacoras.com/
http://ping.groove-cast.com/ping.php
http://ping.pubsub.com/ping
http://ping.wordblog.de
http://serenebach.net/rep.cgi
http://services.newsgator.com/ngws/xmlrpcping.aspx
http://wasalive.com/ping/
http://xianguo.com/xmlrpc/ping.php
http://blogpeople.net/servlet/weblogUpdates
http://feedsky.com/api/RPC2
http://geourl.org/ping/
http://hamo-search.com/ping.php
http://holycowdude.com/rpc/ping
http://mapufacture.com/georss/ping/api
http://mod-pubsub.org
http://newsblog.jungleboots.org/ping.php
http://pinger.blogflux.com/rpc
http://ping.fakapster.com/rpc
http://ping.kutsulog.net
http://ping.namaan.net/rpc
http://pingqueue.com/rpc/
http://ping.snap.com/ping/RPC2
http://ping.speenee.com/xmlrpc
http://rcs.salon.com/RPC2
http://r.hatena.ne.jp/rpc
http://rpc.britblog.com
http://rpc.icerocket.com:10080
http://rpc.reader.livedoor.com/ping
http://rpc.tailrank.com
http://rpc.tailrank.com/feedburner/RPC2
http://rpc.technorati.jp/rpc/ping
http://rpc.wpkeys.com
http://submitblogs.com/
http://thingamablog.sourceforge.net/ping.php
http://www.2bet.com/
http://www.2rss.com
http://www.a2b.cc
http://www.a2b.cc/setloc/bp.a2b
http://www.blogarama.com/
http://www.blogbits.com/
http://www.blogdex.net/
http://www.blogexplosion.com
http://www.bloggernity.com/
http://www.bloglines.com/ping
http://www.blogpulse.com/submit.html
http://www.blogsdominicanos.com/ping
http://www.feedblitz.com/f/f.fbz?XmlPing
http://www.feedsky.com/api/RPC2
http://www.globeofblogs.com/
http://www.holycowdude.com/rpc/ping/
http://www.linksboy.com/
http://www.lsblogs.com/
http://www.octora.com/add_rss.php
http://www.ohlinks.com
http://www.readablog.com/
http://www.rogerlinks.com/linker/index.shtml
http://www.syndic8.com/xmlrpc.php
http://www.wasalive.com/ping/
http://www.xianguo.com/xmlrpc/ping.php
http://xmlrpc.blogg.de/
http://xmlrpc.bloggernetz.de/RPC2
http://xping.pubsub.comping/
http://zhuaxia.com/rpc/server.php
http://api.my.yahoo.com/RPC2
http://api.my.yahoo.com/rss/ping

How to Update WordPress Ping List

Now you have access to my secret WordPress ping list but you need to add it to your WordPress blog to get results. Here is the quick guide to add or update WordPress ping list.

Login to your WordPress Admin Panel and Go to Settings»Writing. Now scroll down to Update Services and paste all the above Ping List.

ping update settings wordpress

That’s it. Now you are done. Congratulations, you have successfully updated your WordPress Ping List. Now WordPress will take care of the rest. It will send pings to all the ping services when you publish or modify a blog post.

If you find this tutorial useful, help me by sharing it with your friends on Facebook, Twitter, and Google+. However, if you have any doubt or advice regarding this post, let me know via comments.

How to Limit or Disable WordPress Heartbeat API

· · Leave a Comment

WordPress Heartbeat API (A great tool for plugin developers to do some amazing tasks), introduced in WordPress 3.6. Most of the plugin developers use this Heartbeat API to show you notifications in real time, etc.

This heartbeat API is good for plugin developers but it can kill your WordPress site by increasing web hosting resource usage. If you are using shared hosting for your WordPress site, it can create a big problem for you.

If your web hosting provider has strict limits on the number of processes or resources, you could go over the limit and your hosting account may suspend by your hosting provider.

In this tutorial, I will show you how to limit or disable WordPress heartbeat API. Below is the complete tutorial on WordPress Heartbeat API.

How WordPress Heartbeat API Works

This heartbeat API uses /wp-admin/admin-ajax.php to run AJAX calls from the web browser. WordPress can keep track of your site dashboard with the help of this API.

Let me show you a better example. Suppose if all you did was login to your WordPress admin panel and then minimized that window for some time, you’d see requests for admin-ajax.php in your site’s access logs. This is the pulse generated by WordPress Heartbeat.

However, even though this is great functionality by WordPress but it may cause issues in certain cases. When you edit your post or page, it will generate the pulse in every 15 seconds.

If you have too many requests, then your server will slow down. That’s the main problem with this great API.

How to Limit WordPress Heartbeat API

If you want to control or limit your WordPress heartbeat, you can use Heartbeat Control plugin. It allows you to control the interval of pulses. Upon activation, go to Settings » Heartbeat Control Settings to configure the plugin.

On Heartbeat Control Settings page, you need to add a new rule to control the heartbeat. Don’t worry, I will show you how to do that.

From the Heartbeat Behavior option, you can allow, disable, or modify WordPress Heartbeat. To change the frequency of Heartbeat API, you need to select Modify Heartbeat from Heartbeat Behavior option.

Now it will show a new option (Frequency) after selecting Modify Heartbeat. Here you can change the frequency of heartbeat API. By default, Heartbeat API makes a post call every 15 seconds on post edit pages and every minute on the WordPress admin dashboard.

I would recommend that you choose 60 seconds frequency time for Heartbeat API.

With this plugin, you can also select where you want to control heartbeat settings. You just need to tick the checkboxes to select the locations.

When you are done, click on Save Changes button to apply your settings. That’s it. Now plugin will take care of your heartbeat API. With this method, you can easily limit the heartbeat API of your WordPress site.

How to Disable WordPress Heartbeat API without Plugin

Most of the WordPress users don’t like to use too many plugins on their site because it can lead to high CPU usage. Now I will show you to how to disable heartbeat API without using any plugin.

With this method, you can disable API entirely on your WordPress site. You can’t use this amazing functionality after disabling it.

Make sure you are a single user on your site and you don’t need any features made possible by the API, then you can disable it.

Below is the code to disable heartbeat API on entire site. You need to copy and paste this code into your theme functions.php file. Make sure you are using child theme, otherwise the changes will be lost with the next theme update.

Note: Backup the functions.php file before editing.

add_action( 'init', 'stop_heartbeat', 1 );
function stop_heartbeat() {
wp_deregister_script('heartbeat');
}

Now you are done. You have successfully disabled the WordPress heartbeat API on your entire site.

If you control the heartbeat API, pulses are less likely to impact on server performance. Several users who use this method to control API report they no longer experience suspensions for using too many resources.

I hope you like this tutorial, you can support us by sharing this post on Instagram, Twitter and or subscribe to our newsletter for more useful tutorials.

Affiliate Disclaimer

When you use my referral links to buy something, I earn a little commission and appreciate it.