Personal webmaster: Talking about the impact of Trojan events on SEO

Network security for SEO impact, seems to have been a cliché of the topic, however, I would like to talk about my personal experience, trying to give the old topic to bring a wisp of fresh breath.

Now network security on the impact of SEO more and more, the recent purple field event is a typical case. And do not say that the server shut down or slow network speed will have a huge impact on the site simply hanging horse Such things, on the site hurt very much. I've had a very serious experience these days. A few days ago, a Web site management, due to the hanging horse caused by Google to screen the site.

I was puzzled when the administrator of the site looked at the traffic statistics system in the morning of 9.11 and told Google that the traffic was completely gone. If Google traffic suddenly disappears, there are several possible reasons for this:

1 Web site Cheating by Google down the right or directly deleted;

2 The website of the Trojan, by Google shielding;

3 The website or traffic system out of error and fault, unable to access and statistics;

When I came back from the seaside to deal with, the date is already 9.13. I checked them in the order of 1, 2 and 3. found that the Site keyword collection and rankings did not change, but see the results of the search has such a hint: "The site may damage your computer," when I clicked the URL to go in, found by Google to intercept, can not reach the site. Description of the site hanging horse up. Through Google Admin backstage, I found that Google crawler in the 9.9 day of the 4 o'clock in the morning to crawl the site page, this time just happened to the site was put on the Trojan horse. But the real interception flow started at 9.11.

So, roughly sorted out the contact shielding ideas:

First, delete the site page of the Trojan, and then through a series of methods to let Google know as quickly as possible, to update the site to retrieve the page, so as to remove the screen as soon as possible. The train of thought was certain. The next step is to carry out specific implementation.

The specific steps are as follows:

1 Clear the Trojan in the webpage

Delete existing pages in the Trojan, there are mainly such similar code:

<iframe ... or ...xxx.js></script>.

Appear above these characteristics of the code, if it contains the URL is not their own site, it is basically a Trojan horse. We are more common Trojan is <iframe, the home page and other major pages of the source code for inspection, with Notepad to open these pages, to "<iframe" for the keyword search, find after you can see if it is hanging horse code. However, experienced hackers, will write a piece of code to the whole line of the horse code encryption, so we can hardly find the Web page of the horse code. At this point, all Web pages can be sorted by the modified time, if there are individual pages are modified, we can quickly find.

2) Stimulate Google to update quickly

The Trojan is cleared, Google is still blocked. Try to get Google Crawler to retrieve the site again and update the search results. In this way, the screen of the site can be lifted. The following are some of the ways to stimulate Google's updates:

1 continue to update the article on the homepage of the website;

2 Submit site map to Google again;

3 for the site to find some high-quality outside the chain;

4) Application for review. When the site has a virus, the Google Webmaster tools in the "diagnostics" page will have a hint, that is, the site contains malicious code, and then you will be prompted to "apply for approval" to fill in the relevant information submitted.

Above some of the means to stimulate Google Crawler can "quickly arrive at the scene", quickly update the site's search results.

After I have arranged the above ideas, I will let the webmaster of the website deal with this matter in accordance with the relevant details on the 9.14 day. Until 9.21,google lifted the shield for the site. Google's background found that on the day of 9.14, the company crawled through a Web page again. may be catching up with the Site page update. Starting from 9.14 to perform the lifting of the work operation to 9.21 was relieved, just went through 1 weeks.