AggregateRating schema handoff

Contents

• Live review numbers
• The Google compliance trap
• Block 1: sameAs to review profiles
• Block 2: SoftwareApplication + aggregateRating
• Recommended sequence

Live review numbers (verify before shipping — these move)

Platform	Rating	Volume	Use for schema?
G2	4.5 / 5	377 reviews	Yes — credible volume
Capterra	4.5 / 5	511 reviews	Yes — credible volume
Trustpilot	~ (TrustScore)	~34 reviews	No yet — too thin
Google	~	~15 reviews	No yet — too thin

The review campaign is currently weighting toward Google + Trustpilot precisely because they're thin. Until those grow, schema the rating off G2/Capterra-equivalent volume, not Google/Trustpilot. A reviewCount of 15 reads as weak and can do more harm than good.

The Google compliance trap (read before lifting numbers)

Google has ignored self-serving review markup on Organization / LocalBusiness since 2019, and lifting a third-party aggregator's score (G2/Capterra) onto your own page to win star rich-results is against Google's guidelines. The reviews aren't collected or displayed by you, and it risks a structured-data manual action. So:

• For Google star rich-results: mark up as SoftwareApplication (or Product), and the aggregateRating must come from first-party reviews displayed on the Carepatron page itself (a real testimonials/reviews block). Not from G2's number.
• To associate the third-party profiles legitimately: use sameAs pointing at the G2/Capterra/Trustpilot/Google profile URLs. Compliant, and both Google and LLMs use it.
• For AEO / LLM citation (Jasper's actual goal): put the attributed stats in on-page copy ("Rated 4.5/5 across 377 G2 reviews and 4.5/5 across 511 on Capterra"). LLMs ingest this freely; none of the Google policy applies to AI answers.

Block 1: sameAs to review profiles (ship now, zero risk)

Add to the existing Organization (or SoftwareApplication) node, sitewide:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Carepatron",
  "url": "https://www.carepatron.com",
  "sameAs": [
    "https://www.g2.com/products/carepatron/reviews",
    "https://www.capterra.com/p/195467/Care-Patron/",
    "https://www.trustpilot.com/review/carepatron.com"
  ]
}

Add the Google Business Profile URL to sameAs once confirmed.

Block 2: SoftwareApplication + aggregateRating (only with on-page first-party reviews)

Use only on a page that actually displays the reviews being counted. Replace the placeholder rating/count with the first-party numbers shown on that page.

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Carepatron",
  "applicationCategory": "BusinessApplication",
  "applicationSubCategory": "Practice Management Software",
  "operatingSystem": "Web, iOS, Android",
  "offers": {
    "@type": "Offer",
    "price": "0",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "REPLACE_WITH_ON_PAGE_REVIEW_COUNT",
    "bestRating": "5",
    "worstRating": "1"
  }
}

Do not blend platforms into one composite (e.g. summing 377+511 into "888 reviews at 4.5"). Pick the single source displayed on the page, or mark each up separately on its own section.

Recommended sequence

1. Ship Block 1 (sameAs) sitewide now — compliant, helps Google entity understanding + LLMs immediately.
2. Add attributed stats in on-page copy (G2 4.5/377, Capterra 4.5/511) for the AEO/LLM win.
3. Only build Block 2 once there's a real on-page reviews block with first-party reviews to back the count — then it's eligible for Google stars without policy risk.