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


7

These are no resources which get usually accessed by the browser but simply a fancy way to declare a name space, i.e. all SVG images share the same XML name space which is defined by the URL and same with xlink. This means you should treat any of these xmlns just as some kind of special string and leave them unchanged.


5

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


4

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


3

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


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

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


3

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


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.


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


2

You can simply refer to Your logo via meta/link tag as suggested in official documentation: http://schema.org/docs/gs.html#advanced_missing <!-- schema.org item wrapper --> <div itemscope itemtype="http://schema.org/Organization"> <!-- This is Your original SVG markup --> <svg id="my-logo" height="60" width="60" ...


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

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

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

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

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

There are usually two "levels" of your web page that can be marked up with Schema.org (note that I made these levels up for this answer; the difference is not always useful): level 1: the web page itself (i.e., the transport medium) level 2: the content/entities contained in the web page Obviously, every web page can be marked up with WebPage (or one of ...


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

Yes and often you need to do this to activate widgets. Schema.org has shoddy support for things like review-aggregate and doesnt support breadcrumbs (weird eh?). Reviews especially, it fails validators until you use a mix of Schema and Data-Vocabulary. Here are some random examples: This Schema does not work for Product review summary: <div itemscope ...


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

JSON-LD doesn’t care. Which makes sense, because the data is the same, no matter from where in the document it gets extracted. From the perspective of HTML, you should only include it in the head if the JSON-LD is about your web page or about what your web page represents, because the head element is defined to contain metadata for the document. But it’s ...


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

Your use of additionalType in the first snippet is correct. An example where additionalType is used can be seen on Schema.org’s IndividualProduct: <script type="application/ld+json"> { "@context": "http://schema.org", "@id": "#product", "@type": "IndividualProduct", "additionalType": "http://www.productontology.org/id/Racing_bicycle", ...


2

I’m assuming you are using the vocabulary Schema.org and have something like this: <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "LocalBusiness", "url": "http://example.com/" } </script> Here the url property belongs to the LocalBusiness item. So it should give the URI of the local business, no matter on ...


2

No, your example would mean that it’s an schema:Article and a pto:Dog_breed. To state what the schema:Article is about, you could use its about property. The elaborate version would be: <article itemscope itemtype="http://schema.org/Article"> <div itemprop="about" itemscope itemtype="http://schema.org/Intangible"> <link ...


1

Google says that they can read dynamically added structured data if the JSON-LD syntax is used: Also, Google can read JSON-LD data even when it is dynamically injected into the page's contents, such as by Javascript code or embedded "widgets". They don’t document this for the other syntaxes they support (Microdata, RDFa), but this doesn’t necessarily ...


1

You will only see Googles maps. The SERPS get address and map data from Google Places, which has been merged into Google+ pages for business. Using a Google verified place on a verified domain in GWT, with a rel publisher keystone: you will see map, but only from Google. So even if you define a new or non-google map using schema, it will still use the ...



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