Site Owner: I Am Going To Be Sued Over Wrong Data In Google's Knowledge Graph

Mar 27, 2014 • 8:23 am | comments (13) by twitter Google+ | Filed Under Google Search Engine
 

Google Knowledge GraphA Google Web Search Help thread has someone who works at a company named BeyondTrust. The company has a knowledge graph come up for a Google search on the company name.

The issue is, the CEO listed in the knowledge graph is wrong and the lawyers are getting upset according to what was posted in the Google thread.

Chris Burd, the Senior Director of Marketing at BeyondTrust, wrote:

When searching for "BeyondTrust," my company's name, the Knowledge Graph results display the name of a former CEO. We updated the Wikipedia entry for BeyondTrust on 3/4 with current information. The update has not been picked up by Knowledge Graph, though it appears the Wikipedia page for BeyondTrust was last indexed by Google on 3/19. I've submitted feedback via the KG feedback link about 4 times in the past two weeks to no avail. Just received an email from our current CEO indicating that lawyers are now involved. How do I escalate this?

Chris has done everything right but Google is slow.

Here is the Google Knowledge Graph showing the old CEO's name John Mutch:

click for full size

Here is the Wikipedia box:

click for full size

This is not a new issue, the Google Knowledge Graph is known to be updated slowly and have outdated information.

This is just interesting because Chris wrote that the CEO got a letter and the "lawyers are now involved."

Forum discussion at Google Web Search Help.

Previous story: Google Notifies Publishers Of A New AdSense Reporting Dashboard
 

Comments:

Spellcheck

03/27/2014 12:31 pm

Right

Barry Schwartz

03/27/2014 12:33 pm

I need to stop doing 3 things at once, thanks!

Paddy Displays

03/27/2014 02:24 pm

Surely if any one is liable its google as they are the ones showing the wrong info. BeyondTrust have updated all records the own (again it is not their responsibility to keep Wikipedia up-to date either, but they have done) I think BeyondTrust are just covering their bases, showing they have gone above and beyond trying to fix the issue and therefore not liable

Steve Peron

03/27/2014 02:29 pm

I wonder what the average time between knowledge graph updates are...

Durant Imboden

03/27/2014 03:31 pm

John Mutch is also listed as BeyondTrust's CEO by Forbes, in a Twitter profile, and elsewhere. Maybe he needs to learn the art of patience.

danlev

03/27/2014 08:01 pm

This is a Freebase issue, less of a Wikipedia issue. Looks like their Freebase entry was just updated today though: http://www.freebase.com/m/0640vpv

James

03/27/2014 08:14 pm

In the USA, why is the answer to everything "lawyers" or "guns"?

James R. Halloran

03/27/2014 09:12 pm

I don't really understand why lawyers would ever get involved for a miscommunication. Seems entirely dumb to me.

Tian_Mian

03/27/2014 10:20 pm

Why the fuck would BeyondTrust care? They did their due diligence taking care of a right entry in Wikipedia. Shouldn't be their problem that there's a website out there that doesn't give a shit about accuracy, which is Google in this case. If I was the CEO of BeyondTrust I'd simply tell the lawyers to go fuck themselves.

Leeza Rodriguez

03/27/2014 10:51 pm

I see that too. A user named 'snafu' updated info for Kevin Hickey in Freebase around 1:20 p. In my experience this takes a couple of days to digest.

Sam Sinton

03/28/2014 11:07 am

100% agree! They have done what is expected of them, tell the lawyers to sue Google.

wertwert

03/28/2014 04:14 pm

guns are only the answer if it moves. Lawyers are for everything else.

Evelina Jankauskyte

04/07/2014 10:33 am

I will try find the link but a guy provided a case study, he said he entered all of the information in December on freebase and saw results end of Jan early Feb on the knowledge graph. Our company had 3 duplicate types on Freebase and its taken a month for them to just be merged so yeah, I think there is still quite a bit of waiting around between updated.

blog comments powered by Disqus