透過集合功能整理內容
你可以依據偏好儲存及分類內容。
使用 Google 搜尋狀態資訊主頁
Google 搜尋狀態資訊主頁提供 Google 搜尋系統運作狀態的相關資訊。資訊主頁會顯示影響許多網站或使用者的問題,因此,如果您在資訊主頁中看到某個註解,該註解可能與網站成效的變化有關。
資訊主頁也會顯示 Google 搜尋近期與網站擁有者相關的排名更新事項。如要進一步瞭解 Google 如何改善搜尋功能,以及我們分享更新資訊的原因,請參閱《Google 如何更新搜尋功能》這篇網誌文章。您也可以前往我們的網誌,進一步瞭解 Google 搜尋的最新消息。
如要接收問題與最新資訊的通知,可以訂閱 RSS 動態消息。
查看資訊主頁
問題的生命週期
偵測到 Google 搜尋相關問題時,搜尋關係團隊和搜尋工程團隊會合作解決問題,並告知您:
- 偵測結果與初步回應
- 著手查看
- 後續追蹤
- 緩解或修正措施
偵測結果與初步回應
搜尋關係團隊會觀察多種不同信號 (包括內部監控和社群提供的意見回饋),藉此監控 Google 搜尋系統的狀態。發生影響廣泛的問題時,搜尋關係團隊會更新資訊主頁。廣泛問題代表有大量網站或使用者受到影響。
狀態資訊主頁可能包含下列狀態:
狀態定義 |
可用 |
系統大致運作正常,可以使用。 |
系統資訊 |
系統已更新或變更,例如開始推出排名更新,或 Googlebot 開始透過 HTTP/2 進行檢索。 |
系統受到干擾 |
網站可能發生系統效能降級,起因為常見第三方 (例如 DNS 伺服器)
|
系統服務中斷 |
系統未能大範圍運作,此問題影響到大量網站或使用者。
|
調查
搜尋工程團隊會負責調查問題的根本原因。如要進一步瞭解相關資訊,請參閱《Site Reliability Engineering》(網站可靠性工程) 一書的第 12 章。
後續追蹤
在問題持續期間,搜尋關係團隊會定期提供更新相關資訊,內容可能包括:
- 該問題的相關資訊,例如問題規模或受影響的區域。
- 下一次更新的預計時程。
- 問題修正進度,例如何時發現根本原因或是否有替代方案。
緩解或修正措施
只有當 Google 確定目前實施的變更能排解系統受到的影響,才會將問題視為「已修正」。在 Google 再次處理網站之前,網站可能還是會受到影響。
在問題處理期間,網站可靠性工程團隊會嘗試緩解問題。「緩解措施」指的是減少問題的影響或影響範圍,例如向受影響的搜尋系統提供額外的內部資源,或為網站擁有者提供解決方法。
搜尋關係團隊會盡可能找出替代方案並通知您。「替代方案」是您可以用來避開問題以解決基本需求的操作步驟。舉例來說,解決方式可能是使用其他 DNS 伺服器。
常見問題
通知問題時會發生什麼事?
偵測到 Google 搜尋相關問題時,搜尋關係團隊和搜尋工程團隊會合作解決問題並告知您。
通知最新消息時會發生什麼事?
發現排名系統更新時,請點選以下連結 (如有提供) 以進一步瞭解此更新內容,以及任何需要考慮的指引。通常您都不需採取任何行動。
會列出哪些排名更新?
這個資訊主頁會列出 Google 搜尋近期與網站擁有者相關的排名更新事項。如要進一步瞭解 Google 如何改善搜尋功能,以及我們分享更新資訊的原因,請參閱《Google 如何更新搜尋功能》這篇網誌文章。您也可以前往我們的網誌,進一步瞭解 Google 搜尋的最新消息。
系統發生問題,但資訊主頁並未列出。
該問題可能與您的網頁無關,也可能只有少數搜尋者或網站受到影響。如果您是網站擁有者,可以針對資訊主頁中未列出的問題,前往 Google 搜尋中心產品討論社群與我們聯絡。如果您在使用 Google 進行搜尋時遇到任何問題,請造訪 Google 搜尋說明論壇。
資訊主頁中記載的問題可在「摘要與歷史記錄」頁面中取得,保存時間為 5 年。按一下摘要列,即可查看註解相關貼文。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-04 (世界標準時間)。
[null,null,["上次更新時間:2025-08-04 (世界標準時間)。"],[[["\u003cp\u003eThe Google Search Status Dashboard provides information on Google Search systems and their performance, including outages, disruptions, and updates.\u003c/p\u003e\n"],["\u003cp\u003eYou can use the dashboard to see if any reported issues may be affecting your site's performance or search visibility.\u003c/p\u003e\n"],["\u003cp\u003eGoogle shares updates about ranking changes and other system information to help website owners understand and adapt to search improvements.\u003c/p\u003e\n"],["\u003cp\u003eSubscribe to the RSS feed or check the Summary and History page to stay informed about past and current issues with Google Search.\u003c/p\u003e\n"],["\u003cp\u003eIf you are experiencing an issue not listed on the dashboard, you can contact Google Search Central or the Google Search help forum for assistance.\u003c/p\u003e\n"]]],["The Google Search Status Dashboard displays the status of Google Search systems and ranking updates. It communicates issues affecting multiple sites or users, using statuses like \"Available,\" \"System Information,\" \"System Disruption,\" and \"System Outage.\" Upon detection, the Search Relations and engineering teams investigate, provide updates, and work towards mitigation or a fix. The dashboard lists ranking updates, and users can subscribe for notifications or find historical data from the past 5 years.\n"],null,["# How to Use the Google Search Status Dashboard | Google Search Central\n\nUsing the Google Search Status Dashboard\n========================================\n\n\nThe [Google Search Status Dashboard](https://status.search.google.com) provides\nstatus information on the systems that power Google Search. The dashboard shows issues that\naffect many sites or users, so if you see an annotation in the dashboard, it may be related to\nthe change in your site's performance.\n\n\nThe dashboard also shows the latest ranking updates made to Google Search that are relevant to\nwebsite owners. To learn more about how Google makes improvements to Search and why we share\nupdates, check out our blog post on\n[How Google updates Search](https://blog.google/products/search/how-we-update-search-improve-results/).\nYou can also find more updates about Google Search on [our blog](/search/blog).\n\n\nTo get notified about issues and updates, you can subscribe to\n[our RSS feed](https://status.search.google.com/en/feed.atom).\n\n[View the Dashboard](https://status.search.google.com)\n\nLifecycle of an issue\n---------------------\n\n\nWhen an issue with Google Search is detected, the Search Relations team and Search engineering\nteam work together to resolve the issue and communicate it to you:\n\n1. [Detection and initial response](#detection)\n2. [Investigation](#investigation)\n3. [Follow up](#follow-up)\n4. [Mitigation or fix](#fix)\n\nDetection and initial response\n------------------------------\n\n\nThe Search Relations team monitors the status of Google Search systems by looking at many\ndifferent types of signals (including [internal monitoring](https://sre.google/sre-book/monitoring-distributed-systems/)\nand feedback from the community). In the event of a widespread issue, the Search Relations team\nupdates the dashboard. A widespread issue means there's something affecting a large number of\nsites or users.\n\n\nThe status dashboard may use the following statuses:\n\n| Status definitions ||\n|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------|\n| Available | The system is generally working and available. |\n| System information | There's been an update or change to a system (for example, a ranking update started rolling out, or Googlebot started crawling over HTTP/2). |\n| System disruption | Websites may experience degraded system performance due to a common third-party (for example, DNS servers). |\n| System outage | The system isn't functioning to a large extent, and the issue is affecting a large number of sites or users. |\n\nInvestigation\n-------------\n\n\nSearch engineering teams are responsible for investigating the root cause of issues. For more\ninformation, see [Chapter 12 of the Site Reliability Engineering Book](https://sre.google/sre-book/effective-troubleshooting/).\n\nFollow up\n---------\n\n\nWhile an issue is ongoing, the Search Relations team provides regular updates. Updates may\ninclude:\n\n- Information about the issue, such as the scale of the issue or regions affected.\n- Timeline for when you can expect the next update.\n- Progress towards fixing the issue, such as when the root cause has been found, or if there are workarounds.\n\nMitigation or fix\n-----------------\n\n\nAn issue is considered *fixed* only when changes have been made that Google is confident\nwill end the impact in the system. Sites may still experience effects until Google can reprocess\nsites again.\n\n\nWhile an issue is in progress, the Site Reliability Engineering team attempts to mitigate the\nissue. *Mitigation* is when the impact or scope of an issue can be reduced, for\nexample, by providing additional internal resources to affected Search systems or by providing\nworkarounds for website owners.\n\n\nWhen possible, the Search Relations team finds and communicates workarounds. *Workarounds*\nare steps that you can take to solve the underlying need despite the issue. For example, a\nworkaround might be to use a different DNS server.\n\nFAQs\n----\n\n### What happens if an issue is noted?\n\n\nWhen an issue with Google Search is detected, the Search Relations team and Search engineering\nteam work together to resolve the issue and communicate it to you.\n\n### What happens if an update is noted?\n\n\nWhen a ranking system update is noted, follow the link (when provided) to learn more about the\nupdate and any guidance to consider. Often, there's no action needed.\n\n### What ranking updates are listed?\n\n\nThe dashboard lists the latest ranking updates made to Google Search that are relevant to\nwebsite owners. To learn more about how Google makes improvements to Search and why we share\nupdates, check out our blog post on\n[How Google updates Search](https://blog.google/products/search/how-we-update-search-improve-results/).\nYou can also find more updates about Google Search on [our blog](/search/blog).\n\n### I'm experiencing an issue, but it's not listed in the dashboard.\n\n\nThe issue may be isolated to your web pages, or it may be impacting a limited number of searchers\nor websites. If you're a website owner, you can\n[contact us in the Google Search Central help community](https://support.google.com/webmasters/community)\nabout any issues you are experiencing that are not listed on the dashboard. If you're experiencing\nissues with your searches on Google, visit the [Google Search help forum](https://support.google.com/websearch/community).\n\n### Where can I find information about past system statuses?\n\n\nIssues and updates reported on the dashboard are available on the\n[Summary and History page](https://status.search.google.com/summary)\nfor 5 years. Click a summary row to review the posts about the annotation."]]