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 ...


4

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 ...


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 ...


4

I guess there is no reason to assume that Google wouldn’t handle SVGs as value of the image property: Schema.org’s image property expects an image URL (or an ImageObject). SVG is an image format (image/svg+xml). Google does index SVG images. (Of course, we can never be sure; and things might change always.) Generally, the syntax shouldn’t matter, as ...


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

It validates as a list of product entities, but the "official" Google doc says: Product markup on listing or category pages is not supported. This doesn't mean that it won't work though. As we know what Google says is not what Google does. It doesn't hurt to have the multi-product markup in there regardless. It's not like they will de-rank your site ...


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

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

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

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

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

[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

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

How to debug markup implementation errors and Fix it: To investigate an issue with a specific content type, click on it and it will show you the markup errors found for that type. You can see all of them at once, or filter by error type using the tabs at the top. Check to see if the markup meets the implementation guidelines for each content type. Click on ...


2

This issue is rather common and found in mostly poorly edited or made WordPress themes. entry-title, updated and author are all related to the Hatom markup which requires hentry to included above the fold and ideally in the body. It's likely that your website is missing author, updated and entry-title leaving hentry still within your code. View source and ...


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

If you want to use the Schema.org vocabulary, you could use two WebPage sub-types: ItemPage for a product. A page devoted to a single item, such as a particular product or hotel. CollectionPage for a tag/category page.


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 ...


2

I cant comment on whether this would work for all situations, but we use Schema.org in the manner you describe -- as meta "content" on the product pages. Why? It's just so much more portable and doesn't wreck up themes. It also allows more granular control on formatting the data, and it gets relevant data just after <body> (far above the fold). ...


2

Don’t use protocol-relative Schema.org URIs: I wouldn’t expect all Microdata consumers to handle these URIs correctly (while it’s common for links or embedded resources, values of the itemtype attribute typically don’t get dereferenced). They fail when a different protocol than HTTP/HTTPS is used (for example, file). It’s not just that the link is broken ...


2

1.) I stand corrected on the particular problem i stated before being an ISO time/format issue. I think its because the Schemas are being mixed together. After some removal of misc stuff from source code to make this smaller OP source code is as follows: <div itemtype="http://data-vocabulary.org/Recipe" itemscope="" class="pd_main_wrapper"> ...


2

Perhaps http://schema.org/ItemList would be a better fit. But I'm not sure how it will actually help search engine to parse a menu in a better way.


2

The mainContentOfPage property expects a WebPageElement as value, but you are using Blog (which is not a child of WebPageElement). You seem to use it like a property to denote the "main entity" of a page, but this is not appropriate. A property for that is currently under discussion. Side note: It is not appropriate to use the url property for each ...


2

You are missing some closing </div> tags. If I correctly interpret your intentions, it should look like this: <div itemscope itemtype="http://schema.org/SocialEvent"> <a itemprop="url" href="www.convention-name.org"><div itemprop="name"><strong>Bob's Convention</strong></div></a> <div ...


2

Note that syntaxes like Microdata and RDFa don’t annotate the HTML, they use the HTML just as a carrier. After parsing the Microdata/RDFa, it doesn’t matter anymore which markup was used. If your two properties with the same content belong to the same item, it’s not useful to have the additional one, as it doesn’t add anything new (but it’s not forbidden ...



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