Hello fellow BHW's!
First and foremost: Apologies if this topic has already been discussed before!
I've been exploring Review and AggregateRating Structured Data and would like to implement it on my pages. However, I find it challenging to distinguish the correct usage, as I can't seem to find an exact match that fits my landing pages. Like many others, I have landing pages comparing casinos and bonuses—the classic top 10 list format.
I understand that Review and AggregateRating aren't new concepts, but since Google itself highlighted them in its January 2025 core update, it seems like a new area of focus that they might reward if used correctly.
From what I gather, Review and AggregateRating are often intended for a single product or service, not necessarily a list of "products" like casinos or bonuses.
I have a few questions that I hope will help clarify things:
Best regards,
Didge
First and foremost: Apologies if this topic has already been discussed before!
I've been exploring Review and AggregateRating Structured Data and would like to implement it on my pages. However, I find it challenging to distinguish the correct usage, as I can't seem to find an exact match that fits my landing pages. Like many others, I have landing pages comparing casinos and bonuses—the classic top 10 list format.
I understand that Review and AggregateRating aren't new concepts, but since Google itself highlighted them in its January 2025 core update, it seems like a new area of focus that they might reward if used correctly.
From what I gather, Review and AggregateRating are often intended for a single product or service, not necessarily a list of "products" like casinos or bonuses.
I have a few questions that I hope will help clarify things:
- Which "features" within structured data are best suited for lists comparing casinos and bonuses? (Product, Review, etc.)
- Is it possible to have multiple "reviews" on a single page?
- Could you be penalized for highlighting iGaming products using schema markup?
- Have I missed something, or are there other schema markups that would be a better fit for this specific use case?
- Do you—or someone you know—have any examples of before-and-after results from implementing this type of markup (if that’s even a thing)?
Best regards,
Didge