SiteVerdict — Review Stars & Rating Schema Checker avatar

SiteVerdict — Review Stars & Rating Schema Checker

Pricing

Pay per event

Go to Apify Store
SiteVerdict — Review Stars & Rating Schema Checker

SiteVerdict — Review Stars & Rating Schema Checker

Will Google show review stars for your pages? Checks Review and AggregateRating markup (JSON-LD, microdata, RDFa) against Google's review snippet rules and self-serving review policy, then gives exact fixes and corrected JSON-LD. Monitoring and alerts built in.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Aman Thakran

Aman Thakran

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Categories

Features

Limited permissions

Share

Review Stars & Rating Schema Checker — will Google show your stars?

Find out in seconds why your product, recipe, course or app pages are not getting review stars in Google — and get the exact fix. SiteVerdict reads the Review and AggregateRating markup on each page (JSON-LD, microdata and RDFa), checks it against Google's review snippet rules and the self-serving review policy, and gives you a plain-English verdict, a fix for every problem and a corrected JSON-LD block.

  • ✅ Star eligibility per page: eligible, eligible-with-warnings, not-eligible or no-review-markup
  • 🚫 Self-serving review detection: catches the #1 reason businesses lose stars — a LocalBusiness or Organization rating itself on its own site
  • 🔧 Fixes, not just errors: every issue has a fix, plus ready-to-paste corrected JSON-LD
  • 🔁 Monitoring: schedule it and get a Slack/webhook alert the day a theme update, app or plugin breaks your stars
  • 🧩 Spots review widgets (Trustpilot, Yotpo, Judge.me, REVIEWS.io, Feefo, Okendo, Stamped, Loox, Bazaarvoice, PowerReviews…) that inject markup with JavaScript
  • 🤖 Optional AI fix with your own Anthropic or OpenAI key (off by default)

Who it is for

  1. E-commerce and Shopify/WooCommerce stores — check every product page from your sitemap after a theme or review-app change.
  2. SEO agencies — audit a client's whole catalogue in one run and hand over a report with fixes.
  3. Local businesses and their developers — confirm whether that "4.9 ★" markup on the homepage can ever show in Google (spoiler: usually not — it is self-serving).

What it checks

CheckBased on
aggregateRating has ratingValue and ratingCount or reviewCountGoogle review snippet required properties
Counts are whole numbers above 0; rating is a number inside worstRating–bestRating (default 1–5)Google review snippet docs
Comma decimals ("4,5"), "9/10", "90%"Parsed and flagged where Google may misread them
Review has an author with a real name (< 100 characters, not promo text), itemReviewed when stand-alone, reviewRating, datePublishedGoogle review snippet docs
The reviewed item's @type is supported (Product, Recipe, Book, Course, Event, HowTo, LocalBusiness, Organization, SoftwareApplication, Movie, Game, CreativeWorkSeason/Series, Episode, MediaObject, MusicPlaylist, MusicRecording and their subtypes) and has a nameGoogle list of valid itemReviewed types
Self-serving reviews: LocalBusiness/Organization rating itself on its own domain → not eligible. Third-party review pages about another business are recognised and allowedGoogle self-serving review policy
Ratings visible on the page (rating or count appears in the HTML text)Google: marked-up reviews must be visible to users
Ratings on category/list pages; many rated products on one pageGoogle: ratings must be about one specific item
Duplicate markup (e.g. JSON-LD plus microdata, or theme plus review app)Avoids conflicting counts
Invalid JSON-LD blocks, blocks split across scripts with the same @id (merged correctly)JSON-LD 1.1

Example output (one page)

