Without linking them
You could of course simply use a LocalBusiness
for the taxi company on the taxi site, and a LocalBusiness
for the tour company on the tour site, without linking them in any way.
<!-- on the taxi site -->
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "LocalBusiness",
"name": "Taxi company",
"address": {
"@type": "PostalAddress",
"streetAddress": "Example street 1"
}
}
</script>
<!-- on the tour site -->
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "LocalBusiness",
"name": "Tour company",
"address": {
"@type": "PostalAddress",
"streetAddress": "Example street 1"
}
}
</script>
Linking them
But if you want to convey that the taxi company is the parent company, and the tour company is its child company, you can use the parentOrganization
/subOrganization
properties.
You can do this without repeating the taxi information on the tour site and vice-versa. Simply give each LocalBusiness
a URI (via @id
in JSON-LD) and reference it as the value of the properties.
<!-- on the taxi site -->
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "LocalBusiness",
"@id": "http://taxi.example.com/#company",
"name": "Taxi company",
"address": {
"@type": "PostalAddress",
"streetAddress": "Example street 1"
},
"subOrganization": {"@id": "http://tours.example.com/#company"}
}
</script>
<!-- on the tour site -->
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "LocalBusiness",
"@id": "http://tours.example.com/#company",
"name": "Tour company",
"address": {
"@type": "PostalAddress",
"streetAddress": "Example street 1"
},
"parentOrganization": {"@id": "http://taxi.example.com/#company"}
}
</script>