Skip to content
Back to skills

Review

ASecurity

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.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-review/badge)](https://www.skillsdirectory.com/skills/thedaviddias-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Files in this skill

  • SKILL.md2.2 KB
  • references/rule.md3.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…