I have tried to mark up the kind of information you'd offer when you're selling a premium wine, here's what it looks like: http://www.google.com/webmasters/tools/richsnippets?url=dekoninck.co.uk%2Fwine.html.
The Rich Snippets Tools is showing "Warning: Incomplete microdata with schema.org., and I can't work out what's missing.
Also, I'd love recommendations on
the best way to mark up grape variety; currently done via additionalType
the best way to mark up region; currently done via additionalType
the best way to mark up producer; currently done via manufacturer which feels clunky
the best way to specify vintage; currently done via releaseDate which feels clunky
the best way to specify offering storage for wine; currently done via businessFunction http://purl.org/goodrelations/v1#Maintain
how I can specify VAT/tax in pricing, for storage, wine price and delivery price.
I've worked out what the warning means. It appears that the rich snippets testing tool no longer accepts Offer to be nested within Product.
Before I had
<div itemscope itemtype="http://schema.org/Product">
... details
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer">
... details
</div>
</div>
The fix (at least to make the warning disappear) is to move Product outside of Product:
<div itemscope itemtype="http://schema.org/Product">
... details
</div>
<div itemscope itemtype="http://schema.org/Offer">
... details
</div>
Does this look right?
Related
My client is a retail store with an online boutique on Magento. I'm implementing Schema.org in Microdata.
The problem comes from the fact that his prices are different depending on the closest city from the user. What "offer" elements do I use in order to set things straight with machines?
My fear is that Google could show the wrong price in the SERP. I don't want to deceive users!
A single Product can have multiple Offer items (via the offers property), exactly for such a purpose.
In the Offer item, you use properties that describe in which situation (for whom, when, etc.) the offer is valid. For location-based offers, the eligibleRegion property can be used:
[…] the geo-political region(s) for which the offer […] is valid.
(With the ineligibleRegion property you can list for which location the offer is not valid.)
So in Microdata it could look like this:
<article itemscope itemtype="http://schema.org/Product">
<h1 itemprop="name">Product 1</h1>
<section itemprop="offers" itemscope itemtype="http://schema.org/Offer">
<h2>Offer 1</h2>
<div itemprop="eligibleRegion" itemscope itemtype="http://schema.org/City">…</div>
</section>
<section itemprop="offers" itemscope itemtype="http://schema.org/Offer">
<h2>Offer 2</h2>
<div itemprop="eligibleRegion" itemscope itemtype="http://schema.org/City">…</div>
</section>
</article>
The documentation for Google’s Product Rich Snippet doesn’t mention a case where a Product has multiple Offer items (except for the different case of AggregateOffer), so it’s unclear if a Rich Snippet can be displayed in such a case.
We have embedded rich snippets for a rental objects rating website. Here an example:
http://www.google.de/webmasters/tools/richsnippets?q=http%3A%2F%2Fwww.sonnenquartiere.de%2Fferienwohnungen%2F4-wohnung-8-boardinghaus-norderney-2-zimmer-apartment.html
Works fine when listed in Google search results.
Now we want to aggregate all ratings and post them on the homepage so the homepage itself gets a rating in the Google search results. We did it some time ago:
http://www.google.de/webmasters/tools/richsnippets?q=www.sonnenquartiere.de
We did that some time ago, but the result in the Google Search is still not being displayed with the aggregated rating. Here an Example:
https://www.google.de/search?q=Boardinghaus+Norderney (2nd place here)
Is there something we can do to get this working?
One thing that I did notice about your markup is that you are using the schema.org/WebPage markup for your aggregate review rating. So search engines are seeing that schema as a rating for your home page. You should be using the aggregate rating schema with a schema that better describes your type of business, perhaps something in the schema.org/LodgingBusiness category.
I hope this is not too late and that I will be able to help.
Following the standard procedure is the best practice in such thing. Make sure you use the correct markup. So for review use the reviews-schema as the example below:
Use this tool to generate the code and then modify your website according to this working sample
http://www.microdatagenerator.com/reviews-schema/
For example:
<div itemscope itemtype="http://schema.org/Review">
<div itemprop="itemReviewed" itemscope temtype="http://schema.org/Thing"><span itemprop="name">home mortgage</span> </div>
<div itemprop="author" itemscope itemtype="http://schema.org/Person">
<span itemprop="name"> Nick M.</span>
</div><meta itemprop="datePublished" content = "01/01/2016">
<div itemprop="reviewRating" itemscope itemtype="http://schema.org/Rating"
<meta itemprop="worstRating" content = "1"/><span itemprop="ratingValue">5</span>/<span itemprop="bestRating">5</span> stars </div>
<span itemprop="description">My experience with ABC Company was very good and I recommend it to everyone. </span>
</div>
you take that code and take the parts you need to your webpage.
This video was great:
https://www.youtube.com/watch?v=N2PjWtybDOs
Im trying to get this rich snipnet going, so far no errors but no image shown:
<div itemscope itemtype="http://schema.org/Product" style="display: none;">
<span itemprop="name">Canon EOS 5D (prove)</span>
<span itemprop="description"><p>Canon's press material for the <strong>EOS 5D</strong> states that it 'defines (a) new D-SLR category', while we're not typically too concerned with marketing talk this particular statement is clearly pretty accurate. The EOS 5D is unlike any previous digital SLR in that it combines a full-frame (35 mm sized) high resolution sensor (12.8 megapixels) with a relatively compact body (slightly larger than the <strong>EOS 20D</strong>, although in your hand it feels noticeably 'chunkier').</p>
</span>
<img itemprop="image" src="http://wonna.it/image/cache/data/demo/canon_eos_5d_2-74x74.jpg"/>
<div itemprop="aggregateRating" itemscope itemtype="http://schema.org/AggregateRating">
<span itemprop="ratingValue">3</span>
<span itemprop="reviewCount">3 recensioni</span>,
</div>
</div>
This is how I check there is no image: http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwonna.it%2Fcamera-eos-canon&html=
I think you're getting things mixed up.
Microdata is designed to describe your website so software can interpret your page and have a much better understanding of what you are publishing to the world.
This standard is not designed about how you look on Google!
Google also uses this standard (and many more techniques) to decide how they want to represent your site in their results.
Because you start to describe a product with an image won't force them to display it in their result.
Nesting an Offer that has a priceSpecification inside a Product throws up an Incomplete microdata warning in Google Rich Snippets testing tool.
This
<div itemscope itemtype="http://schema.org/Product">
<h1 itemprop="name">1984 Vintage Selection Cabernet Sauvignon</h1>
<p itemprop="description">Cabernet Sauvignon.</p>
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer">
<p itemprop="priceSpecification" itemscope itemtype="http://schema.org/priceSpecification">Prices start at
<meta itemprop="priceCurrency" content="GBP" />£<span itemprop="price">0.71</span> (per bottle)</p>
<meta itemprop="validThrough" content="2013-09-01" />
</div>
</div>
throws the following warning in google rich snippets testing tool:
Warning: Incomplete microdata with schema.org.
If I move Offer outside Product:
<div itemscope itemtype="http://schema.org/Product">
<h1 itemprop="name">1984 Vintage Selection Cabernet Sauvignon</h1>
<p itemprop="description">Cabernet Sauvignon.</p>
</div>
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer">
<p itemprop="priceSpecification" itemscope itemtype="http://schema.org/priceSpecification">Prices start at
<meta itemprop="priceCurrency" content="GBP" />£<span itemprop="price">0.71</span> (per bottle)</p>
<meta itemprop="validThrough" content="2013-09-01" />
</div>
then the warning is no longer thrown up, but this doesn't appear to make sense, as the Offer is not linked to the Product it's applicable to.
All the examples at schema.org nest Offer within Product, however, none of them use priceSpecification. I could only find one blog post where Offer is not nested within Product: http://seolobster.de/richsnippets-schema-org-products-update. This does not fill me with confidence to use in a live environment.
Which is correct? Especially if you throw in more than one Offer?
I have the same problem and I just figured it out though painstaking trial-and-error: The problem is that, even though price is part of the priceSpecification schema, it still needs to be defined outside the priceSpecification metatag in the regular offer, too!
I needed priceSpecification because we show prices including and excluding VAT, and now I have no frickin' idea on how to implement this! If I HAVE to define the price in offer, how do I tell it it's with or without VAT? valueAddedTaxIncluded is not part of the offer schema! An empty div just including valueAddedTaxIncluded=true? Okay, so how do I implement the other price without the VAT then? That would define the price twice in the offer, and that's not possible!
Also, why is schema.org and getschema.org so damn effing useless when it comes to samplecode and how to properly implement any given schema? If you want people to adopt some fancy new technology - TELL THEM HOW TO DO IT!!
Based on your example I don't think you need to use a separate priceSpecification property. Instead you can directly add the price and priceCurrency property to the Offer like the example below.
<div itemscope itemtype="http://schema.org/Product">
<h1 itemprop="name">1984 Vintage Selection Cabernet Sauvignon</h1>
<p itemprop="description">Cabernet Sauvignon.</p>
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer">
Prices start at <meta itemprop="priceCurrency" content="GBP" />£
<span itemprop="price">0.71</span> (per bottle)
</div>
</div>
As stated before, the offer also needs the price-tag. One solution that the tag-tester allows is adding the data as a meta-tag like this:
<meta itemprop="price" content="79" />
I'm not sure if google will parse and show this however.
I have a "Review-aggregate" microdata snippet in my site, and google has cached it, but it is not appearing in the google search results with the rating stars.
The URL that has the microdata in is:
http://www.rnsalert.com/
And here is the snippet:
<div class="ui-corner-bottom" id="micro-data-reviews" itemscope="" itemtype="http://data-vocabulary.org/Review-aggregate">
<span itemprop="itemreviewed">RNSalert</span> is rated
<span itemprop="rating" itemscope="" itemtype="http://data-vocabulary.org/Rating">
<span itemprop="average">9.0</span>
out of <span itemprop="best">10</span>
</span>
based on <span itemprop="votes">16</span> independent ratings.
</div>
Using Google's structured data test tool, it shows that the microdata is being parsed correctly...
http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwww.rnsalert.com%2F&html=
Yet the google search results aren't showing it. The page has been cached.
Search google for "RNS alert" and you will get the page listed as the first organic result.
Any thoughts?
Many thanks,
Dan
Google should recognise all types defined in schema.org, but it supports rich snippets in the search results for these content types only:
Reviews
People
Products
Businesses and organizations
Recipes
Events
Music
Source:
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=99170&topic=1088472&ctx=topic
Also, it may take a while before you're able to see them in the search results - maybe even days.
I'm 95% sure that for your rating/review stars to appear in Google's web results you must also setup Google authorship with the site/page.
6+ months ago this step wasn't required.
Your page contains microdata for a review aggregate, but it is not related to a product or item.
Check the examples here https://schema.org/AggregateRating
The aggregate needs to be within the scope of another item:
<div itemscope itemtype="http://schema.org/Restaurant">
<span itemprop="name">GreatFood</span>
<div itemprop="aggregateRating" itemscope itemtype="http://schema.org/AggregateRating">
<span itemprop="ratingValue">4</span> stars -
based on <span itemprop="reviewCount">250</span> reviews
</div>
<div itemprop="address" itemscope itemtype="http://schema.org/PostalAddress">
<span itemprop="streetAddress">1901 Lemur Ave</span>
<span itemprop="addressLocality">Sunnyvale</span>,
<span itemprop="addressRegion">CA</span> <span itemprop="postalCode">94086</span>
</div>
<span itemprop="telephone">(408) 714-1489</span>
<a itemprop="url" href="http://www.dishdash.com">www.greatfood.com</a>
Hours:
<meta itemprop="openingHours" content="Mo-Sa 11:00-14:30">Mon-Sat 11am - 2:30pm
<meta itemprop="openingHours" content="Mo-Th 17:00-21:30">Mon-Thu 5pm - 9:30pm
<meta itemprop="openingHours" content="Fr-Sa 17:00-22:00">Fri-Sat 5pm - 10:00pm
Categories:
<span itemprop="servesCuisine">
Middle Eastern
</span>,
<span itemprop="servesCuisine">
Mediterranean
</span>
Price Range: <span itemprop="priceRange">$$</span>
Takes Reservations: Yes
</div>
Unfortunately, just because you put something on your site doesn't mean that Google has to show it in their search results.
I would assume that they need to have a certain amount of trust in your site before anything will show. If not then everyone would just mark their own products/posts with 5 stars so it looks good in a search listing page.
In my experience, it is a lot easier to get rating stars in listings when your site contains votes for other people's products rater than your own.
Google help:
The search preview is approximate.
Real Google Search results for your data might look different.
The search preview is illustrative.
We do not guarantee that the content you preview will be displayed in Search results. Your content will likely appear in Search results for relevant queries, but that content must first pass through our systems to be appropriately indexed and ranked before it appears in actual Search results. We reserve the right to filter out any results at our discretion if it violates our quality guidelines. Finally, any preview tool URL for your content is only valid for a limited duration (e.g. weeks).