Duplicate Schema.org content on same page - schema.org

I am currently setting up Schema.org content on multiple sites.
They are using the LocalBusiness type and have telephone/address both in the header and footer.
When setting up Schema.org on both sections and testing, I get 2 LocalBusiness returned with the same content.
Does this affect in any way the Schema.org? Would it be better to only have it pull 1 section instead of 2?

With Microdata/RDFa, you are not annotating your page’s content. You are just using your content/markup as "carrier" to provide structured data.
If the telephone number of the local business appears several times on the same page, there’s no need to mark it up with Microdata/RDFa several times: you only need it one time for the consumers that make use of your structured data.
So don’t provide two LocalBusiness items on the same page, if both really represent the same local business.

Related

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.

Multiple rich snippets on homepage?

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.

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

How to markup alternate part numbers for Schema.org Product?

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.

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.