microdata

Validation error: “The itemprop attribute was specified, but the element is not a property of any item”

南楼画角 提交于 2019-12-04 08:56:08
问题 For better SEO I need put some meta on my page like this: <!-- Schema.org markup for Google+ --> <meta itemprop="name" content="The Name or Title Here"> <meta itemprop="description" content="This is the page description"> <meta itemprop="image" content="http://www.example.com/image.jpg"> Here is the source. Then I check this code on Markup Validation Service: <!DOCTYPE html> <html> <head lang="en"> <meta itemprop="name" content="The Name or Title Here"> <meta itemprop="description" content=

Using Microdata with schema.org/OpeningHoursSpecification

被刻印的时光 ゝ 提交于 2019-12-04 06:49:34
I'm looking at http://schema.org/OpeningHoursSpecification Microdata schema for places (and more). I'm a little bit confused on the value to be used for DayOfWeek . Both classes ( OpeningHoursSpecification and DayOfWeek ) are derived from the GoodRelations Vocabulary for E-Commerce and I'm not confident with this vocabulary. Please, can you post a full example? Martin Hepp The enumerations (list of predefined values) of the GoodRelations model remain in the GoodRelations namespace, i.e. for Mondays, use http://purl.org/goodrelations/v1#Monday Here is a full example: <div itemscope itemtype=

Right way to set microdata for Q&A HTML

好久不见. 提交于 2019-12-04 06:37:28
Say one has a simple question and answer HTML and would like to add microdata, how should one proceed? <h2>My Question</h2> <p>My Answer</p> I am aware of the schema.org example, but I don't find it very clear. It looks like overkill. I need a simple solution. Can I proceed this way? <h2 itemscope itemtype="http://schema.org/Question">My Question</h2> <p itemscope itemtype="http://schema.org/Answer">My Answer</p> I just want to tell what the question is and what the answer is. Is this enough for search engines? Or should I have something more sophisticated like: <div itemscope itemtype="http:/

Schema.org setup for multiple events on one page

浪子不回头ぞ 提交于 2019-12-04 04:16:27
问题 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> <

Is it OK to have multiple items of the same Schema.org type on a page?

这一生的挚爱 提交于 2019-12-04 04:07:12
问题 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

How can I manage microdata with xslt?

人盡茶涼 提交于 2019-12-04 00:42:09
问题 I'm trying to add a tag like <div itemscope> in my xslt transformation but I get an error.(The expected token is '=') I'm working in C# .net 4.0 xslt 1.0. 回答1: XSLT is optimized for generating XML output. HTML5 is, in general, not XML. The syntax <div itemscope> is clearly not XML and therefore can't be generated using xsl:attribute . This is because XML doesn't support empty-valued attributes. That's the bad news. The good news: There are two ways of writing the same thing as <div itemscope>

What is the difference between metadata & microdata?

China☆狼群 提交于 2019-12-03 22:06:41
问题 I am quite puzzled with these two terminologies. I know the basic meaning of metadata is "data about the data" . Microdata means the webpages are now more accessible to the search engines . But what separates these two terms? 回答1: Microdata is the name of a specific technology, metadata is a generic term. Metadata is, like you explain, data about data. We’d typically want this metadata to be machine-readable/-understandable, so that search engines and other consumers can make use of it. In

Can I use multiple itemtypes in one itemscope for Schema.org? [duplicate]

主宰稳场 提交于 2019-12-03 12:27:39
This question already has an answer here: Correct way to use multiple itemtypes in Microdata 2 answers I am wondering if I can use multiple itemtypes inside one item scope. For example I have this at the moment: <body id="home" itemscope itemtype="http://schema.org/WebPage"> <div class="wrapper" itemscope itemtype="http://schema.org/ProfessionalService"> <p itemprop from professional service></p> <p itemprop from web page></p> </div> </body> When I do a structured data test within Google's Web developer tools it only picks up items within the professional service schema and every itemprop that

Meta tags itemprop

与世无争的帅哥 提交于 2019-12-03 10:58:26
问题 I am trying to include extracted structured data in my webpages. I included this for description: <meta itemprop="description" content="my description" /> However I realised that there is already a normal meta description on the page: <meta name="description" content="my description" /> Is it ok to leave both of them or it is really necessary to merge them together maybe like: <meta itemprop="description" name="description" content="" /> 回答1: You should leave both of them. The Microdata Spec

What is the relationship between RDF, RDFa, Microformats and Microdata

巧了我就是萌 提交于 2019-12-03 04:52:33
问题 I've done quite a bit of research but I can't understand the exact relationship between the 3. Also, now that W3C has officially recognised RDFa, would you recommend it over Microdata, taking into consideration that it matches Microdata's features and more? 回答1: <sarcasm>I can't imagine what you find so confusing</sarcasm> (edit: these tags were invisible before) Very briefly: Microformats A way to use html pages as both a human readable document and machine readable data , without repetition