Hot answers tagged microdata
12
The three big search engines, Google, Bing and Yahoo (and more recently, Yandex), have agreed to understand 1 single microdata vocabulary. This is Schema.org, which has examples of placement.
This formats your results as Rich Snippets, the search engine results which have pictures and fivestar ratings, etc, displayed on the search result page. While this ...
4
I believe you are looking for schema.rdfs.org - pertinent links:
RDF/XML
JSON
CSV
4
If there is a microformat for the data you have on your website and you wish to optimize your website for the search engines then you should use use microformats in your websites. How much of a difference it will make in your SEO efforts will vary just like every other thing that has to do with SEO. It will depend on lots of other factors. But if you want to ...
4
Google recommends using microdata, but it does support three formats: microdata, microformats, and RDFa. A big reason to choose microdata would be that the examples that Google gives on it's website and those on schema.org are in the microdata format.
Here is a site that has a huge table of the various advantages and disadvantages of the three formats. ...
4
You should use
<meta itemprop="image" content="/uploads/images/medium/product_img.jpg">
Since src="" is associated with embedding content on the page and content="" is associated with embedding items off the page so to speak. This is the same method as used with the Facebook Open Graph meta as well, take a look:
<meta property='og:image' ...
3
Your rich snippet data needs to be visible to users. From Google's rich snippet troubleshooting:
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. It can be tempting to add all the content relevant for a rich snippet in one place on the page, mark it up, and ...
3
Source: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1211158
Google currently supports rich snippets for people, events, reviews,
products, recipes, and breadcrumb navigation.
So, no address information will be shown in SERP. However, Google may change it's algorithms some time later, like showing pin icon or anything else. And ...
3
There are two properties:
significantLink - URL - One of the more significant URLs on the
page. Typically, these are the non-navigation links that are clicked
on the most.
significantLinks - URL - The most significant URLs on the page.
Typically, these are the non-navigation links that are clicked on the
most (legacy spelling; see singular form, ...
3
As of right now, schema.org microformats are primarily used to display purposes in search results. So far there has not been any indication that they affect search results in any significant way. Plus with that particular format being easy to abuse i would suspect it would have no effect on rankings. I would speculate it will serve other purposes somehow ...
3
No, you don't need to duplicate the HTML exactly: microdata schemas are based on the microdata attributes. It doesn't matter (usually; e.g. links are an exception) what HTML tag those attributes are applied to.
You may want to start by reading "Getting started with schema.org", if you haven't already.
3
Honestly, I have a feeling it is about as elusive as getting Google Sitelinks. My recommendation is to follow the Google guide for Rich Snippits and when the site gets enough PageRank and keywords hits, it will naturally start appearing.
Also be sure to watch your webmaster tools closely and address any issues Google finds. There is also a section called ...
2
Ok, first of all you are not using the microformat suggested by www.schema.org. If you would, your markup code would look like this:
<span itemprop="reviews" itemscope itemtype="http://schema.org/Review" style="display:none;">
<div itemprop="reviewRating" itemscope itemtype="http://schema.org/Rating">
<meta itemprop="worstRating" ...
2
Unfortunately none of those formats are suitable for what you do. What you're offering is a service and although each of the rich snippets formats support Products, services are really quite different things.
There's some discussion of the need for something on services on the Microformats wiki
There is a need for a specific microformat dedicated to ...
2
The basic direction is correct, but you must use <link> and href=... instead of meta, since the value is a URL/URI, not a string:
<link itemprop="acceptedPaymentMethod" href="http://purl.org/goodrelations/v1#PayPal" />
<link itemprop="acceptedPaymentMethod" href=" http://purl.org/goodrelations/v1#PaymentMethodCreditCard" />
The rest ...
2
Using on page SEO for local results can still appear in the main searches nationally if your page is strong enough. So using SEO for local purposes should not effect your national rankings at all unless you are using lots of on page SEO such as Page Dilution.
Page Dilution
Page Title: The Name of the Product | Bournemouth for Example
Meta ...
2
The type of tag can be either div or span without changing how micro-data is extracted. Here is a site giving examples with itemprop on a span tag: http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html
The best way to know for sure that Google will accept your markup, is to test it with the Google Structured Data Tool.
2
Choosing which one is better for you is (IMO) somewhat subjective. Here are a couple factors that may help you to make an informed decision:
RDFa is problematic for non-XHTML web pages (though support appears to be emerging), and has a bit of a learning curve when dealing with nested entities (see the Google example for Address)
Facebook's Open Graph ...
1
There is no schema entry for FAQ, you most likely best of adding it as a 'WebPage'. or using the about. It's not required to use rich snippets for all pages. It holds little SEO weight if any. Google will be able to establish it as a FAQ page without any markup of this type.
1
Micro data has strict rules regarding the tags that you can use, you can open an itemprop with using the p tag and specify the data-vocabulary but nested elements must not be in a p tag.
For example you can use:
<p itemprop="address" itemscope
itemtype="http://data-vocabulary.org/Address">
<span itemprop="street-address">123 Road ...
1
Yes it makes sense. There is even a specific event type for you, the saleEvent. A sale will use many of the fields of the event schema.
startDate
endDate
duration
name (like "Macy's Presidents' Day Sale")
description
image (website logo maybe?)
url
You won't be able to put in the location in the case of online-only sales. Or fields like performers. ...
1
Yes Product uses Schema which Google now recommends as it is supported by Google, Microsoft and Yahoo, while some older formats are not supported by Bing or Yahoo making schema the most ideal choice.
Qoute from Googles PRODUCT Rich Snippets Page
New! schema.org lets you mark up a much wider range of item types on
your pages, using a vocabulary that ...
1
This article from Google describes it well. In short:
Pick a markup format (microdata, microformtats, RDFa).
Mark up your content according, for example using the formats described on http://www.schema.org/.
Test your markup with the structured data testing tool.
For example, if you have a product on your site you need to wrap some custom HTML around it. ...
1
Where possible, amend your website's template files to use microdata. For example, in most implementations, it should be straightforward to add microdata to common elements like titles, images and so on. However, weaving microdata into complex pieces of text, like a biography or a news article, can probably only be done on a page-by-page basis in most cases.
...
1
It'd be perfectly valid to mark up the same content in multiple locations. The point of microdata is that it makes your information understandable to machines (search engines, browsers, applications, what have you), so wherever data occurs on your site that you can mark up with microdata, you should mark it up.
Generally speaking, I would recommend using as ...
1
Breadcrumbs are basically navigation elements. Their purpose is to let the visitor know where they are in the site and give them context. So, having the product name will allow visitors to know where they are.
A link to product name will serve no purpose and will only reload the page the user is already on and is hence, redundant. In general the last part ...
1
There is no "right". However the widely used convention is that a. you should the product name and b. it's not a link.
In the example you give the last page is listed and linked, but above the breadcrumbs, but that's because they are breadcrumbs in search results, not on a page. Search results always have the page title (and a link to the page) as the ...
1
Despite being (as of today) way too short for a subject like this, the Wikipedia article about Microdata (HTML5) still puts the relationship between the three common semantic markup approaches nicely:
Microdata can be viewed as an extension of the existing microformat idea which attempts to address the deficiencies of microformats without the complexity ...
1
Microformats are much simpler to understand and implement, using additional classes on existing HTML elements (or additional span/div elements where necessary).
RDFa on the other hand is more complex and can be difficult to implement, using attributes like xmlns:v and values like v:Person. Like JasonBirch says it's a little problematic for non-XHTML pages ...
1
Yes, you can use the itemprop attribute within an HTML tag even if the immediate enclosing HTML tag brackets, such as <div> and </div>, does not have itemscope and itemtype, as long as some level of enclosing tag brackets does define the item scope and type. The microdata attributes can be used in any type of HTML tags, not just <div> and ...
Only top voted, non community-wiki answers of a minimum length are eligible
