I'm wondering what the effects/benefits/issues are with linking Website
and Organization
structured data (specifically in JSON-LD).
On the homepage of my site I have something like this:
<script type='application/ld+json'>
[{
"@context":"http://schema.org",
"@type":"Organization",
"@id":"https://example.com/",
"url":"http://example.com",
"name":"My site",
"logo":"https://example.com/logo.jpg",
"sameAs": [
"https://www.facebook.com/example/",
"https://twitter.com/example"
]},
{
"@context":"http://schema.org",
"@type":"WebSite",
"@id":"https://example.com/",
"url":"https://example.com",
"name":"My Site",
"potentialAction":{
"@type":"SearchAction",
"target":"https://example.com?searchQuery={search_term_string}",
"query-input":"required name=search_term_string"
}
}]
</script>
In this case I've connected the Website
and Organization
with the same ID. I've noticed in the Structured Data Tool, Google will combine this into one data type:
I'm using Website
for the potential benefits of the site search box and I'm using Organization
for the benefits of contact point and linking to social accounts.
My question is: is this a good idea? Is there any reason to not connect these two items in structured data? What implications are there to link these items vs. keeping them as separate IDs?
@id
?