Multiple rich snippets on homepage? - schema.org

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.

Related

schema.org with two domains/websites: main site and shop site

I have two websites: www.mycompany.com and shopmycompany.com (not a subdomain) and would like to publish the relationship between them using schema.org. At present the www.mycompany.com identifies itself as an Organization and shopmycompany.com as a WebSite but there is no linkage between them. What would be best practices to present that connection?
Just from a quick skimming of https://schema.org/WebSite, there are multiple properties that would be fine as linking the website with the company:
author/creator
maintainer
provider
publisher
However, I wonder whether the Shop really should classified as a WebSite (which is a CreativeWork) and not rather as a Store which may simply have a parentOrganisation.
Yet another alternative would be to classify it as a Service, which is provided by the Organisation and can offer things.
And yet another alternative could be to classify the shop website as the OfferCatalog of offers made by the company.

Can a product's structured data be split into separate sections?

I'm working on a site optimizing their structured data and noticed they use YotPo to pull in ratings and reviews. YotPo is defining the Product and only has a couple of values for AggregateRating that are being injected via JavaScript.
I have all of the other product data coming from the CMS, so I defined all the other information there, but when I run Google's testing tool on the page, it sees it as 2 products and says it's missing fields for the YotPo markup that are already defined in my markup.
Is there some way to let Google know that they're both chunks of data for the same product so it only sees it as a single product with the combined data?
You need to make sure both Yotpo and your CMS use the same format. e.g. json-ld or microdata.
You can then indicate that they relate to the same product by setting both up to use the same id.

Structured data on product category pages?

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.)

Would it be Appropriate to use the Product Schema for Services?

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.

Can I use multiple Schema.org itemscope on one page?

I have been looking around on Schema.org but I don't understand one thing.
Can a single HTML page be made up of multiple schemas? If so do they need to be nested?
We have a one page landing / selling page we are working on.
I would like to have the following Schemas in place on it:
Organization
Product
Product Reviews
I am guessing the product reviews need to be nested within a product? Or can they be in a totally different part of the page?
Looked over what little docs there are.
You can have multiple schemas as well as mix on other markup types.
Some schema types naturally nest other types, like a product may contain product reviews. It is possible to markup the reviews outside the product but you may find less systems pick up the association correctly.