Welcome to WebmasterWorld Guest from 54.158.252.131

Forum Moderators: Robert Charlton & andy langton & goodroi

Message Too Old, No Replies

Google SERP's 'Page 2" Link Triggered My Anti-Virus

     
10:17 pm on Apr 10, 2009 (gmt 0)

New User

10+ Year Member

joined:Aug 29, 2006
posts: 8
votes: 0


Today i almost fell off my chair, i was checking on some keywords in Google, i did a first page search and clicked page 2 at the bottom to go to the next page, then my Avast antivirus started sounding off that my CPU was being attacked by a virus.

This can be very bad for Google's PR if this is something new......

[edited by: tedster at 10:54 pm (utc) on April 10, 2009]
[edit reason] removed specific keywords [/edit]

10:58 pm on Apr 10, 2009 (gmt 0)

Senior Member

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:May 26, 2000
posts:37301
votes: 0


If the Google search results page does contain a virus, I certainly wouldn't want to publicly publish the serach terms! The best bet would be to report the event to Google - see the Google Forum Charter [webmasterworld.com] for four different avenues you can use.

However, since I got to see your search terms before I edited them, and I can report that I found no virus from the internal links on the page. So I'm not sure what's going on for you - do you check for malware regularly?

6:58 am on Apr 11, 2009 (gmt 0)

New User

10+ Year Member

joined:Aug 29, 2006
posts:8
votes: 0


Something must be triggering my Avast anti virus, its strange , because what avast does is to scan the whole page you are on. it must be a script of some sort avast is taken it to be a virus.
10:57 pm on Apr 12, 2009 (gmt 0)

Senior Member from GB 

WebmasterWorld Senior Member dstiles is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:May 14, 2008
posts: 3153
votes: 4


I don't suppose avast is pulling the old AVG trick of pre-scanning every page in the google listing regardless of whether you want to view it or not? That might cause something like this.