透過集合功能整理內容
你可以依據偏好儲存及分類內容。
APIs-Google 使用者代理程式
APIs-Google 是 Google API 所使用的使用者代理程式，用途是提供推播通知訊息。
應用程式開發人員可以要求收到這些通知，如此一來，他們就不必持續輪詢 Google 伺服器，確認感興趣的資源是否有所異動。為了確保這項服務不會遭到濫用，當開發人員要將某個網域的網址登記為接收訊息的位置時，Google 會要求他們先驗證自己擁有該網域。
APIs-Google 如何存取網站
APIs-Google 會使用 HTTPS POST 要求來傳送每一個推播通知。如果因為暫時性的錯誤情況而導致要求失敗，APIs-Google 會重新傳送通知。如果要求依然失敗，APIs-Google 會按指數輪詢的方式繼續重試，最長可達數天時間。
在不同情況下，APIs-Google 存取您網站的頻率會有差異，可能影響因素包括：針對您網站伺服器所建立的推播通知要求數量、受控資源的更新速度，以及重試所發生的次數等等。因此，APIs-Google 的流量模式在某些情況下可能相當穩定一致，但在其他情況下，則可能起伏不定或瞬間出現流量暴增的現象。
讓網站為 APIs-Google 做好準備
APIs-Google 使用 HTTPS 來提供推播通知，因此您的網站必須具備有效的 SSL 憑證才能運用 APIs-Google。無效的憑證包括：
- 自行簽署的憑證。
- 由不受信任的來源所簽署的憑證。
- 已撤銷的憑證。
請妥善設計您的應用程式，在數秒鐘內迅速回應通知訊息，以避免不必要的重試要求。
禁止 APIs-Google 呼叫您的網站
如要禁止 APIs-Google 呼叫您的網站，請執行下列任一操作：
-
取消註冊推播通知功能。如果您管理的網域具有由他人所擁有/管理的子網域或網址子空間，其中一名子網域擁有者可能建立了使用推播通知的應用程式。此時如果想封鎖 APIs-Google，請聯絡建立該應用程式的使用者，並請對方停用這項功能。
-
使用 robots.txt。robots.txt 檔案中的使用者代理程式應該設為
APIs-Google，因為 APIs-Google 不會遵循 Googlebot 使用者代理程式的規則。
APIs-Google 可能需要一點時間才會發現 robots.txt 檔案存有異動，如果在您使用 robots.txt 檔案封鎖 APIs-Google 數天之後，APIs-Google 仍持續傳送訊息到您的網站，請檢查 robots.txt 檔案的所在位置是否正確。
驗證呼叫者
如果懷疑收到假冒的要求，可以驗證存取伺服器的漫遊器呼叫是否確實來自 google.com。請在記錄中搜尋任何聲稱為 APIs-Google 使用者代理程式的 IP 位址，並執行反向 DNS 查詢，如果並非假冒，則查詢結果會顯示 googlebot.com 或 google.com 網域。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-04 (世界標準時間)。
[null,null,["上次更新時間：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."]]
