schema.org - w3toppers.com

Can Schema.org Expected Types be collections, too?

Every Schema.org property can have multiple values. It doesn’t necessarily make sense for some properties (e.g., birthDate), but it’s still allowed. In JSON-LD: “sameAs”: [“https://stackoverflow.com/foo”, “/bar”], In Microdata: <link itemprop=”sameAs” href=”https://stackoverflow.com/foo” /> <link itemprop=”sameAs” href=”http://stackoverflow.com/bar” /> In RDFa: <link property=”sameAs” href=”https://stackoverflow.com/foo” /> <link property=”sameAs” href=”http://stackoverflow.com/bar” /> This doesn’t necessarily mean that Google (or any other … Read more

@id vs. URL for linking JSON-LD nodes

@id (JSON-LD) (and the same goes for itemid in Microdata, and resource in RDFa) Each thing should get a different URI, and if multiple nodes are about the same thing, they should ideally reuse this URI. Note that these don’t have to be URLs, and they should often not be used as values for Schema.org’s … Read more

Schema.org/Microdata markup for list of recent posts without providing “author” / “publisher”?

It’s perfectly fine not to provide these properties. Schema.org doesn’t require any property. If Google’s Structured Data Testing Tool says that certain properties are missing, what it really means is: “If you don’t provide these properties, we won’t show the corresponding Rich Snippet or Knowledge Graph feature in Google Search” There’s no need to get … Read more

Why does Google Testing Tool use the “id” attribute to generate a URL for the Microdata item?

This is strange. It’s definitely not conforming to the Microdata Note. Apart from Microdata’s itemref attribute, HTML5’s id attribute has no special meaning in Microdata. If Google wants to use the id value anyway, they should at least generate the URL with a fragment identifier, i.e., http://www.example.com/#foobar. My guess is that they are (probably unintentionally) … Read more

Best JSON-LD practices: using multiple elements?

There is no benefit in having single or multiple data blocks, other than limitations around how you might store and manage schema data in your website. For example, you might need them separate if different components within your website are responsible for generating each data block independently. Alternatively, if your website is able to manage … Read more

Schema.org NewsArticle: invalid value for logo property

Your markup is valid HTML5+Microdata and you are using the Schema.org vocabulary appropriately. With “validator”, you probably refer to Google’s Structured Data Testing Tool. Note that errors shown in this tool don’t necessarily mean that your markup is wrong; they often mean that you won’t get a certain Google search result feature unless you provide … Read more

What is the correct use of schema.org SiteNavigationElement?

If SiteNavigationElement is meant for the whole navigation (i.e., a navigation link list), your first example is correct. If SiteNavigationElement is meant for a single navigation entry (i.e., a link in the navigation link list), your second example is correct. I think Schema.org doesn’t unambiguously define which variant is meant, as they only say: A … Read more

Can I Use Multiple ItemProps in a Span Tag for schema.org Rich Snippets?

The usual HTML way would be to use one attribute and separate several values with space characters. Looking into the Microdata specification, you’ll notice that this is the case for the itemprop attribute, too: The itemprop attribute, if specified, must have a value that is an unordered set of unique space-separated tokens […] So this … Read more

Is it possible to use the same meta tag for opengraph and schema.org

HTML+RDFa 1.1 and Microdata extend HTML5’s meta element. HTML+RDFa 1.1 (W3C Recommendation) defines: If the RDFa @property attribute is present on the meta element, neither the @name, @http-equiv, nor @charset attributes are required and the @content attribute MUST be specified. Microdata (W3C Note) defines: If a meta element has an itemprop attribute, the name, http-equiv, … Read more

Why use Schema.org microdata to mark up web page elements?

This answer is primarily about the WebPageElement types (like SiteNavigationElement). For WebPage, see my answer to the question Implicity of web page structure in Schema.org (tl;dr: it can be useful to provide WebPage, even for the current page). For WebSite, similar reasons from the answer above apply. HTML doesn’t allow you to state something about … Read more