透過網站管理員工具查看垃圾網站人工介入處理
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
2014年2月24日星期一
原文:
View manual webspam actions in Webmaster Tools
作者:
Matt Cutts
, Distinguished Engineer
我們一向致力從使用者的搜尋結果中
排除垃圾內容
,具體做法包括改善垃圾網頁檢索演算法,以及針對違反
品質指南
的網站採取人工介入處理行動。許多網站管理員都想要瞭解,自己的網站是否受到垃圾網站人工介入處理行動影響,於是我們推出了一項新功能,希望對您有所幫助。如果垃圾網頁管理小組所採取的人工介入處理行動對網站在 Google 網頁搜尋結果中的排名直接造成影響,網站管理員工具中的人工介入處理檢視器會顯示相關資訊。如要試用這項功能,請前往
網站管理員工具
,然後在 [搜尋流量] 部分中按一下 [人工介入處理]。
您可能會看到「找不到任何垃圾網站人工介入處理項目」訊息。根據最近的索引分析結果,在我們已檢索的網域中,遭到人工介入移除垃圾網頁的網站比例遠低於 2%。如果您看到這則訊息,表示您的網站並未被視為垃圾網站,因此我們沒有採取人工介入移除垃圾網頁或直接降低搜尋結果排名的處理行動。
如果您的網站有一小部分出現人工介入處理項目,那麼您在網站管理員工具中可能
已經收到我們的通知
。我們會持續傳送這類通知給您,不過現在您也可以直接在線上查詢我們的內部垃圾網站系統。以下是 Google 因網站的特定部分含有「使用者濫發的垃圾訊息」而採取人工介入處理行動的範例:
在這個範例中,我們假設的情形屬於「部分相符結果」,而不是全網站相符結果。部分相符結果是指我們僅針對網站的特定部分採取人工介入處理行動。在本案例中,網站管理員面對的問題是他人在 mattcutts.com/forum/ 上製造垃圾訊息。如果網站管理員解決這項常見問題,不僅有助於恢復論壇在 Google 搜尋結果中的排名,還能改善使用者體驗。如需最新疑難排解資源,請按一下 [瞭解詳情]。
更正所有違反 Google
品質
指南的情事後,接著您可以
要求重新審查
。這項新功能簡化了重新審查要求程序,使提交作業更加流暢。現在,當您造訪重新審查要求頁面時,可查看網站的人工介入處理項目,且只有在您的網站受到人工介入處理時才能要求重新審查。如果您確實有垃圾網頁問題,只要按一下 [要求審查],即可直接透過「人工介入處理」頁面進行處理。
其實大多數的網站管理員並沒有陷入垃圾網站問題的麻煩,不過我們仍基於踴躍要求而提供人工介入處理檢視器這項功能,希望能讓大家放心。對於少數真正需要處理垃圾網站問題的人,我們希望這項最新資訊有助於更快排解您的疑難。如果您還有其他問題,歡迎透過網站管理員說明論壇與我們聯絡,或是在我們的
服務時間
洽詢客戶服務小組。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2014-02-01 (世界標準時間)。
[null,null,["上次更新時間:2014-02-01 (世界標準時間)。"],[[["\u003cp\u003eGoogle launched a new "Manual Actions" feature in Webmaster Tools to help webmasters check if their sites have received a manual webspam action affecting search rankings.\u003c/p\u003e\n"],["\u003cp\u003eFewer than 2% of domains have received manual actions for webspam, indicated by a "No manual webspam actions found" message in the tool.\u003c/p\u003e\n"],["\u003cp\u003eFor sites with manual actions, the tool provides details like the type of action and affected sections, offering resources for troubleshooting.\u003c/p\u003e\n"],["\u003cp\u003eWebmasters can use the tool to request reconsideration after addressing violations, streamlining the process by checking for existing manual actions.\u003c/p\u003e\n"],["\u003cp\u003eThe new feature aims to provide transparency, reassurance, and quicker resolution for webspam issues.\u003c/p\u003e\n"]]],["Google introduced a manual action viewer in Webmaster Tools to help webmasters identify if their site has been penalized for webspam. Accessible via the \"Manual Actions\" link, it displays whether a site has a manual removal or demotion. If an action is detected, it specifies if it's site-wide or a partial match. The viewer allows users to learn more about the issue and provides a simplified reconsideration request process, which can be initiated directly from the Manual Actions page after fixing any violations.\n"],null,["# View manual webspam actions in Webmaster Tools\n\nThursday, August 08, 2013\n\n\nWe strive to\n[keep spam out](https://www.google.com/insidesearch/howsearchworks/fighting-spam)\nof our users' search results. This includes both improving our webspam algorithms as well as\ntaking manual action for violations of our\n[quality guidelines](/search/docs/essentials/spam-policies).\nMany webmasters want to see if their sites are affected by a manual webspam action, so today we're\nintroducing a new feature that should help. The manual action viewer in Webmaster Tools shows\ninformation about actions taken by the manual webspam team that directly affect that site's\nranking in Google's web search results. To try it out, go to\n[Webmaster Tools](https://search.google.com/search-console)\nand click on the \"Manual Actions\" link under \"Search Traffic.\"\n\n\nYou'll probably see a message that says, \"No manual webspam actions found.\" A recent analysis of\nour index showed that well under 2% of domains we've seen are manually removed for webspam. If you\nsee this message, then your site doesn't have a manual removal or direct demotion for webspam\nreasons.\n\n\nIf your site is in the very small fraction that do have a manual spam action, chances are we've\n[already notified you](https://searchengineland.com/google-sent-over-700000-messages-via-webmaster-tools-in-past-two-months-113807)\nin Webmaster Tools. We'll keep sending those notifications, but now you can also do a live check\nagainst our internal webspam systems. Here's what it would look like if Google had taken manual\naction on a specific section of a site for \"User-generated spam\":\n\n\nIn this hypothetical example, there isn't a site-wide match, but there is a \"partial match.\" A\npartial match means the action applies only to a specific section of a site. In this case, the\nwebmaster has a problem with other people leaving spam on mattcutts.com/forum/. By fixing this\ncommon issue, the webmaster can not only help restore his forum's rankings on Google, but also\nimprove the experience for his users. Clicking the \"Learn more\" link will offer new resources for\ntroubleshooting.\n\n\nOnce you've corrected any violations of Google's\n[quality](/search/docs/essentials/spam-policies) guidelines, the next\nstep is to\n[request reconsideration](https://support.google.com/webmasters/answer/35843).\nWith this new feature, you'll find a simpler and more streamlined reconsideration request process.\nNow, when you visit the reconsideration request page, you'll be able to check your site for manual\nactions, and then request reconsideration only if there's a manual action applied to your site. If\nyou do have a webspam issue to address, you can do so directly from the Manual Actions page by\nclicking \"Request a review.\"\n\n\nThe manual action viewer delivers on a popular feature request. We hope it reassures the vast\nmajority of webmasters who have nothing to worry about. For the small number of people who have\nreal webspam issues to address, we hope this new information helps speed up the troubleshooting.\nIf you have questions, come find us in the\n[Webmaster Help Forum](https://support.google.com/webmasters/threads?hl=en&thread_filter=(category:search_console))\nor stop by our\n[Office Hours](/search/events#sign-up-for-online-seo-office-hours).\n|\n| **Update (12:50pm PT, August 9th):** Unfortunately we had some problems during our\n| feature deployment, so it will be another couple days before the feature is available to\n| everyone. We will post another update once the feature is fully rolled out.\n|\n| **Update (10:30am PT, August 12th):** The feature is now fully rolled out.\n\n\nPosted by\n[Matt Cutts](https://www.mattcutts.com/blog), Distinguished Engineer"]]