schema.org

I'd like to place a Schema.org Organization item on my website. Should I place the JSON-LD only on the contact page or can I add it to every page of the website? What is the best solution? With Schema.org, you would typically provide structured data about what is relevant to the current page. Assuming that it’s the website of the organization, you could specify your Organization as value for these properties: publisher (for WebSite , for every WebPage ) about and mainEntity (for WebSite , for the WebPage on the homepage, for the AboutPage ) author (for Article , BlogPosting etc.) (There are

The data markup Schema.org for search sites like Google, Yahoo!, Bing and Yandex is great for snippets. However, I perceive that most of webmasters use Microdata and almost never use JSON-LD . I learned about JSON-LD recently and I have some doubts: Could I use it without compability problems with search engine? unor There can’t be a general answer: Each consumer (search engine, tool, etc.) has its own conditions (what it supports for which feature). Each syntax (JSON-LD, Microdata, RDFa, etc.) has its own advantages and disadvantages. Specific example to illustrate the problem: Google

Is there a proper way to show multiple events on one page in Schema.org? Ideally, we don't want a page for each event. Here is a sample structure of what we want: <div itemscope itemtype="http://schema.org/Event"> <div itemprop="name"><h2>Chili Cookoff</h2></div> <div itemprop="location" itemscope itemtype="http://schema.org/PostalAddress"> <h3><span itemprop="addressLocality">Manhatten</span>, <span itemprop="addressRegion">New York</span> - <span itemprop="addressCountry">US</span></h3> </div> <div> May, 1st 2014 - May 4th, 2014 <meta itemprop="startDate" content="2014-05-1:00.000"> <meta

I have a site which has three places where I would use Schema.org’s Organization ( itemtype="http://schema.org/Organization" ): the contact information with the affiliation for the contact person the site logo a profile for another organization How will search engines tell these three apart? The first two point to the same organization, but in different contexts. The last one does not represent our site at all but is a detailed profile for another organization. Will search engines know which ones refer to us and which one doesn't? unor If it’s the same entity (on the same document ) you

When I attempt to validate my structured data using Google's Structured Data Testing tool, I get an error: The attribute publisher.itemtype has an invalid value. I am getting that on this line: <meta itemprop="publisher" content="My Real Name Here" /> How do I provide a valid value for this property? The expected value of the publisher property is another item ( Organization or Person ). While Schema.org always allows to provide a string value (like you do), Google might require a certain value type for one of their search features (e.g., an Organization value for their Articles rich result

I have a link that looks like this: <a href="//href" itemscope itemtype="http://schema.org/Product"> <img src="src" itemprop="image"> </a> I'd like to put itemprop="url" in the <a> tag, but it contains the itemscope for that product. Can I put that at the same level as itemtype= ? Or, do I either need to wrap the whole thing in a div to make it work, or use a <meta> tag for the itemprop="url" microdata? Thanks! You can have itemprop and itemscope on the same element, but it will mean something different. In this example, a Product item has the url property: <div itemscope itemtype="http:/

After reading thousand of posts, questions, blog articles and opinions, I'm still a bit confused about how to markup a web page with microdata. If the main purpose of microdata is to help search engine to better understand the content of a web page (and web page is assumed implicitly), is it correct to start with itemtype Webpage in the body element, and then continue to markup the rest of nested elements defining which is the main entity, or is it better to start with an itemtype that is ideally the main topic of the web page and associate properties at the top level, or is better to have