Reputation: 313
There is the coins catalog https://colnect.com/en/coins/list/year/1889
Each item in list has Product
Microdata, some items in marketplace have the offers
property. For example: this stamp.
Recently the Structured Data Testing Tool began to show error instead of warning for missing offers
property on Product
pages against it still described as recommended property in product rich result docs. Also here are 'Either "offers", "review", or "aggregateRating" should be specified' errors in Google Search Console.
What kind of structured data will be most suitable for those items?
How to avoid these structured data errors? Will it be correct to have Thing
type for catalog items and then change it to Product
when the item will be placed in marketplace?
Update 2019-10-15: Structured Data for mentioned above stamp are here. At the moment it has offers
so there are 3 warnings only.
And Structured Data for some other stamp without offers
, here is the missing offers
filed error.
It seems Google does not allow schema.org Product
markup without offers
.
Upvotes: 0
Views: 546
Reputation: 7781
Hard to answer your issue (Next time please add some code examples).
In general in this URL:
Without this warning:
'Either "offers", "review", or "aggregateRating" should be specified'
- But read this:
https://www.checkerboard.com/web-development/fix-offers-review-aggregaterating-specified/
Product VS Thing - it's better to use more specific object-type (This is not related to the "marketplace" option to pay Online) (Google rich-snippet related to products).
productontology: For coins/Sports Cards and so on you could add extra-data by productontology (not mandatory): http://www.productontology.org/
Related: Can we make structured page data for any type of entities?
Upvotes: 1