I need "per entree" or "per night" written with AggregateOffer or Offer from schema.org.
Google's Structured Data Testing Tool shows an example if you click on "Reviews". Urbanspoon uses the text "per entree" to outline the relation to the price, but they do not work with schema.org. Does anybody know how to handle this with schema.org?
Related
I am creating a website form my enterprise and I wonder how/how many snippets I should use on my homepage.
I know they are separate into multiple categories such as
local business or more generic organization, events, product etc.
I have read this post:
Homepage Rich Snippets
And this one:
Multiple Schema.org Product items & how will it look like in search engine result?
In my case on my homepage (let's say index.html) I want to present my activity, put some links to the services/products I propose, and show incoming events.
Which snippet(s) should I use?
1) Only one such as organization? (my services are not available directly so I suppose it is not a local business category)
2) Or should I put several snippets: organization + event + products
because all three categories are described/present on my homepage?
According to a Google employee, Google Search won’t show Rich Snippets for homepages. But this is not documented, and it might change anytime.
From the perspective of Schema.org, it’s fine to provide as much data as possible. If you have multiple entities on your homepage, you can use multiple Schema.org types to describe them.
If one of these entities can be considered the primary entity (for example, on an organization’s website it would typically be the entity for the organization itself), you can use the mainEntity property for it.
I have a situation where I can put 99% of my structured data into JSON-LD in the of my product pages. But the only way I can get the UPC is to place it inline as microdata.
Will Google aggregate the product data from the JSON-LD and the inline microdata?
Most likely yes.
Google’s Structured Data Testing Tool works fine if you are using JSON-LD and Microdata (and RDFa).
Google does not say otherwise (they did in the past), see their Structured Data Policies:
The data may be embedded in your webpage using any of three supported formats: JSON-LD, RDFa, and microdata.
Some of Google’s structured data features are (currently) only documenting JSON-LD (for example, TV and Movie Watch Actions); for others, Google recommends using RDFa/Microdata, see for example their "About schema.org":
[…] Google recommends the use of JSON-LD for those features. For the remaining Rich Snippets types and breadcrumbs, Google recommends the use of microdata or RDFa.
It wouldn’t make sense for Google to restrict authors so that can’t make use of all the features (using different syntaxes) in the same document.
That said, you can never know for sure (their documentation is not always up-to-date, and their rules might change each day.)
One can use both in same page. But may not divide the info of one type of entity into parts ..example: some info about the product in JSON-LD format and some in microdata format does not work.
Also two separate things would mean two entities. Although one may use #id in JSON-LD and itemid in microdata to specify them as same entity but the Google’s Structured Data Testing Tool still shows them as two entities.
You can combine all three formats in a single page but Google gives more priority to JSON-LD and will take data from JSON-LD format shall the other one (or two) have different values than the former.
I have added structured data to the product pages of my website. Would it also be beneficial to also add the structured data to the category pages? i.e. the pages that show all products within a certain product category group?
My thought is yes, as I'm describing what that page is displaying. The only doubt I have is that I'm only displaying a subset of the information that's on the full product page. E.g. I don't have a itemprop='description' entry on the category page. But I would assume/hope that because I have itemprop="url" for each product on the category page, that the search engines will be smart enough to tie the two together …?
Yes.
It can be beneficial to have the structured data also on category pages, in sidebars, on search result pages, etc., for various reasons. The more the merrier.
It’s no problem to specify only a subset of the content. Neither Microdata nor Schema.org require any properties.
And yes, by using Schema.org’s url property, you give consumers the chance to learn
that the two items are about the same thing, and
that they might find more properties about the item by following the URL.
(If, or which, consumers actually do this is another topic.)
I am interested in tagging the page that features all the services.
My particular industry Schema doesn't offer the span itemprop="itemOffered". Thus, should I make each the services page reflect the Product Schema rather than the industry specific itemtype, Or is it best to specify on the services page the product Schema and then on the individual product pages use the industry-specific itemtype and list the product using makesoffer?
Technically, Poe, a product can also be a service. So in your case (without knowing more info about what you offer), you can use the Product Schema for your service.
However, there is another way to mark up your service, which is by using a GoodRelations markup to augment the Schema.org/Offer markup. Here's a link to another stackoverflow post that perhaps can give a better example that I can: Using Schema.org and GoodRelations markups for services
Hope that helps.
We have been using schema.org to markup our products on the web with metadata.
We have a system where we have alternate part numbers for products and customers want to be able to search for any of the alternate part numbers.
Using schema.org or GoodRelations how should we mark up alternate part numbers? We think we should have one page on the web per part on not one page per alternate part number but we do want Google and Bing to be able to find and understand our alternate part number semantically?
Any ideas?
A "product part" concept can be represented in GoodRelations by an object property isAccessoryOrSparePartFor (http://purl.org/goodrelations/v1#isAccessoryOrSparePartFor) that is allowed on a class ProductOrServiceModel (http://purl.org/goodrelations/v1#ProductOrServiceModel)
I don't have an answer on whether Google or Bing take this property into account in their current implementation. This is a moving target and perhaps your best option is to give it a try.