You have 200 G2 reviews at 4.8 stars. Your homepage proudly displays the G2 badge. And yet in Google search results, your competitor shows star ratings and you show a plain blue link. Here's exactly why — and how to fix it in 15 minutes.
Google doesn't scrape G2. It doesn't check Capterra. It doesn't look at Trustpilot on your behalf. When Google crawls your website, it reads your HTML — and unless you've explicitly told Google about your reviews using structured data, those 4.7-star reviews might as well not exist from a search visibility standpoint.
This is why Zendesk shows "★★★★★ · Software · 4.3 · 6,847 reviews" directly in Google search results, while a competing support tool with equally strong G2 ratings shows up as a plain blue link. The difference isn't the reviews themselves — it's AggregateRating schema.
vs. what it looks like without schema:
The star ratings version gets significantly more clicks. Studies consistently show rich results with star ratings have 15–30% higher click-through rates than plain links for the same position.
AggregateRating is a type of structured data (written in JSON-LD format) that you embed in your website's HTML. It tells Google: "This product has X reviews with an average rating of Y out of Z stars." When Google trusts this data and your product appears in search results, it can display those star ratings directly in the SERP snippet.
The key word is embed. The schema lives in your HTML, not on G2. Google reads your page, finds the schema, validates it, and — if everything checks out — starts showing stars for your listing.
Important: AggregateRating must be nested inside a SoftwareApplication schema block to work for software products. Google needs to know what type of thing has ratings. A standalone AggregateRating without a parent @type context will be ignored or misinterpreted.
Here's a complete, production-ready schema block that combines SoftwareApplication + AggregateRating. Replace the placeholder values with your actual product data:
<Head> component using next/head, or use a dangerouslySetInnerHTML script tag in your page component<head> of your homepageThe aggregateRating block is what tells Google to display stars. The required fields inside it are:
| Field | Required? | What to put here |
|---|---|---|
ratingValue |
✓ Required | Your G2 average rating (e.g., "4.7") |
reviewCount or ratingCount |
✓ Required | Total number of reviews on G2 |
bestRating |
Recommended | Maximum possible rating ("5") |
worstRating |
Recommended | Minimum possible rating ("1") |
Do not fabricate review data. Google cross-checks structured data claims against what it can verify. If your schema claims 1,000 reviews but Google can find no evidence, it will ignore the schema or flag it as spam. Always use real numbers from your actual G2, Capterra, or Trustpilot profile.
During our audits of Indian SaaS companies, the single most frequent schema error we find isn't missing AggregateRating — it's having AggregateRating nested under the wrong parent type.
We audited one well-funded SaaS company whose schema had their product classified as "@type": "PerformingGroup" — a music group. Their AggregateRating was technically present, but it was attached to a music group entity. Google had no idea this was a software product. The star ratings never appeared.
Other common wrong parent types we find:
The fix: make sure AggregateRating is nested inside "@type": "SoftwareApplication" — not Organization, not WebSite, not any other type.
After you implement and validate the schema:
Validate before you deploy. Use Google's Rich Results Test to paste your schema and confirm it's valid. It shows you exactly what rich results you're eligible for and highlights any errors.
The same schema applies — just update the values with your Capterra or Trustpilot rating and review count. The ratingValue and reviewCount fields are platform-agnostic. You can also combine reviews across platforms using a weighted average, but keep it consistent and verifiable.
One important note: Google is more likely to show star ratings when the review platform is well-known and the data is easily verifiable. G2, Capterra, Trustpilot, and Google Business Profile reviews are all recognized sources.
We audit a lot of Indian SaaS websites. The pattern is consistent: the company has solid G2 ratings displayed as a badge on their homepage, but zero AggregateRating schema in their HTML. Their competitors — often US-based — have had this schema implemented for years and show star ratings in every relevant SERP.
The result is a click-through rate gap that compounds over time. For high-intent queries like "best HR software India" or "CRM software for sales teams," a result with 4.7 stars and 300+ reviews will consistently outperform a plain link even from a higher ranking position.
It's one of the highest-ROI technical SEO fixes available — it takes an afternoon to implement and the SERP impact is permanent.
@typereviewCount (not just ratingCount)bestRating: "5" and worstRating: "1"We audit your homepage for schema errors, missing structured data, and SEO issues that are costing you SERP real estate — in 24 hours, for free.
Get Your Free Audit →Yes — you can use your G2 rating and review count in your AggregateRating schema. Use your G2 average rating (e.g., 4.7) as ratingValue, your G2 review count as reviewCount, and 5 as bestRating. Google's guidelines require the rating to be verifiable, and G2 is a recognized third-party review platform. Just make sure your schema values match what's on your G2 profile.
AggregateRating schema doesn't directly change your ranking position, but it enables star ratings to appear in your SERP snippet. Star ratings significantly increase click-through rate (CTR) — typically 15-30% higher than plain blue links. Higher CTR sends positive engagement signals to Google, which can indirectly improve rankings over time.
G2 reviews don't automatically appear in Google SERP for your own website. Google reads your website's HTML, not G2's platform. To show star ratings in search results for your site, you need to implement AggregateRating schema (JSON-LD) on your homepage or product pages. Without this schema, Google has no way to know your software has ratings.
Google requires at least 1 review and a ratingCount of at least 1 to display star ratings in SERP. In practice, Google tends to show star ratings more reliably when there are 5+ reviews. There's no official minimum threshold published by Google, but more reviews with a verified source (like G2) increases eligibility.
You can add AggregateRating schema to any website platform: Webflow (via custom code injection in project settings), WordPress (via Rank Math or Yoast schema builder, or manually in header), Next.js/React (in the page component or layout file), Framer (via custom code component), and static HTML (directly in the head tag).
Yes — Google explicitly prohibits manipulative structured data. If your schema claims 500 reviews but Google can find no evidence of those reviews, it may trigger a manual action or ignore your schema entirely. Always use real, verifiable numbers from platforms like G2, Capterra, or Trustpilot.