\n The price of freedom from malware is eternal vigilance. This article contains tips and
\n pointers for preventing malware infection. However, it is by no means exhaustive, and Google
\n encourages website owners to conduct more thorough research as well.\n <\/p>\n
\n Many of the features of Search Console can help you identify potential problems. For example:\n <\/p>\n
site:<\/code> search operator<\/a>
\n to see what pages Google has found on your site. It’s always a good idea to do this
\n periodically to see whether anyone has snuck unexpected pages or content on your site. If
\n you see unknown pages on your site, or topics that you didn’t write, you may have been
\n hacked. If you’re not already familiar with the site:<\/code> search operator, it’s a
\n way for you to restrict your search to a specific site. For example, the search
\n site:developers.google.com<\/code><\/a>
\n will return results only from the Google Developers site.\n <\/li>\n- \n The
\n Security Issues report<\/a>
\n shows any hacked pages that Google has identified on your site, and instructions on how to
\n fix the problem.\n <\/li>\n- \n If Google detects malware on your site, you’ll see a notification in the
\n message panel in
\n Search Console<\/a>. To ensure that you’re notified quickly, you can have your messages
\n forwarded to your email account<\/a>.\n <\/li>\n<\/ul>\nSecurity checklist<\/h2>\n
In addition to monitoring your site regularly, we also recommend the following:<\/p>\n
All website owners<\/h3>\n\n- \n Choose good passwords.<\/b>
\n The Google account guidelines<\/a>
\n are helpful.\n <\/li>\n- \n Pick third-party content providers very carefully.<\/b>
\n Make sure that third-party apps and ads on your site are from trusted and legitimate
\n sources. A trusted and legitimate source provides support and contact information on their
\n website.\n <\/li>\n- \n Contact your hosting company or publishing platform for support.<\/b>
\n Most companies have helpful and responsive support groups and\/or security pages. If a
\n security page or site has an RSS feed, subscribe to it to make sure you stay up to date.\n <\/li>\n- \n Keep all of your computers safe. Especially when working on a website, make sure that your
\n local workstation has up-to-date software, is clean from viruses, trojans, or similar malware
\n and has recently updated anti-virus software installed.\n <\/li>\n<\/ul>\nWebsite owners with server access<\/h3>\n\n- \n Check your server configuration.<\/b>
\n Apache has some
\n security configuration tips<\/a>
\n on their site and Microsoft has some
\n tech center resources for IIS<\/a>
\n on theirs. Some of these tips include information on directory permissions, server-side
\n includes, authentication, and encryption.\n <\/li>\n- \n Make a backup copy of your
.htaccess<\/code> file<\/b>
\n (or other access control mechanisms depending on your website platform). Use your backup
\n file to recover if the following fails. Be sure to delete the backup file once you are
\n finished.\n <\/li>\n- \n Stay up-to-date with the latest software updates and patches.<\/b>
\n There are lots of tools that make building a website easy, but each one adds some risk of
\n being exploited. A common pitfall for many website owners is to install a forum or blog on
\n their website and then forget about it. Much like taking your car in for a tune-up, it’s
\n important to make sure you have all the latest updates for any software program you have
\n installed. Make a list of all the software and plug-ins used for your website, and keep
\n track of the version numbers and updates. Even if you’re diligent and keep all your website
\n components updated, you may still be vulnerable if your web hoster has not installed the
\n most recent operating system patches. This problem affects not only small sites; there have
\n been warnings on the websites of banks, sports teams, and corporate and government websites.\n <\/li>\n- \n Keep an eye on your log files.<\/b>
\n Making this a habit has many great benefits, one of which is added security. For example,
\n unfamiliar URL parameters (like =http:<\/code> veya =\/\/<\/code>) or spikes in
\n traffic to redirect URLs on your site may indicate that a hacker is exploiting
\n open redirects<\/a>. Also, bear
\n in mind that hackers often try to alter log files. Take measures to protect these files from
\n attack. For example, you can move these files from their default location, making it harder
\n for hackers to find them.\n <\/li>\n- \n Check your site for common vulnerabilities.<\/b>
\n Avoid having directories with open permissions. This is like leaving the front door to your
\n home wide open.<\/p>\n\n Also check for any
\n XSS<\/a>
\n (cross-site scripting) and
\n SQL injection<\/a> vulnerabilities.\n <\/p>\n<\/li>\n- \n Use secure protocols.<\/b>
\n Google recommends using SSH and SFTP for data transfer, rather than plain text protocols
\n such as telnet or FTP. SSH and SFTP use encryption and are much safer.\n <\/li>\n- \n Keep up to date on the latest security news.<\/b>
\n The
\n Google Security Blog<\/a>
\n provides useful information about online security and safety, as well as pointers to other
\n resources. The government site
\n US-CERT<\/a>
\n (United States Computer Emergency Readiness Team) provides technical security alerts and
\n tips.\n <\/li>\n<\/ul>\n\n\n If you’re a Search Console user and are having trouble with persistent or unfixable security issues on your site, you can let us know.\n <\/p>\n