Tag Info

Hot answers tagged

7

Both are solutions for semantically annotating your content, but in very different ways: Microdata extends HTML5 (e.g., by introducing new attributes like itemprop), while Microformats only uses existing HTML mechanisms (like class and rel attributes). With Microdata, you can use almost any vocabulary (a popular one is Schema.org), with Microformats you ...


5

Tool from Yandex The "Structured data validator" supports JSON-LD. Alexander Shubin (working for Yandex) wrote: Pls, take into account that in order to check JSON-LD you need to put it in tag (since this is how it should be embedded into html). E.g., <script type="application/ld+json">{ "@context":"http://schema.org", "@type" : ...


4

Typically, user agents wouldn’t dereference these URIs. There should be absolutely no problem in using the Schema.org HTTP URIs on a HTTPS site. In fact, many other vocabularies (used for Microdata or RDFa) provide only HTTP URIs, so you have no choice there. I’d even say it’s bad practice to provide multiple vocabulary URIs for the same concept, as ...


3

Open Graph markup is completely different from Schema.org markup usually displayed in individual meta tags in the site's header, like so: <meta property="og:type" content="website" /> Schema.org markup is used inline with the content and is used to mark up, or describe the content itself. Open Graph and Schema.org are two different things and have ...


3

Microdata (Note) can only be used on HTML elements as defined by HTML5. According to HTML5 (CR), the svg element is not in the HTML namespace. WHATWG’s HTML spec explicitly mentions that Microdata doesn’t work for svg (quoted on 2014-01-02): Currently, the itemscope, itemprop, and other microdata attributes are only defined for HTML elements. This means ...


3

Sadly, schema.org doesn't have every type of place, person or object on the planet. At this current time you only have 2 options, which are: <div itemscope itemtype="http://schema.org/Place"> <div itemscope itemtype="http://schema.org/City"> Either are valid because a village, town and city is a place. City is more specific, which is also a ...


3

If the code is validated, no. The following is: <div itemscope itemtype="http://data-vocabulary.org/Breadcrumb"> <a href="http://www.example.com/" itemprop="url"> <span itemprop="title">Dresses</span> </a> </div> Gets validated with any of those tags (<span>, <li>, <div>) and many ...


3

They're using microformats, specifically hCard and hCalendar. Along with RDFa and JSON-LD, this is an alternative to microdata. See Google's Rich Snippet spec for people here, and here's my public LinkedIn page viewed with Google's structured data testing tool, showing a preview Rich Snippet and the extracted structured data.


3

Google won't pick up on any markup that isn't visible to users. Because of this policy, they are unlikely to recognize any structured data that is in <script> tags. In general, Google won't display any content in rich snippets that is not visible to human user. Don't hide the content that you have marked up for rich snippets using techniques like ...


3

If the website is a organization or local business then you should opt to use either: organization or local business combined with things like products and services. Many online businesses use lcoal markup in the footer and company name at the top meaning that schema is repeated on every page, then in the content area you use products or services which ...


3

Here is how it works based on sites we have released recently + a couple that have ran awhile. Assuming its a new site using all out Schema.org as well as fallback data-vocab for crumbs and reviews datas, you should expect at least a 3 month lag time. You will see the Google webmaster tools schema reports doing nothing -- no new reviews, no new ...


3

You could use Product, but I guess you’d only use its name and description properties. So why not use Offer directly? You can specify name, description, category, and price.


2

Being strict while keeping things simple, and without mixing vocabularies, you can use the image property, which is generic but specific enough about the content you are marking up. A logo is not normally associated with a person, it's associated with a product, a company, or things like that. So for practical purposes, the image she uses is going to define ...


2

Well, you are attempting to claim that an Article is also a Person, which doesn't make sense semantically. If you are trying to claim that Person is an author of Article, there is an 'author' property of Article to do this. The additonaltype property is only useful when you are dealing with 'nested' types -- in other words, the properties you specify are ...


2

Yes, you could/should add the markup on any page where relevant content can be marked up. However, you should not add several items for the same thing on the same page, unless something like Microdata’s itemid can be used to specify that the items are actually about the same thing. You might use the itemref attribute if you have relevant data about the same ...


2

Your questions seem to be: Can I specify itemprop="url" on li? Can I specify itemprop="name" on a? The answer to both of these questions is: No, you should not do that. Microdata defines special parsing rules for elements like a. Schema.org’s url property expects a URL as value. Microdata defines that you have to use a, area or link for specifying ...


2

Disclaimer, I've never used share price, but I use Organization, Place, & Offer frequently. Based on past usage of exitpoint Offer: I'm not sure it is the best fit. Offer is meant to "sell" as a Organization > (optional POS) > Place > (optional service/product/thing) > (optional reviewed entity) > Offer, whereas stock price is more like a "organization ...


2

Every classified ad could be an Offer. The seller property can refer to the Organization/Person offering something. The itemOffered property can refer to the actual Product (e.g., a car) that gets offered. etc.


2

I am not sure what all you need so it will be hard to speak to your particular needs. But this is what I think is going on and the solution is really really simple. Each entity/data pair belongs to a type within the schema. You cannot mix them. But you can use any or all of them any time any way you want. Here is what I mean. For Articles, they live within ...


2

You can use a <meta> element with itemprops for content which doesn't appear in a format you could otherwise mark up. This is described by Schema.org as "missing and implicit information". I'm not aware of any reason why you can't apply this principle to any data you wish to describe with microdata, though if your HTML is well structured applying it ...


2

There are different standards for microdata. The word microdata just means that data has been embedded in the page. When you start using microdata you must reference which standard you are using with the itemtype attribute. For example; <div itemtype="http://schema.org/WebPage"> This itemtype property defines the microdata format for all the ...


2

Yes, you can use every HTML5 element for Microdata … Microdata defines 5 new attributes for HTML5: itemid itemprop itemref itemscope itemtype Let’s see where they can be used. Section 5.2 says: Every HTML element may have an itemscope attribute specified. So every element can have itemscope. Further on it says: Elements with an itemscope ...


2

As far as I am aware, they do not directly influence your SERP position. However, they do increase CTR (click-through-rate) on search results. A lot of webmasters work hard at getting themselves into the top five results for a specific keyword without ever giving much thought to CTR. This is a bit wasteful, in my opinion, considering our sole reason for ...


2

I'm not sure when this issue started for you, but my Merchant Center Account was throwing the same error for Limited Availability items also. It turns out that Google's updated their feed specification (see here) and are removing LimitedAvailability as an allowed value. I updated those items to be In Stock, and the warnings disappeared. Another valid ...


2

[Updated: I suggest nesting types/elements when mark-up appears to require it. The reason is simple. You never know how the data will be used and where nesting is appropriate, nesting will give a clearer picture of the data you are marking-up. Nesting does not always seem possible when you try and stitch mark-up into your HTML. It can be a real struggle ...


2

The Schema markup for a product should be like:- <div itemscope itemtype="http://schema.org/Product"> <a itemprop="url" href="http://www.example.com/product"> <div itemprop="name"><strong>Product Name</strong></div> </a> <div itemprop="description">This is my product ...


2

You should use Comment instead of UserComments. UserComments is for the action/event of commenting, while Comment represents the published comment itself. (You’ll often find that UserComments is used although it’s not appropriate; that is because Comment was introduced later.) Neither Schema.org nor Microdata define which conclusions can be drawn when a ...


2

Google’s documentation of their Rich Snippet Aggregate Review still uses the Data-vocabulary.org vocabulary, but I think it’s safe to assume that this also applies to the Schema.org vocabulary. There it says about count (which would probably be reviewCount in Schema.org): Note: Whenever you include count, the page must also contain review markup for ...


2

Yes, your use of Microdata and schema.org is correct. Instead of div, you might want consider using the sectioning element aside: The element can be used for […] advertising, […] That way the advertisement is separate from the main content flow of your document. Oh, and don’t forget to provide an alt attribute for the image. Depending on the ad, you ...


2

Your plan of using meta data for microdata is not viable. Here is Google's FAQ about why it isn't showing your data in the search results: Is your marked-up content hidden from users? In general, Google won't display any content in rich snippets that is not visible to human user. Don't hide the content that you have marked up for rich snippets ...



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