Yesterday when i searched for the site:sitename.com on google the results were also amazing for me(check my tweet here). “Site:www.honeytechblog.com was dropped from your search because it is not supported for this type of search”. @gmishra suggest me that it may be the google dancing issues and it was recovered after about 30 minutes of shaking and palpitation.

googleissue2 thumb Google is googling with strange results google may harm

Today twitter is buzzed with #googmayharm and while checking my tweets i came across the tweet of @unitechy where she tweet about google behaviors.I suddenly checked for google on the google search and the results were astounded. “This site may harm your computer” – We are not expecting the malwares issues for the worlds most knock-down company.

google Google is googling with strange results google may harm

Similarly,

These sort of results yield the series of questions like Google traffic will gone be halt? Whats up with the results? Is it a google dancing?

Please suggest if you have some better answers or you already encountered with the similar situations.

Updated:Google search recovered for me.Probably this may be the server update or dancing.Check out #googmayharm for detailed story of the scene.

Latest Update: Google says it his postWe maintain a list of such sites through both manual and automated methods. We work with a non-profit called StopBadware.org to come up with criteria for maintaining this list, and to provide simple processes for webmasters to remove their site from the list.

We periodically update that list and released one such update to the site this morning.

Unfortunately (and here’s the human error), the URL of ‘/’ was mistakenly checked in as a value to the file and ‘/’ expands to all URLs. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes.”