HighLevel’s Reviews widget outputs AggregateRating structured data on website pages, but the markup is missing required fields, causing Google’s Rich Results Test to flag a critical issue: “Either ratingCount or reviewCount should be specified.”

Where the problem occurs

Websites (Website Builder) → Pages using the Reviews widget

(Structured data / Rich Snippets output in the page source)

What happens now

When a page includes the Reviews widget, HighLevel injects Review/AggregateRating schema in the page code.

Google’s Rich Results Test flags the AggregateRating as invalid/critical because neither ratingCount nor reviewCount is included, even though ratingValue is present (ex: 5.00).

Result: pages get structured data warnings that can reduce eligibility or trust for review rich results, and it creates confusion for agencies trying to deliver “SEO-clean” sites.

What should happen instead

HighLevel should output valid AggregateRating structured data by including at least one of the required properties:

ratingCount or reviewCount

…and ensure the output aligns with Schema.org + Google’s structured data expectations.

Real-world use case

We build client sites in HighLevel and often add the Reviews widget to service pages/homepages for social proof. When we run QA using Google Rich Results Test or Search Console, we see a critical structured data issue on pages that otherwise pass. This creates:

extra client support + explanations (“why is Google saying this is broken?”)

potential reduced SEO performance/eligibility for review enhancements

additional dev time to troubleshoot something generated by the platform

Current workaround (if any)

Avoid using the Reviews widget on SEO-critical pages, or

Use a custom-coded schema injection (manual JSON-LD) and attempt to suppress/ignore the widget’s output (not always clean/easy), or

Accept the error and ship anyway (not ideal for agencies and SEO deliverables)

Suggested fix or enhancement

Option A (Best): Update the Reviews widget schema generator to always include:

reviewCount (total number of reviews displayed/available) and/or

ratingCount (total rating count)

…and ensure the values are accurate.

Option B: If accurate counts are not available in some cases, provide a setting/toggle:

“Enable Review Schema” (on/off)

so users can disable invalid schema rather than being forced into a critical error.

Option C: Output the schema as JSON-LD in a single, clean block (if not already), ensuring required properties are present for AggregateRating.