Malware on your own website – An important tool for webmasters from Google

Meanwhile, it happens more often that for an infection of a Windows machine you don’t have to run a file or confirmation of an installation in a web browser (player, etc.), but just by the simple browsing a Web page it can happen. Become a classic in this context, the Federal Police virus that requires no conscious action by the user. Google offers a tool with which to test the own website.
Now, Matt Cutts, a top executive at Google, informs the SEO community and other interested parties about new trends, features and internals of Google via the usual channels such as Twitter, Google +, own blog and on google webmaster central-blog. On the Webmaster Central blog is a new video and a German translation of about malware and what you can do as a webmaster. There are really good tips here, the posts from Matt Cutts, are somewhat more general, and held in the subjunctive, but it is a reputable source of information for all Internet marketers.
So you can easily check whether your website from Google has been classified as dangerous. Namely, by typing the following into the address bar of your web browser: / safe browsing / diagnostic site =?
Example: / safe browsing / diagnostic site =
Then you get some data on the website and when Google has recently been investigated.
But there are two other ways to check the website, which are described in detail in the post. This involves features in Webmaster Tools. An application, which should use every webmaste, as the information that you get there via its website, are really important for search engine optimization.
In Webmaster Tools, there is a point to „diagnosis“ and then „Check malware“ and the possibility of „Fetch as Googlebot. Both features are explained in the post. It should be as an operator of one or more websites to make these checks, it’s no big hassle. To prevent the website being hacked and infected advises Cutts, WordPress and other CMS to provide each with the latest updates, and SQL versions on the Web server should be current.