Where does Schema.org Microdata go on a page?

[RScime25]

Say you've got a Magento e-commerce site and you want to add Schema.org Microdata to it to take advantage of Google's Rich Snippets feature.

Would the markup be part of the page's HTML TITLE . . . or somewhere in the bare-bones description (usually wrought by inputting data into separate fields in the CMS), e.g.,

Item: Something
Price: $00.00
Short Description: blah, blah, blah

Or, hidden somewhere in the header?

Or, can it be marked-up somewhere beneath my lengthy (and Panda-friendly) content and subsequently extracted by Google and highlighted in the SERPs?

Admittedly, I'm more than a bit late to the Schema.org party and I'm a content-guy anyway; and not much good at under-the-hood stuff. I figure I'd better get my chops together, now.

I've searched Moz.com's Q&A as well as Google's and Schema.org's and haven't come up with an answer yet that doesn't require that I learn a whole new vocabulary.

[ChristopherGlaeser]

The markup is used to identify what the content is.  When a human sees

2003 Boxster, Red with Black convertible top, 26,000 miles, $14,000

we know someone is trying to sell something and we know what the item is, the description, and price, but search engines may or may not know this is a product for sale or is a review of a product or something else.  The schema.org allows you to tell search engines this is indeed a product for sale and here are the attributes of that product including item name, price, etc.

So, in answer to your question, the markup goes in the body of the page and marks up the content.

Best,
Christopher

[RScime25]

Thank you. I'll give it a try.

[LesleyPaone]

I do not work on Magento, I work with Prestashop, but I think you might come across the same problem I did with my clients. Google does not specifically say you cannot pass a product amount with a currency sign, but I have found they will not accept the "offer" if the price has a currency sign. We had to develop a regex function in smarty to break the currency sign off of out products prices and they were all accepted after that.

[RScime25]

Perhaps I worded my question poorly.

When I've tested Schema.org, it returns a result that looks something along the lines of:

Item: widget
Price: $00.00
**Short Description: **blah, blah, blah, blah, blah, blah, blah, blah, blah

But, what if my on-page content reads:"The **widget **comes in blue, green or yellow, and costs $00.00. It blows away the competition and could easily be described as blah, blah, blah, **blah, blah, blah, **blah, blah, blah."

In other words, the page's content is written in a narrative form, and I'd rather not have that narrative broken up with a block showing just the Item, Price, and Description—but, I'd still like to have the benefits of rich snippets.

Did that make more sense?

[ChristopherGlaeser]

Yes, your question makes sense.

You can put the schema.org properties in any order, but spitting the description like that is going to be problematic.  I would also suggest that your example is tedious to read and lacks a product description heading.  A more realistic example would be:

h1 Widget /h1
The widget comes in blue, green, ...

Hiding the price in the middle of the description is also difficult for humans to read.  Putting aside the schema syntax, the example IMO is a poor user experience.