Tag Info

New answers tagged

3

Similar to adding multiple string/URL values: by using an array. <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "Organization", "address": [ { "@type": "PostalAddress" }, { "@type": "PostalAddress" } ] } </script>


0

What is the correct usage of using the brand schema from schema.org? There is not one "correct usage" – it depends on what you want to convey. If you want to say something about a brand, you can use Schema.org’s Brand type. The Product type has the property brand, which takes a Brand item as value. This would allow you to reference the Brand from each ...


0

Last week’s Schema.org release (version 2.0) introduced two relevant properties: mainEntity mainEntityOfPage This allows you to omit WebPageElement (which is not very useful in the first place) and use something like this: <body itemscope itemtype="http://schema.org/WebPage"> <!-- properties about the web page --> <div ...


2

No, your example would mean that it’s an schema:Article and a pto:Dog_breed. To state what the schema:Article is about, you could use its about property. The elaborate version would be: <article itemscope itemtype="http://schema.org/Article"> <div itemprop="about" itemscope itemtype="http://schema.org/Intangible"> <link ...


2

I’m assuming you are using the vocabulary Schema.org and have something like this: <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "LocalBusiness", "url": "http://example.com/" } </script> Here the url property belongs to the LocalBusiness item. So it should give the URI of the local business, no matter on ...


0

I think the main entity should be Offer. This allows you to specify the prices and start/end dates. If you need to specify general data about the offered service/product, you could use the itemOffered property, which takes a Product as value. That’s fine, I guess, as Product is still defined to include both, products and services: Any offered product ...


2

Your use of additionalType in the first snippet is correct. An example where additionalType is used can be seen on Schema.org’s IndividualProduct: <script type="application/ld+json"> { "@context": "http://schema.org", "@id": "#product", "@type": "IndividualProduct", "additionalType": "http://www.productontology.org/id/Racing_bicycle", ...



Top 50 recent answers are included