Check and add structured data that describes user reviews and average ratings on product or service pages. Verify required fields against real reviews and validate the markup for star-rating search results.
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.
review checks and adds structured data that communicates reviews on product or service pages to search engines. It examines Review for individual reviews and AggregateRating for average ratings and counts. Checks cover missing or inconsistent rating values, rating counts, and upper and lower rating limits. It also handles adding values based on actual reviews to JSON-LD.
Use it to review implementations intended for star-rating displays in search results on e-commerce or review websites. It applies to pages publishing user reviews of products, stores, recipes, apps, books, and similar subjects.
AggregateRating and identify any missing required fields.”Ratings must be based on reviews from real users. Fabricated or self-serving ratings are treated as violations of Google’s guidelines. Validate the markup with Google’s Rich Results Test before publishing. The skill’s approach is to remove rating data from pages that have no genuine reviews.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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.
Review schema on individual review pages and AggregateRating on product/service pages to earn star-rating rich resultsAggregateRating requires ratingValue, ratingCount or reviewCount, and valid bestRating / worstRating valuesInspect 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.
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 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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.