{
"url": "https://shop.example.com/products/rain-jacket",
"starEligibility": "not-eligible",
"score": 26,
"summary": "1 reviewed item: NOT eligible for stars - 4 error(s), 2 warning(s).",
"issues": [
{ "severity": "error", "code": "aggregateRating-missing-count", "message": "Product \"Rain Jacket\": aggregateRating needs ratingCount or reviewCount (at least one is required).", "fix": "Add \"ratingCount\" (number of ratings) and/or \"reviewCount\" (number of written reviews)." },
{ "severity": "error", "code": "aggregateRating-out-of-range", "message": "Product \"Rain Jacket\": ratingValue 9.2 is outside the 1-5 scale.", "fix": "Add \"bestRating\": 10 to declare your scale." },
{ "severity": "error", "code": "review-author-promo", "message": "... author name \"50% OFF TODAY\" looks like promotional text.", "fix": "Author must be a real person or organization name." }
],
"items": [{ "type": "Product", "name": "Rain Jacket", "eligibility": "not-eligible", "fixSnippet": "<script type=\"application/ld+json\">{ ... \"bestRating\": 10 ... }</script>" }],
"widgets": ["Judge.me"]
}

Before: "Why don't we get stars?" — After: a list of 3 exact errors, a corrected JSON-LD block and an alert if it ever breaks again.

How to use

  1. Paste page URLs into Pages to check and/or add your sitemap (we take up to 2,000 pages from it).
  2. Click Start. Open the Star eligibility and Issues & fixes tabs, or download the HTML report (REPORT in the key-value store) or RESULTS_CSV.
  3. For ongoing protection, switch on Monitor mode, add a Slack or webhook URL and schedule the Actor weekly.

No URLs? It runs on fictional sample pages so you can see every kind of finding for free.

Pricing

Pay per event — you only pay for pages that were actually checked:

EventPrice (proposed)
Page checked (page-checked)$0.004
AI fix generated (ai-fix-generated, only when you switch on AI and it succeeds)$0.01

Examples: 100 product pages ≈ $0.40, a 1,000-page catalogue ≈ $4, weekly monitoring of 50 key pages ≈ $0.80 a month. Errors, robots-blocked pages and sample mode are free. If your run's maximum cost is reached, every remaining page gets a not-processed row and is not charged; a page is always paid for before an AI fix is added to it. Your AI provider bills you directly for the AI step.

Benchmark (honest summary)

We compared ours with the structured-data validators on the Apify Store by their documented features (we do not run competitors' Actors).

SiteVerdictGeneric schema validators
Google review-snippet rules (required props, scale, counts)✅Partial (schema.org syntax only)
Self-serving review policy✅❌
JSON-LD node merging across blocks (@id)✅Rarely
Microdata + RDFa✅Usually JSON-LD only
Fix snippets / AI fix✅❌
Monitoring + alerts✅❌

Live check on 11 Oct 2026: BBC Good Food's pancake recipe splits its Recipe and aggregateRating into two script blocks with the same @id. A naive parser reports "missing type/name"; we merge them and correctly report eligible.

FAQ

Does "eligible" mean Google will show stars? No. Google decides case by case. Eligible means the markup follows the documented rules, so nothing on the page is stopping it.

My stars come from a JavaScript widget. Will you see them? This Actor reads the HTML your server sends (no browser), which is what most review apps output for SEO. If a widget injects markup only in the browser, we tell you and suggest checking with Google's Rich Results Test.

Why is my LocalBusiness rating "not eligible"? Since 2019 Google does not show stars for reviews a business hosts about itself (self-serving reviews). Keep ratings on products, recipes, courses etc.; your Google Business Profile reviews show separately.

Do you store my pages? No. Only the result is saved in your own Apify storage. Monitor mode keeps a small snapshot (eligibility + issue codes) in a named key-value store in your account.

Limits

  • HTTP only, no JavaScript rendering. robots.txt is always respected; pages that block bots are reported as robots-blocked and not charged. Empty or HTTP 202 responses (usually a bot-protection holding page) are reported as errors and not charged; sites behind such protection cannot be checked.
  • Max 2,000 URLs per run, 4 MB of HTML per page. Same-host requests are spaced (default 1 s, or the site's Crawl-delay up to 30 s).
  • Rule set follows Google documentation as of 11 Oct 2026 (re-checked 3 Nov 2026); Google may change its rules.

Sources & compliance