tag:blogger.com,1999:blog-770618155822587206.post8069920054141821921..comments2008-05-06T12:18:34.015-07:00Chris (Anzel Online)http://www.blogger.com/profile/15186851266728130358noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-770618155822587206.post-6548285495585978752008-05-06T12:18:00.000-07:002008-05-06T12:18:00.000-07:00The screen shot was not intended to show a virus at Google. It was intended to show a safeguard was being incorrectly provoked.<BR/><BR/>I did in fact explore the possibility of this being a problem with my system. However after checking with my peers and later checking with Google, I found that it was not a problem that I was exclusively experiencing (inside or outside my local area).<BR/><BR/>untmarkb, your comment was left after I had posted an update saying that I had talked to Google AM’s directly. You would think that a "Director of Internet Marketing" would have the contacts within the company that dominates our industry to verify my claim.Chris (Anzel Online)http://www.blogger.com/profile/15186851266728130358noreply@blogger.comtag:blogger.com,1999:blog-770618155822587206.post-45049519046779069502008-05-06T11:17:00.000-07:002008-05-06T11:17:00.000-07:00The screenshot you show has nothing to do with a virus at Google. It would be more likely that you might have a virus. <BR/><BR/>The main reason this screen would show is because you or someone else on your IP is sending automated requests to Google and Google is blocking your access.<BR/><BR/>This is common for rank checking software such as WebPosition as well as for scripts that are scraping search results, etc.<BR/><BR/>So you might want to look at your self before assuming this is a Google issue.untmarkbhttp://profile.typekey.com/untmarkb/noreply@blogger.com