\n increase in hacked site reconsideration requests. While we are working hard to help webmasters
\n prevent hacks in the first place through efforts such as
\n blog posts<\/a> and
\n #NoHacked<\/a> campaigns, we
\n recognize that our reconsideration process is an important part of making recovering from a hack
\n faster and easier. Here’s what we’ve been focusing on:\n<\/p>\n
- \n
- Improved communication<\/li>\n
- Better tools<\/li>\n
- Continuous feedback loop<\/li>\n<\/ol>\n
Improving communications with webmasters of hacked sites<\/h2>\n
\n Last year we launched the
\n “Note from your reviewer<\/a>”
\n feature in our reconsideration process. This feature enables us to give specific examples and
\n advice tailored to each case in response to a reconsideration request. Thus far in 2015 we have
\n sent a customized note to over 70% of webmasters whose hacked reconsideration request was
\n rejected, with specific guidance on where and how to find the remaining hacked content. The
\n results have been encouraging, as we’ve seen a 29% decrease in the average amount of time from
\n when a site receives a hacked manual action to the time when the webmaster cleans up and the
\n manual action is removed.\n<\/p>\n![\"Example](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-fe3cbb8b48f0.png\")
<\/p>\n\n We have also completed our second #NoHacked campaign, with more detailed help on preventing and
\n recovering from hacks. In the campaign, we focused on ways to improve the security on your site as
\n well as ways to fix your site if it was compromised. You can catch up by reading the
\n first post<\/a>.\n<\/p>\nBetter tools including auto-removal of some hacked manual actions<\/h2>\n
\n Last year we launched the “Fetch and Render” feature to the
\n Fetch as Google<\/a>
\n tool, which allows you to see the website exactly as Googlebot sees it. This functionality is
\n useful in recovering from a hack, since many hackers inject
\n cloaked content<\/a>
\n that’s not visible to the normal user but obvious to search engine crawlers like Googlebot.\n<\/p>\n\n This year we also launched the
\n Hacked Sites Troubleshooter<\/a>
\n in 23 languages which guides webmasters through some basic steps to recover from a hack. Let us
\n know if you have found the troubleshooter useful as we’re continuing to expand its features and
\n impact.\n<\/p>\n\n Finally, we’re beta testing the automated removal of some hacked manual actions. In Search Console
\n if Google sees a
\n “Hacked site” manual action under “Partial matches”<\/a>,
\n and our systems detect that the hacked content is no longer present, in some cases we will
\n automatically remove that manual action. We still recommend that you submit a reconsideration
\n request if you see any manual actions, but don’t be surprised if a “Hacked site” manual action
\n disappears and saves you the trouble!\n<\/p>\n![\"Example](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-e9be86bf665e.png\")
<\/p>\nSoliciting your feedback and taking action<\/h2>\n
\n Our improved communication and tools have come directly from feedback we’ve collected from
\n webmasters of sites that have been hacked. For example, earlier this year we hosted webmasters who
\n have been through the hacked reconsideration process in both Mountain View, USA and Dublin,
\n Ireland for brainstorming sessions. We also randomly sampled webmasters that had been through a
\n hacked reconsideration. We found that while only 15% of webmasters were dissatisfied with the
\n process, the main challenges those webmasters faced were in clearer notification of their site
\n being hacked and clearer guidance on how to resolve the hack. This feedback contributed directly
\n our more detailed
\n blog post<\/a> on hacked recovery,
\n and to much of the content in our latest
\n #NoHacked<\/a> campaign.\n<\/p>\n![\"Googlers](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-eefa40a8dcc7.png\")
<\/p>\n\n We will continue to support webmasters of hacked sites through the methods detailed above, in
\n addition to the
\n Webmasters help for hacked sites<\/a>
\n portal and the
\n security, malware and hacked sites section of our forum<\/a>.
\n And we’d love to hear your ideas in the comments below on how Google can better support webmasters
\n recovering from a hacked website!\n<\/p>\nWednesday, September 23, 2015 Thus far in 2015 we have seen a 180% increase in the number of sites getting hacked and a 300% increase in hacked site reconsideration requests. While we are working hard to help webmasters prevent hacks in the first place through efforts such as blog posts and #NoHacked campaigns, we recognize […]<\/p>\n","protected":false},"menu_order":83299,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24902","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24902\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27083"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24902"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24902"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}