-
Posts
-
Hello, looking inside the Ping Log of WordPress Ping Optimizer I noticed that I get ping only when I upload new images. But not when I modify the old images. For example today I modified something in the name of the site and I changed the tagline. My question: when the new changes will appear in the search engines and, most important, if all the images were updated with new informations These information will be updated in Google and other search engines or no? The correct functioning of WordPress Ping Optimizer is concerning me a bit. Is normal that in the Ping list is says Not ping when I modify an image?
I did a forced ping and I got this: what is in red is error. Why do I get these errors?
» http://ping.pubsub.com/ping was successfully pinged (extended format)
» http://xianguo.com/xmlrpc/ping.php could not be pinged. Error message: “parse error. not well formed”
» http://www.blogpeople.net/ping was successfully pinged (extended format)
» http://www.bloglines.com/ping was successfully pinged (extended format)
» http://www.bing.com/webmaster/ping.aspx could not be pinged. Error message: “parse error. not well formed”
» http://serenebach.net/rep.cgi could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://rpc.bloggerei.de/ping/ was successfully pinged (extended format)
» http://rpc.aitellu.com was successfully pinged (extended format)
» http://ping.fc2.com/ was successfully pinged
» http://ping.bloggers.jp/rpc/ could not be pinged. Error message: “parse error. not well formed”
» http://blogsearch.google.com/ping could not be pinged. Error message: “parse error. not well formed”
» http://blo.gs/ping.php could not be pinged. Error message: “parse error. not well formed”
» http://blogpingr.de/ping/rpc2 could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://blog.with2.net/ping.php was successfully pinged (extended format)
» http://blogping.unidatum.com/RPC2/ was successfully pinged (extended format)
» http://www.weblogues.com/RPC/ could not be pinged. Error message: “transport error – could not open socket”
» http://www.wasalive.com/ping/ could not be pinged. Error message: “parse error. not well formed”
» http://www.popdex.com/addsite.php could not be pinged. Error message: “transport error – could not open socket”
» http://www.blogoole.com/ping/ could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://www.blogdigger.com/RPC2 could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://topicexchange.com/RPC2 could not be pinged. Error message: “transport error – could not open socket”
» http://rpc.blogrolling.com/pinger/ 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 la bitácora no figura en el directorio de Bitacoras.com, pero puedes darte de alta manualmente en http://bitacoras.com.
» http://cullect.com/feed/ping could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://api.my.yahoo.com/rss/ping could not be pinged. Error message: “transport error – could not open socket”
» http://api.moreover.com/ping could not be pinged. Error message: “transport error – could not open socket”
» http://ping.myblog.jp could not be pinged. Error message: “transport error – could not open socket”
» http://pinger.blogflux.com/rpc could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://rpc.newsgator.com/ could not be pinged. Error message: “transport error – could not open socket”
» http://www.newsisfree.com/RPCCloud could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://rpc.weblogs.com/RPC2 was successfully pinged (extended format)
» http://rpc.technorati.com/rpc/ping could not be pinged. Error message: “transport error – could not open socket”
» http://rpc.reader.livedoor.com/ping was successfully pinged (extended format)
» http://rpc.icerocket.com:10080/ could not be pinged. Error message: “transport error – could not open socket”
» http://ping.syndic8.com/xmlrpc.php could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://ping.feedburner.com/ was successfully pinged (extended format)
» http://ping.blogs.yandex.ru/RPC2 was successfully pinged (extended format)
» http://feedsky.com/api/RPC2 could not be pinged. Error message: “transport error – could not open socket”
» http://api.my.yahoo.com/RPC2 could not be pinged. Error message: “transport error – could not open socket”
» http://api.moreover.com/RPC2 could not be pinged. Error message: “transport error – could not open socket”
» http://rpc.pingomatic.com was successfully pinged (extended format)
» http://geourl.org/ping?p=http%3A%2F%2Fwww.food.ezeepics.com could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://rpc.weblogs.com/pingSiteForm?name=BlogTitle&url=http%3A%2F%2fwww.food.ezeepics.com was successfully pinged (extended format)
» http://rpc.twingly.com was successfully pinged
» http://www.google.com/webmasters/tools/ping?sitemap=http://www.food.ezeepics.com/sitemap.xml could not be pinged. Error message: “transport error – HTTP status code was not 200”
» http://submissions.ask.com/ping?sitemap=http%3A//www.food.ezeepics.com/sitemap.xml could not be pinged. Error message: “transport error – could not open socket”
» http://www.bing.com/webmaster/ping.aspx?siteMap=www.food.ezeepics.com/sitemap.xml could not be pinged. Error message: “parse error. not well formed”
» http://feedburner.google.com/fb/a/pingSubmit?bloglink=http%3A%2F%2Fwww.food.ezeepics.com could not be pinged. Error message: “parse error. not well formed”
» http://rpc.pingomatic.com/ was successfully pinged (extended format)
» http://blogsearch.google.com/ping/RPC2 was successfully pinged (extended format)
The forum ‘Archives’ is closed to new topics and replies.