使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
APIs-Google 用户代理
APIs-Google 是 Google API 用于传递推送通知消息的用户代理。
应用开发者可以请求接收这些通知，这样就不必反复询问 Google 的服务器以了解他们感兴趣的资源是否发生了更改。为避免有人滥用此服务，Google 会要求开发者证明网域所有权，然后才允许他们注册相应网域的网址作为消息的接收位置。
APIs-Google 如何访问您的网站
APIs-Google 使用 HTTPS POST 请求发送每条推送通知。如果系统中可能存在的暂时性错误导致请求失败，APIs-Google 会重新发送通知。如果请求仍然没有成功，它会基于指数退避算法继续重试（最多可持续数天）。
APIs-Google 对您网站的访问频率取决于为您网站上的服务器创建的推送通知请求数、所监测资源的更新速度以及重试次数。因此，APIs-Google 流量模式在某些情况下可能相当稳定，但在某些情况下可能会断断续续或急剧起落。
让您的网站为 APIs-Google 做好准备
APIs-Google 使用 HTTPS 传递推送通知，因此您的网站必须具备有效的 SSL 证书。无效证书有以下几种：
- 自签名证书
- 由不受信任的来源签发的证书
- 已被撤消的证书
请确保您的应用已经过精心设计，并能在几秒内及时响应通知消息，以避免不必要的重试请求。
阻止 APIs-Google 访问您的网站
若要阻止 APIs-Google 调用您的网站，请执行以下任一操作：
-
取消通知接收注册。如果您管理的网域中存在归他人所有或由他人管理的子网域或网址子空间，其中一位子网域所有者可能设置了使用推送通知的应用。如果您希望屏蔽 APIs-Google，请联系可能已设置此类应用的所有者，让他们停用此设置。
-
使用 robots.txt。您需在 robots.txt 文件中指定用户代理
APIs-Google - APIs-Google 不会遵循 Googlebot 用户代理的规则。
在 APIs-Google 发现您对 robots.txt 文件所做的更改之前，可能会出现短暂的延迟。如果您在 robots.txt 中屏蔽 APIs-Google 数天后，它仍然向您的网站发送消息，请检查 robots.txt 的位置是否正确。
验证调用者
如果您怀疑自己收到的是仿冒请求，可以验证访问您服务器的漫游器是否确实来自 google.com。在您的日志中搜索将自己标识为 APIs-Google 用户代理的所有 IP 地址；进行 DNS 反向查找，结果会显示 googlebot.com 或 google.com 网域。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-04。
[null,null,["最后更新时间 (UTC)：2025-08-04。"],[[["\u003cp\u003eAPIs-Google is a user agent utilized by Google APIs to deliver push notifications, allowing developers to receive updates without continuous server polling.\u003c/p\u003e\n"],["\u003cp\u003eAPIs-Google accesses websites using HTTPS POST requests for notifications, employing retries with exponential backoff for failed deliveries, leading to varied traffic patterns.\u003c/p\u003e\n"],["\u003cp\u003eWebsites must possess a valid SSL certificate to receive notifications and should be optimized for prompt responses to minimize unnecessary retry attempts by APIs-Google.\u003c/p\u003e\n"],["\u003cp\u003eTo prevent APIs-Google access, website owners can unregister for notifications or utilize robots.txt to block the user agent.\u003c/p\u003e\n"],["\u003cp\u003eSpoofed requests can be identified by verifying the caller's IP address through reverse DNS lookup to confirm association with googlebot.com or google.com.\u003c/p\u003e\n"]]],["APIs-Google is Google's user agent for push notifications, delivering messages via HTTPS POST requests. Developers must verify domain ownership to use this service. APIs-Google retries failed requests with exponential backoff and can create sporadic traffic. Sites need valid SSL certificates, and apps should respond quickly to avoid retries. To block APIs-Google, unregister notifications or use `APIs-Google` in robots.txt. Spoofed requests can be identified by verifying IP addresses against googlebot.com or google.com domains.\n"],null,["# APIs-Google User Agent | Google Search Central\n\nAPIs-Google user agent\n======================\n\n\nAPIs-Google is the user agent used by Google APIs to deliver push notification messages.\nApplication developers can request these notifications to avoid the need for continually\npolling Google's servers to find out if the resources they are interested in have changed.\nTo make sure nobody abuses this service, Google requires developers to prove that they own\nthe domain before allowing them to register a URL with a domain as the location where they\nwant to receive messages.\n\nHow APIs-Google accesses your site\n----------------------------------\n\n\nAPIs-Google sends each push notification using an HTTPS POST request. If the request fails due\nto an error condition that might be temporary, APIs-Google will resend the notification. If\nthe request still doesn't succeed, it will continue to retry---based on an exponential backoff\nschedule---up to a maximum of several days.\n\n\nThe rate at which APIs-Google accesses your site varies by how many push notification requests\nwere created for servers on your site, by how fast the monitored resources are getting\nupdated, and by the number of retries occurring. As a result, the APIs-Google traffic patterns\ncan be consistent in some scenarios, but in other scenarios the traffic can be sporadic or\nspiky.\n\nPrepare your site for APIs-Google\n---------------------------------\n\n\nAPIs-Google uses HTTPS to deliver push notifications, so it requires your site to have a valid\nSSL certificate. **Invalid** certificates include the following:\n\n- Self-signed certificates.\n- Certificates signed by an untrusted source.\n- Certificates that have been revoked.\n\n\nAvoid unnecessary retry requests by ensuring that your application is well-designed and\nresponds promptly to notification messages (within seconds).\n\nPrevent APIs-Google from calling your site\n------------------------------------------\n\n\nTo prevent APIs-Google from calling your site, do one of the following:\n\n- **Unregister for notifications.** If you administer a domain that has subdomains or URL subspaces that are owned or administered separately, one of the subdomain owners may have set up an application that uses push notifications. If you want to block APIs-Google, contact anyone who might have set up an application like this and ask them to disable it.\n- **Use robots.txt.** The user agent to specify in the robots.txt file is `APIs-Google` - `APIs-Google` does not follow rules for the Googlebot user agent. There may be a small delay before `APIs-Google` discovers your robots.txt file change. If `APIs-Google` continues to send messages to your site several days after you've blocked it in robots.txt, check that the robots.txt is in the correct location.\n\nVerify the caller\n-----------------\n\n\nIf you suspect that you are receiving spoofed requests, you can\n[verify that a bot accessing your server really is calling from google.com](/search/docs/crawling-indexing/verifying-googlebot).\nSearch your logs for any IP addresses identifying themselves as the\n`APIs-Google` user agent; a reverse DNS lookup shows the googlebot.com or\ngoogle.com domain."]]
