Should Website and Organization be linked?

by StuFu   Last Updated April 15, 2019 01:04 AM

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:

Screenshot of Structured Data Testing results

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?



Related Questions


Updated June 29, 2016 08:01 AM

Updated July 19, 2018 09:04 AM

Updated October 01, 2018 21:04 PM

Updated March 18, 2019 18:04 PM

Updated June 10, 2019 12:04 PM