Structured Data markup that communicates one organization acquired another

[barry...@gmail.com]

Hello all,

Trying to figure out the simplest/most effective way to use schema.org vocab to markup  that one organization was acquired/merged with another.

Was reviewing a Google knowledge graph recently and noticed that GKG in question still shows the old company domain as the URL. While that URL does 301 redirect to the proper domain and does suggest that the GKG does reflect some sort of acquisition or merger, the information isn't quite accurate.

Ideally I'd be able to update the URL to show the proper new domain and I was thinking I could use sameAs property to better establish the relationship between old domain and new domain - but none of the current Organization or Corporation properties really speak to this kind of relationship between business organizations.

Any help or guidance is appreciated.

Thank you in advance.

[Denver Prophit Jr.]

sameAs should never be used on a domain redirect. A simple 301 redirect and provide feedback on the KG that the domain name has changed. 

[Richard Wallis]

Agree with Denver on sameAs - it's not what you want here.

As you identify, the properties of the Organization based types do not really cover this scenario. member/memberOf & parentOrganization/subOrganization possibly come close.

Just changing the url property to that of the new site may be sufficient?

~Richard

Richard Wallis

Founder, Data Liberate

http://dataliberate.com

Linkedin: http://www.linkedin.com/in/richardwallis

Twitter: @rjw

--
You received this message because you are subscribed to the Google Groups "Semantic Search Marketing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semantic-search-ma...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/semantic-search-marketing/00467b89-c804-4aa4-ba5f-6472875b4f6fn%40googlegroups.com.

[Barry Rolapp]

Richard and Denver, appreciate you both weighing in. We've got the 301 up and running properly.

We've got the URL property on the live domain, and I already plan on expanding the current organization level data to be more robust, just wanted to make sure I wasn't missing anything - and it sounds like I am not.

I also found out what was causing the issue with the Knowledge Graph reporting the wrong URL - wikidata and wikipedia hadn't been updated. Hopefully having those data points match the structured data we already have on the homepage will help.

The wikidata /wikipedia article also already showcase the rebranding/merger so I'll just have to be happy with that for now.

Thank you!

To view this discussion on the web visit https://groups.google.com/d/msgid/semantic-search-marketing/CAD47Kz5TUUz%3DcVVLdh5b4V%2BjaRF3KRGGtSET3wLSQQL_S3UbPw%40mail.gmail.com.