Search queries being used against accused murderer in court |
A man currently on trial accused of murdering his wife is having search queries made on his computers scrutinized.

Forensic recovery from hard drives revealed some disturbing, coincidental searches related to his alleged crime:
Investigators are also focusing e-mails to women they said Petrick was having affairs with and a download of a document entitled “22 ways to kill a man with your bare hands.” Authorities claim that Petrick looked up the depth and topography of a lake where the body of his wife Janine Sutphin was found — before he reported her missing.
It is unknown whether Google participated in the investigation in any active capacity or not. A subpoena would have been all that was necessary to get them to assist, I’m guessing.
Mike from Techdirt jokes: “Either way, for the potential criminals among our readers, perhaps you shouldn’t Google up stuff related to your crime before committing it.”
For those of us logged in, Google does maintain a (permanent?) record of search history. I was curious what my recent search history would say about me? You can choose to “Pause” recording of the search history or “Remove” it at any time (pictured above).
Quickly realized when I came across queries like “mold mildew out of laundry” that I never searched for that (aha! suddently knew what my wife was up to). Also, there were some searches made by others at Mind Camp this last weekend that I didn’t make, but had offered up my Tablet for use. Nothing sinister of course. No Perry Mason moments in my search engine history.
Stories like this one will certainly help sell that erase your tracks type software but that won’t do anything about third party hosted and saved historical information. And since passwords can be stolen and people can lend their computers to others (and not pause or stop search logging), I’m not sure how empirical this evidence can or should be used in court. If I was on a jury I’d be looking at digital evidence like search queries with a squinted eye. You?
Did this post make you go hmm?
Related Posts
- Now Google remembers your searches
- Number of Google searches per week?
- Making the Google Trends volume cut: Gates, Winer, Scoble, Godin
- Google Zeitgeist 2002 searches, looking back
- You know there are network connection problems when…
- Article on Google search query holes




Hmmmm…now I feel the need to check out my search history. Thanks for giving me one more bit of paranoia!
Comment by Suzi Chen — November 12, 2005 @ 6:12 pm PST
[…] Seems a nut job on trial for murdering his wife is in hotter water because of his Google searches. First of all I feel awful for the families that have to deal with this. With that said, with bread-crumbs labeled “neck snap break,” “bloodfest666″ and, if there was any doubt, “22 ways to kill a man with your bare hands” you’d have to have a jury of drunk Monkeys not to see the guy is standing in the right field of normal. […]
Pingback by An Idiot’s Guide to Web 2.0 » Blog Archive » Neck Break Snap — November 12, 2005 @ 11:08 pm PST
[…] Seems a nut job on trial for murdering his wife is in hotter water because of his Google searches. First of all I feel awful for the families that have to deal with this. With that said, with bread-crumbs labeled “neck snap break,” “bloodfest666″and, if there was any doubt, “22 ways to kill a man with your bare hands” you’d have to have a jury of drunk Monkeys not to see the guy is standing in the right field of normal. […]
Pingback by The Rabbit Trail » Neck Snap Break — May 14, 2006 @ 2:16 pm PST
[…] Seems a nut job on trial for murdering his wife is in hotter water because of his Google searches. First of all I feel awful for the families that have to deal with this. With that said, with bread-crumbs labeled “neck snap break,” “bloodfest666″and, if there was any doubt, “22 ways to kill a man with your bare hands” you’d have to have a jury of drunk Monkeys not to see the guy is standing in the right field of normal. […]
Pingback by FunkWadCuintWhich » Blog Archive » Neck Snap Break — July 18, 2006 @ 3:58 pm PST