thedaviddias/Front-End-Checklist / skills/review
review
VerifiedUse when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews. Use when auditing rich result eligibility for e-commerce or review sites.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| references/rule.md | markdown | 3.9 KB |
SKILL.md
View on GitHub---
name: review
description: "Use when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews. Use when auditing rich result eligibility for e-commerce or review sites."
metadata:
category: seo
priority: medium
difficulty: intermediate
estimatedTime: "10"
source: frontendchecklist.io
url: https://frontendchecklist.io/rules/seo/review
---
# Add Review schema markup
Star ratings in search results increase click-through rates by up to 35%; incorrect or missing schema means competitors with valid markup capture that visibility advantage.
## Quick Reference
- Use `Review` schema on individual review pages and `AggregateRating` on product/service pages to earn star-rating rich results
- `AggregateRating` requires `ratingValue`, `ratingCount` or `reviewCount`, and valid `bestRating` / `worstRating` values
- Ratings must reflect genuine user reviews — Google penalises self-serving or fabricated ratings
- Validate markup with Google's Rich Results Test before deploying
## Check
Inspect the page source or rendered DOM for JSON-LD blocks containing `"@type": "Review"` or `"@type": "AggregateRating"`. Verify required properties are present: `ratingValue`, `ratingCount`/`reviewCount`, `bestRating`. Run the URL through Google's Rich Results Test.
## Fix
Add a JSON-LD `<script>` block with `AggregateRating` nested inside the main entity (Product, LocalBusiness, etc.). Populate `ratingValue` and `ratingCount` from real review data. Remove any schema on pages with no genuine user reviews.
## Explain
Explain how Review and AggregateRating schema work, which page types are eligible for star-rating rich results in Google Search, and why fabricated ratings violate Google's structured data guidelines.
## Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Add Review schema markup. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
---
For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.
Rule page: https://frontendchecklist.io/rules/seo/review
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |