搜索引擎PING服务详解及地址大全

本文链接：https://blog.csdn.net/longjing_g/article/details/4067209

写好一篇博客，当然是迫不及待地想和别人分享一下。如果有一种方法，能够自动将你最新的博客摘要发送到各大博客网站，或者让Google在第一时间收录你的大作，你相信吗？
这种方法就是Ping Service。Ping Service最早由WEBBLOGS.COM提出,其目的就是为博客程序提供一种通知机制,以便在第一时间将博客的更新信息发布到提供Ping Service服务的网站。现在，Ping Service已经被各大主流博客系统所采用，并发挥着越来越重要的作用。去WEBBLOGS.COM的主页http://weblogs.com/home.html看看吧，在“Recently Updated Weblogs...”里，你会很直观地发现平均每分钟都有数十甚至上百个各种语言的博客更新。你的博客网站不能Ping？那么，你落后了！这将直接影响到你的博客访问量，还有你的ADSenses收益哦！
从技术上说，Ping Service是一个基于XML-RPC机制的WEB调用接口，一个网站或者博客程序只要能支持这个接口，就可以实现Ping Service的功能。下面列出的是一些常见的支持Ping Service的网站：
国外:
http://rpc.weblogs.com/RPC2 Ping Service的老祖宗Weblogs
http://blogsearch.google.com/ping/RPC2 Goolge BlogSearch,注意RPC一定要大写
http://api.my.yahoo.com/RPC2 Yahoo,注意RPC一定要大写
http://rpc.pingomatic.com/rpc2 Ping-O-Matic 通过其主页http://pingomatic.com/可以手动将博客ping到各大主流博客网站
国内:
http://www.feedsky.com/api/rpc2 飞递
http://www.xianguo.com/xmlrpc/ping.php 鲜果
提供Ping Service的网站还有很多，但实际上很多小的博客聚合网站都会去Weblogs、Google这样的大站下载最新的博客更新，所以你只需要Ping几个主要的站点就行了。借用一位BLOG技术前辈的话：既然Ping一个网站就能达到同样的效果，你为什么还要去Ping15个呢？
对于博客网站程序，主流的如WordPress、Community Server等都提供了自动发送Ping命令的功能，在你提交新博客文章或者对博客文章进行更新时，都会自动将更新信息发送到预先定义的网站。你应该意识到，在这个Ping Service大行其道的年代，如果你想建立一个属于自己的博客网站，在选择博客程序时，最重要的一点就是看一看这个程序能不能提供自动发送Ping命令的功能。
但是一个很不幸的事实是在虚拟主机提供商看来，发送Ping命令是一件消耗资源和不安全的事情，因为博客程序需要建立一个Web Requst以发送更新信息，并等待一个Web Response以检查发送是否成功，而Web Requst可不是只能用来发送Ping命令的哦！因此很多虚拟主机空间都对相关的API进行了限制，比如我的虚拟主机提供商就是这样。在你选择虚拟主机提供商的时候，一定记得问问是否支持发送博客的Ping命令，否则你就只能像我一样，用pingomatic.com来手动发送Ping命令了。
顺便说一句，Windows Live Writer是支持Ping Service功能的，如果你的博客程序支持使用Windows Live Writer 发布，如WordPress，你就可以通过Windows Live Writer来进行Ping，而不一定非要在网站上进行了。打开Windows Live Writer,点击菜单栏的工具->选项，在"选项"对话框左栏中选中"Ping服务器"，在右栏中选中"向以下URL发送PING命令"，在文本框中填入我上面列出的Ping Service地址，然后点击"确定"。现在，当你通过Windows Live Write发布博客文章时，你的博客的更新信息就会自动发送到上面列出的Ping Service网站了。
下面来看看怎么使用pingomatic.com手动发送Ping命令：
点击这个链接http://pingomatic.com/ ；
在Blog Name中输入你的博客名称，如Tiray Blog;
在Blog Home Page中输入你的博客地址，如http://www.tiray.net/ ；
在RSS URL中输入你的博客的订阅地址，如http://www.tiray.net/syndication.axd ；
在Services to Ping中选中你要发送Ping命令的服务器，注意一次不要选太多，否则会出现超时错误；
点击Send Pings,过一会你就可以看到发送的结果了。
1、什么是Ping服务(Ping Service)？
Ping服务，也称更新通知服务，是搜索引擎发现网友博客更新的一种方式。

2、Ping服务有什么好处？
使搜索引擎能更快，更全面地收录博客文章。搜索引擎在收到Ping后会在最短时间内对相应博客进行抓取。

