使用限制
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
這個版本的 Google Search Console API 會強制執行下列用量限制:
搜尋分析
搜尋分析配額分為兩種類型:負載限制和每秒查詢次數限制。所有超出配額的事件,都會導致「超過配額」錯誤。
載入配額
Load 代表查詢耗用的內部資源。大部分使用者不會超過載入限制,但如果您這麼做,就會收到「超過配額」錯誤訊息。Search Analytics (分析) 資源會強制執行以下載入限制:
- 短期載入配額: 短期配額以 10 分鐘的區塊為單位。修正方法:
- 如果超出配額,請等待 15 分鐘後再試一次。如果超過配額,就會超出長期配額。
- 如果您只超出短期配額,請將查詢分散在一天當中。
- 長期載入配額: 長期配額以 1 天區塊為單位。如果您只在 10 分鐘內執行一項查詢而超過配額,就會超出長期配額。修正方法:
- 如果您依網頁或查詢字串分組和/或進行篩選,查詢費用會相當昂貴。按網頁「和」查詢字串分組/篩選的查詢費用最高。如要降低這些查詢的負載,請移除網頁的分組和/或篩選頁面和/或查詢字串。
- 查詢量隨著查詢的日期範圍而增加。因此,約為六個月的查詢,費用會比日期範圍範圍 (1) 的查詢要高得多。
- 避免重新查詢相同的資料 (例如,查詢上個月的所有資料)。
QPS 配額
搜尋分析資源會強制執行下列 QPS (每秒查詢次數) QPM (每分鐘查詢數) 和 QPD (每日查詢數) 限制:
- 個別網站配額 (查詢同一個網站的呼叫):
- 每位使用者配額 (相同使用者發出的呼叫):
- 每項專案配額 (使用同一個 Developer Console 金鑰發出的呼叫):
- 每日 30,000,000 次查詢
- 每分鐘 40,000 次查詢
範例
- 使用者 A 最多可以在 3 個網站上獲得 1,200 次查詢每分鐘 1,200 次查詢。
- 使用者 A 和 B 最多可以在自家網站上獲得 1,200 次 QPM。
網址審查
索引檢查配額
- 個別網站配額 (查詢同一個網站的呼叫):
- 每項專案配額 (使用同一個 Developer Console 金鑰發出的呼叫):
- 每日 10,000,000 次查詢
- 每分鐘 15,000 次查詢
所有其他資源
- 每位使用者限制 (同一位使用者的呼叫):
- 每項專案的限制 (使用同一個 Developer Console 金鑰發出的呼叫):
如要查看或變更專案的用量限制,或是想申請更多配額,請進行以下步驟:
- 確認您的專案已設有帳單帳戶。如果沒有,請先建立一個。
- 開啟 API 控制台並前往 API 程式庫「已啟用的 API」頁面,從清單中選取 API。
- 如要查看及變更配額相關設定,請點選「配額」。如要查看用量統計資料,請點選「用量」。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2024-07-23 (世界標準時間)。
[null,null,["上次更新時間:2024-07-23 (世界標準時間)。"],[[["\u003cp\u003eThe Google Search Console API has usage limits for Search Analytics, URL inspection, and all other resources to ensure fair access.\u003c/p\u003e\n"],["\u003cp\u003eSearch Analytics usage is limited by short-term (10 minutes) and long-term (1 day) load quota, as well as QPS (queries per second), QPM (queries per minute) and QPD (queries per day) quota for per-site, per-user, and per-project usage.\u003c/p\u003e\n"],["\u003cp\u003eURL inspection is restricted by per-site and per-project quota based on QPM and QPD and has an index inspection quota.\u003c/p\u003e\n"],["\u003cp\u003eAll other resources have per-user and per-project limitations on QPS, QPM, and QPD.\u003c/p\u003e\n"],["\u003cp\u003eUsers can monitor their current API usage in the quota tab of their Google API Console project.\u003c/p\u003e\n"]]],["The Google Search Console API has usage limits for Search Analytics and URL inspection. Search Analytics has load and QPS limits; exceeding load quotas requires waiting 15 minutes or reducing query complexity (grouping/filtering, date range, re-querying). QPS limits are 1,200 QPM per site/user, and 30,000,000 QPD and 40,000 QPM per project. URL inspection has 2,000 QPD and 600 QPM per site, with project limits at 10,000,000 QPD and 15,000 QPM. All other resources have a per-user limit of 20 QPS and 200 QPM, and per-project of 100,000,000 QPD.\n"],null,["# Usage Limits\n\nThis version of the Google Search Console API enforces the following usage limits:\n\n*** ** * ** ***\n\nSearch Analytics\n----------------\n\nSearch Analytics quota falls in two types: load limits and QPS limits. The \"[quota exceeded](/webmaster-tools/v1/errors#error_quotaExceeded)\" error is the same for all quota exceeded events.\n\n### Load quota\n\n*Load* represents the internal resources consumed by a query. Most users will not exceed load limits, but if you do, you will receive a \"[quota exceeded](/webmaster-tools/v1/errors#error_quotaExceeded)\" error message. The [Search Analytics](/webmaster-tools/v1/searchanalytics) resource enforces the following load limits:\n\n- **Short-term load quota:** Short-term quota is measured in 10 minute chunks. **To fix:**\n - If you exceed your quota, wait 15 minutes and try again. If you still exceed quota, you are exceeding long-term quota.\n - If you are exceeding short-term quota only, spread out your queries throughout the day.\n- **Long-term load quota:** Long-term quota is measured in 1 day chunks. If you exceed quota when running only a single query inside a 10 minute period, you are exceeding your long-term quota. **To fix:**\n - Queries are expensive when you group and/or filter by either page or query string. Queries grouped/filtered by page AND query string are the most expensive. To reduce your load for these queries, remove the grouping and/or filtering for the page and/or query string.\n - Query load increases with the date range queried. So queries with a six month range are much more expensive than a query with a one day range.\n - Avoid requerying the same data (for example, querying all data for last month over and over).\n\n### QPS quota\n\nThe [Search Analytics](/webmaster-tools/v1/searchanalytics) resource enforces the following QPS (queries per second) QPM (queries per minute) and QPD (queries per day) limits:\n\n- **Per-site quota** (calls querying the same site):\n - 1,200 QPM\n- **Per-user quota** (calls made by the same user):\n - 1,200 QPM\n- **Per-project quota** (calls made using the same Developer Console key):\n - 30,000,000 QPD\n - 40,000 QPM\n\n*Example*\n\n- User A can make up to 1,200 QPM combined to her 3 websites.\n- Users A and B can make up to 1,200 QPM combined to their one website.\n\nURL inspection\n--------------\n\n- **index inspection quota**\n- **Per-site quota** (calls querying the same site):\n - 2000 QPD\n - 600 QPM\n- **Per-project quota** (calls made using the same Developer Console key):\n - 10,000,000 QPD\n - 15,000 QPM\n\nAll other resources\n-------------------\n\n- **Per-user limit** (calls made by the same user):\n - 20 QPS\n - 200 QPM\n- **Per-project limit** (calls made using the same Developer Console key):\n - 100,000,000 QPD\n\n*** ** * ** ***\n\nYou can see your current usage in the quota tab for your project in the [Google APIs Console](https://console.developers.google.com/project)."]]