Hot answers tagged

8

schema.org/BlogPosting image permits ImageObject and URL, however Google only permits ImageObject, hence the error. The intended markup is: <!-- my code --> <div itemprop="image" itemscope itemtype="http://schema.org/ImageObject"> <img src="image.jpg" itemprop="url"> </div>                 Another discrepancy is ...


3

you should be clear, why do you want to make use of structured data? to go through the testing tool or to deliver correctly formatted and standard conform structured data to search engine, so your site will be included into Google News output? Google News Article needs image: that's the fact. Why it needs it? To show it to the people. What are solutions? ...


3

The mainEntityOfPage property is used to give the URL of a page on which the thing is the main entity. It might become clearer if you look at the inverse property mainEntity: this gives the main entity for a page (see an example). For example, for a web page that contains a single blog post, you could provide one of these: BlogPosting → mainEntityOfPage ...


3

What makes it worthwhile providing metadata? The fact that companies like Google and Microsoft provide this metadata also themselves? Or the fact that these companies make use of the metadata you provide? The Schema.org sponsor’s search engines provide no (Bing, Yahoo, Yandex) to little (Google) metadata using the Schema.org vocabulary, and this might ...


3

Schema.org neither requires nor recommends specific image dimensions. For an ImageObject, you may specify the image’s height and width with the height and width properties. Consumers of the data would have their own rules, if any at all. In case of Google Search tl;dr: For some Rich Snippets that use the image property, no dimensions are specified. For ...


2

In HTML5+Microdata, only the meta element can have the content attribute. (In HTML5+RDFa, every element may have the content attribute.) So if you want to add the string value "in_stock", and it should not be visible on the page, using the meta element is the correct choice: <meta itemprop="availability" content="in_stock" /> You were probably ...


2

This code will do the job, and is errorfree validated: <div itemscope itemtype="http://schema.org/Product" itemref="v1437"> <span itemprop="name">MyProduct</span> </div> <div itemprop="brand" itemscope itemtype="http://schema.org/Brand" id="v1437" itemref="p1437"> <h1 itemprop="name">MyBrand</h1> <link ...


2

There is no need for the >symbol regarding to the Google Structured Data page about Breadcrumbs. Just use a markup as shown in the example: <ol itemscope itemtype="http://schema.org/BreadcrumbList"> <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" ...


2

Use this tags. <a href="http://www.example.com/hd-image.jpg"><img src="http://www.example.com/thumbnail-img"/></a> Most of all ecommerce websites, blogger websites, and wikipedia uses links in images for Image SEO. Here, you display compressed image in img src, so it load images quickly, but when Google spider see that link, then they ...


2

