Google recently released a blog post, #NoHacked: A year in review, on their Webmaster central blog talking where they share how websites security changes in 2016.
Hacking is on fire
Hacked websites recorded a 32% growth compared to 2015, and Google hinted that it’s just the beginning of that’s to come.
And we’ve witnessed it on late 2016 and early 2017, where some pretty nasty and aggressive hacking campaign went on. The most noticeable one is the WordPress API security flow that saw nearly 2M websites defaced in 10 days.
More fear than harm
86% webmasters manage to clean up their websites and apply for reconsideration to remove the hacking flag on search results, which is kinda recomforting.
Almost 2/3 never got notified in time by Google because they never registered to the Search ConsoleA Google web service that helps track your search engine related metrics, including hacking flags. .
If you want to stay ahead if the worst happen, go now and make sure to register to Google Search Console.
A more refined resources base
Google took this opportunity to report the improvement done on the knowledge base related to websites’ security and general hacking.
It’s still too theoretical and mainly educational. I still find all the information they share there won’t be helpful for regular users, and it lacks real-world example and applications.
But it’s still a valuable resource and a great starting point. Here are a couple of good pages to check:
- Top ways websites get hacked by spammers
- Glossary for Hacked Sites
- FAQs for Hacked Sites
- How do I know if my site is hacked?
Care to see the full article?Check out #NoHacked: A year in review