3、如何使用Ping服务？
a.手动Ping服务：
当发布一篇博客文章后，在搜索引擎提供的手动ping服务页面提交一次博客的RSS即可。
手动ping服务地址：
Google手动ping地址：http://blogsearch.google.com/ping
IASK手动ping地址：http://blog.iask.com/ping.php
QIHOO手动ping地址：http://so.blog.qihoo.com/pingblog.html
Feedsky手动ping地址：http://rpc.feedsky.com/ping

c.使用pingoat等网站服务
Pingoat(http://pingoat.com/) 这个不错的服务，它可帮助Blogger把自已的blog一次性Ping到大量的Blog搜索引擎，包括我们常见的technorati、 icerocket等等，只是目前还没国内的Blog搜索引擎被列入其中，在Ping的时候，通过点击分类标题就可选择该分类下的所有搜索引擎。
除了Ping功能外，Pingoat还提供了以下几个有用的服务：
1、搜索引擎抓虫模似工具。
2、Google Sitemap生成器。
3、防垃圾邮件生成器。
4、Blog价值查询工具。
5、网页关键字分析工具。
另外，还有一个Ipings(http://www.ipings.com/)的网站也是属于同类服务，只是它提供的Blog搜索引擎要比Pingoat少。
SEO技巧SEO技巧

几个中文网站Ping Service清单：

http://www.feedsky.com/api/RPC2
http://www.zhuaxia.com/rpc/server.php
http://www.xianguo.com/xmlrpc/ping.php
http://blog.iask.com/RPC2
http://ping.blog.qikoo.com/rpc2.php

其他重要的Ping Service：

更多的Ping Service 清单:

现将各大搜索引擎博客网站登陆入口网址整理:

The Weblogs.com ping service is used to automatically inform VeriSign whenever you update content on your site. The service receives notification (a "ping") from your site that you have added new content, and if all goes well, Weblogs.com adds your site to a list of recently changed weblogs.
If you're not using blogging software that automatically pings Weblogs.com, or if you're looking for more information on how to ping, this page will help you get your ping client up and running:

Setting up Your Ping Service Interface

Weblogs.com has two interfaces available: REST and XML-RPC. Both follow standard industry practices for ping server interfaces. You simply configure your blogging software to ping Weblogs.com anytime you publish new content.

A Quick Word on Domains

Weblogs.com manages two domains for normal and extended ping services: www.weblogs.com and rpc.weblogs.com. While both domains currently offer the same ping services, your ping clients and changes XML consumers should only refer to the rpc.weblogs.com domain as www.weblogs.com may not support pinging in the future.

[↑ Top]

Setting up an XML-RPC Client

The XML RPC request should be constructed based on:
RPC endpoint: http://rpc.weblogs.com/RPC2
Method name: weblogUpdates.ping OR weblogUpdates.extendedPing
Parameters: (should be sent in the same order as listed below)

name of site (string, limited to 1024 characters)
URL of site or RSS feed (string, limited to 255 characters)
Optional Parameters:
the url of the page to be checked for changes (string, limited to 255 characters) (non-optional when using the extended ping interface)
the URL of an RSS, RDF, or Atom feed (when using the extended ping interface) (string, limited to 255 characters, non-optional when using the extended ping interface)
a name (or "tag") categorizing your site content (string, limited to 1024 characters. You may delimit multiple values by using the '|' character.)
The XML RPC response will have a Struct with three members:
flerror (Boolean) which is true/1 if an error occurred
message (string) which contains "Thanks for the ping."(if successful) or an error message.
legal (string) which contains "You agree that use of the Weblogs.com ping service is governed by the Terms of Use found at www.weblogs.com."
If the call succeeds, the weblog will appear in shortChanges.xml on the next generation, usually within 5 to 10 minutes.
↑ [Top]

Example XML-RPC Request:

POST /RPC2 HTTP/1.0
User-Agent: Java
Host: rpc.weblogs.com
Content-Type: text/xml
Content-length: 250

weblogUpdates.ping

Someblog

http://spaces.msn.com/someblog

↑ [Top]

Example Extended Ping XML-RPC Request with multiple category tags:

POST /RPC2 HTTP/1.0
User-Agent: Java
Host: rpc.weblogs.com
Content-Type: text/xml
Content-length: 300

weblogUpdates.extendedPing

Someblog

http://spaces.msn.com/someblog

http://spaces.msn.com/someblog/PersonalSpace.aspx?something

http://spaces.msn.com/someblog/feed.rss

personal|friends

↑ [Top]

Example XML-RPC Response:
```
HTTP/1.1 200 OK
Connection: close
Content-Length: 333
Content-Type: text/xml
Date: Sun, 30 Sep 2001 20:02:30 GMT
Server: Apache

    
  
      
   
        
         
    
           
     
             
      
               
       
        flerror
               
       
                 
        
         0
                
              
             
      
               
       
        message
               
       
        Thanks for the ping.
              
             
      
               
       
        legal
               
       
        You agree that use of the Weblogs.com ping service is governed by the Terms of Use found at www.weblogs.com.
              
            
          
           
   

  
```
↑ [Top]

Setting up a REST Client
Weblogs.com accepts form-based HTTP POST and GET requests for non-extended pings. For example, the following is a valid HTTP GET ping request:
URL: http://rpc.weblogs.com/pingSiteForm
Parameters:
name= (limited to 1024 characters)
url= (limited to 255 characters)
Optional Parameter:
changesURL= (limited to 255 characters)
↑ [Top]

Example HTTP GET request:

http://rpc.weblogs.com/pingSiteForm?name=InfraBlog&url=https%3A%2F%2Fblue-sea-697d.quartiers047.workers.dev%3A443%2Fhttp%2Finfrablog.verisignlabs.com

↑ [Top]

Processing Model, Error Responses, and Rejected Pings

Both the REST and XML-RPC interfaces are synchronous and will attempt to ensure that your client submitted a valid ping. Examples of invalid pings include, but are not limited to:
- Your ping is missing a required parameter;
- Your ping contains a parameter that exceeded its length limitation;
- Your ping contains a URL parameter that does not start with "http://";
- Your ping contains a URL parameter that refers to a known invalid host;
- Your XML-RPC request contains an ENTITY reference.
The core Weblogs.com ping processing service is based upon an asynchronous model. This means that even though your client receives an initial "Thanks for the ping" synchronous response, your ping may be dropped or filtered later for various reasons (not limited to the following):
- Your ping client may be pinging too fast (more than one ping per 30 minute interval);
- Your ping may refer to a blog host that has requested to be removed from this service.
As always, if you feel that your ping is being inappropriately dropped, or have other questions regarding this service, you may send an email to info@weblogs.com.

↑ [Top]

Published Weblog Lists: changes.xml and shortChanges.xml

Every five minutes, Weblogs.com publishes two documents:
1. changes.xml contains the latest 60 minutes of pinged weblogs. Applications should not read this file more often than once per hour.
2. shortChanges.xml contains the top 5 minutes of changes.xml. The top 100 of these sites are shown at Weblogs.com.
In addition, once per hour Weblogs.com publishes the previous hours worth of pinged weblogs as XML and HTML documents. For example, you can find the list of Weblogs that were pinged during the 05 GMT hour of 18 October 2005 under www.weblogs.com/2005/10/18/05.xml.

Weblogs.com supports HTTP request and response headers like "If-Modified-Since" and ETag to help you save bandwidth by only downloading the changes files that you haven't already seen.

Both changes.xml and shortChanges.xml conform to the following XML document structure:
```
   
    
    

    
    
    
    

   
```
The www.weblogs.com/rssUpdates service produces changes.xml and shortChanges.xml that conform to the following XML document structure:
```
   

    
    
    
    
    
    

   
```
↑ [Top]

The Element

changes.xml and shortChanges.xml contain a single weblogUpdates element. It has three attributes: version, updated and count; and any number of weblog sub-elements.
1. version is a number; we're currently on version number 2. However if the format changes substantially, we have an easy way to support this version in addition to the new one.
2. updated is a string, a date-time in HTTP 1.0 format, it indicates when changes.xml was last updated.
3. count is a number, it indicates how many times changes.xml has been updated since its deployment.
4. Note that weblogUpdates is sorted in reverse-chronologic order.
↑ [Top]
The Element

weblog has three attributes: name, url and when:
1. name is a string, the name of a weblog.
2. url is a string, its URL.
3. rssUrl is a string, the URL of an RSS, RDF, or Atom feed for the weblog.
4. when is a number of seconds. If you subtract this number from the updated attribute of weblogUpdates, you'll get the time that Weblogs.com was pinged with that weblog.
↑ [Top]
Compatibility Notes

Weblogs.com is compatible with the original www.weblogs.com site formerly maintained by Dave Winer. The following sites are still maintained by Dave Winer and have not migrated to the new VeriSign infrastructure:
- doc.weblogs.com
- radio.weblogs.com