Types and properties for hotels are proposed and will likely be part of the next Schema.org release (2.3). In this proposal, Hotel¹ can have the property starRating¹: An official rating for the lodging business, e.g. from national associations or standards bodies. Use the name property of a PropertyValue for indicating the type of the rating (e.g. ...


2

Follow as in visit? Probably not. In additionalType you specify a URI that represents a type. If a search engine supports this type, it has no need to visit it (because it already knows what it needs to know when seeing the URI). If a search engine doesn’t support this type, it could visit its URI, learn something about it (via RDF), and make use of ...


2

The Schema.org properties articleBody and description expect Text as value. If you want to follow this advice, you have to specify the properties (in itemprop) on an element that creates a string value (these are most elements, e.g., div). So let’s say you use <div itemprop="articleBody"></div>. It’s the textContent of that element that will ...


2

Yes, providing the property multiple times is the correct way to do this in Microdata. If you want to provide data about the telephone number, you could use the contactPoint property with a ContactPoint value for each telephone number. Its contactType property could specify the kind of contact point (e.g., "Office" or "Mobile"). <div itemscope ...


1

If you want, you can use WebPage (or one of its subtypes, like AboutPage) for every page on your site, including the homepage. In addition, you can provide items (using suitable types) for every "entity" you have content about on the page. For example, if every page contains your organization’s name and telephone number, you can (and should) have an ...


1

For the WebSite itemscope, a perfectly viable alternative would be to use JSON-LD format as opposed to Microdata, namely because the scope of a Website would include the <head> element as well. To put that into context, the name item property of the WebPage element is best represented with the <title> element, which lives in the head of the ...


1

If you place the itemscope on the <head> tag, the Microdata item "ends" with the </head> tag. If you want to add properties from the head as well as from the body, you have three options: specify the itemscope on the html element specify the itemscope only on one of these and use the itemref attribute to reference properties from the other ...


1

You can provide Schema.org properties multiple times. So each Service can have multiple areaServed values: <div itemscope itemtype="http://schema.org/Service"> <ul> <li itemprop="areaServed">…</li> <li itemprop="areaServed">…</li> <li itemprop="areaServed">…</li> </ul> </div>


1

Not at all. The HTML content data is not hidden. Only its semantic descriptors. The same descriptor types and information that would equally be hidden from the viewer as attributes of the HTML elements in the microdata form. They're just in a different form as JSON-LD.


1

Yes, provide multiple author properties. But note that the itemprop has to be specified on the element with the itemscope. <div itemscope itemtype="http://schema.org/Book"> <span itemprop="author" itemscope itemtype="http://schema.org/Person"></span> <span itemprop="author" itemscope ...


1

I think the first variant (ExerciseAction → event → SportsEvent) makes more sense, but only because the definition of potentialAction seems to suggest that it’s for, well, potential actions, i.e., actions that could possibly happen at this event (e.g., things you can do), and not for actions that actually happened. For explicitly denoting that this action ...


1

your code contains error, thats why two authors aren't recognized. If you have more then one author, you should add them as list without entity duplication. Here the correct code: <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "WebPage", "mainEntity": { "@type": "Book", "author": [{ ...


1

The website http://schema.org/ is the relevant and the only canonical source for Schema.org types and properties. Type vs. property. A type represents a thing, a property is for providing information about that thing. The name of a type always starts with an uppercase letter (e.g., Person), the name of a property always starts with a lowercase letter (e.g., ...


1

It's actually pretty straightforward - the breadcrumbs error is because you marked up the last (current) element as breadcrumb. However the requirement is to be link also, as the previous breadcrumbs. You have two options: 1). Add the url property to the last element too. It will be link to the article itself, will pass the validator (recommended): instead ...


1

(Leaving aside consumer support.) The vocabulary Schema.org offers two ways to provide breadcrumbs for a WebPage (and its sub-types): breadcrumb property with a text value breadcrumb property with a BreadcrumbList value Using text is easy, but unstructured (harder to parse for consumers). Using BreadcrumbList is more complex, but allows to specify ...


1

About your HTML: You can (and should) use semantic markup, of course. So, for example, the product container should probably be an article instead of a div, and the "Product Name" should probably be an h1 instead of span. Like Martin Hepp writes also, you have to use link instead of meta if the value is a URI. About your Schema.org: The price property ...


1

Traditional hotel star ratings are not based on reviews and would not be appropriate to use the aggregateRating. Instead the stars are an award and if you wish to represent them in schema.org you should do it like this: Rated <span itemprop="award">★★★★☆</span> by the Hotelstars Union.


1

itemref does not work like that. You have to add the itemref attribute to the element you want to apply a property to, and this property has to be defined on an element with the matching ID. So your example should be: <div itemscope itemtype="http://schema.org/Product" itemref="v1437"> </div> <h1 itemprop="brand" itemscope ...


1

As you said there is an open issue on schema.org for this, so you may be better attempting your own solutions and using trial-and-error to see if google picks it up correct. I would use solution 2. because it gives closed hours and seems clearest, this sounded similar to the suggested solution from the schema.org thread ...


1

the testing tool is clear with error descriptions: you haven't applied required properties. If you add location as Type PostalAddress, so you MUST add address and (stadion)name. Location by its own should have its own name too, not only as postalAddress. And avoid usage of relative urls like urls - they could be not correctly recognized. Update: following ...


1

You can use Microdata (as you do in your example) as well. Just add the necessary properties and missing data (with a meta tag) for example like this: <div itemscope itemtype='http://schema.org/LocalBusiness'> <p><strong>Contact Us:</strong></p> <p itemprop='contactPoint' itemscope ...



Only top voted, non community-wiki answers of a minimum length are eligible