How to Use This Rich Snippets Audit Checklist
Rich snippets pull structured data from your pages and display it directly in search results — showing star ratings, prices, stock status, and breadcrumbs before a user clicks. For ecommerce stores, each missing or broken schema element is a missed opportunity to occupy more visual real estate in search results and improve click-through rates.
This checklist covers 12 discrete audit items across product schema, review markup, breadcrumbs, sitelinks, and technical validation. For each item, run the Google Rich Results Test or Schema Markup Validator against your live URLs. Mark each item as PASS if it renders without errors in the testing tool and appears correctly in search results, or FAIL if it triggers a warning, error, or returns no structured data at all.
Product Schema Checks (Items 1–4)
**Item 1 — Product name matches page H1:** PASS if the `name` property in your Product schema exactly matches the visible H1 on the product page. FAIL if there is a mismatch, if the field is missing, or if the name is truncated in the schema but not on-page. Search engines cross-reference these values; discrepancies can suppress the rich result.
**Item 2 — Price and currency are present and accurate:** PASS if `offers.price` and `offers.priceCurrency` are populated with the correct live price in ISO 4217 format (e.g., `USD`). FAIL if price is hardcoded in schema but dynamic on-page, if currency is missing, or if the price in schema is stale. Google will suppress price snippets when the schema value contradicts the visible page price.
**Item 3 — Availability uses accepted enumeration values:** PASS if `offers.availability` is set to a schema.org/ItemAvailability value such as `InStock`, `OutOfStock`, or `PreOrder`. FAIL if the field is absent, uses a free-text string like `available`, or contradicts the in-page copy. Out-of-stock products showing `InStock` in schema result in a Google manual action risk.
**Item 4 — Product image meets minimum spec:** PASS if at least one `image` URL in the schema points to a crawlable image at 160×90 pixels or larger, with the image returning a 200 status. FAIL if the URL is relative, behind authentication, returns a 404, or if no image property is present at all.
Review and Rating Schema Checks (Items 5–7)
**Item 5 — Aggregate rating has both ratingValue and reviewCount:** PASS if `aggregateRating.ratingValue` is a decimal between 1 and 5 and `aggregateRating.reviewCount` reflects the actual number of published reviews. FAIL if either property is absent, if `ratingValue` is outside the 1–5 range without a matching `bestRating` property, or if `reviewCount` is set to zero or a placeholder value. Google requires both fields to render star snippets.
**Item 6 — Review schema is not applied to self-authored content:** PASS if every `Review` entity in the schema corresponds to a genuine third-party customer review visible on the page. FAIL if reviews are written by the store itself, curated from staff, or generated programmatically without real customer input. Google's review snippet guidelines explicitly prohibit first-party promotional reviews from rendering as rich snippets.
**Item 7 — Review schema is only on pages where reviews are visible:** PASS if the aggregate rating markup appears only on pages where star ratings and review counts are rendered in the HTML for users. FAIL if schema is injected on category pages, homepages, or product pages that display no visible reviews. Hidden review markup is a policy violation and triggers manual penalties.
Breadcrumb and Site Navigation Checks (Items 8–9)
**Item 8 — BreadcrumbList schema matches visible breadcrumb trail:** PASS if the `BreadcrumbList` schema on each product or category page reflects the same hierarchy shown in the on-page breadcrumb navigation, with correct `position` integers starting at 1. FAIL if any `item` URL in the list returns a non-200 status, if `name` properties are missing, or if the schema breadcrumb depth differs from what is visually displayed.
**Item 9 — Sitelinks searchbox is implemented on the homepage only:** PASS if a `SearchAction` schema block is present on the homepage, points to a functional internal search URL, and the `query-input` property uses the `required name=search_term_string` format. FAIL if the `SearchAction` is placed on interior pages, if the search URL returns 404 results, or if the schema is missing entirely — stores with strong branded search volume lose a dominant SERP feature without it.
Technical Validation Checks (Items 10–12)
**Item 10 — No critical errors in Google Rich Results Test:** PASS if running your top 10 product URLs through the Google Rich Results Test returns zero red errors. Warnings are acceptable but require documentation. FAIL if any URL surfaces a critical error such as a missing required field, an unrecognized schema type, or a property type mismatch (e.g., a string value where a number is required).
**Item 11 — Schema is implemented in JSON-LD, not Microdata or RDFa mixed inconsistently:** PASS if all structured data on the site uses JSON-LD exclusively, placed in `<script type="application/ld+json">` blocks in the `<head>` or `<body>`. FAIL if the site mixes JSON-LD with Microdata or RDFa on the same page for the same entity type, which creates conflicting signals and unpredictable rendering in search results.
**Item 12 — Structured data is present in the rendered HTML, not only the static source:** PASS if crawling your product pages with a JavaScript-rendering tool (such as Google's URL Inspection tool in Search Console) shows the same schema output as your static HTML source. FAIL if schema is injected only via client-side JavaScript after page load and Google's crawl budget or rendering queue delays indexing of that content — validate with the live URL inspection in Search Console, not just view-source.
Prioritizing Fixes After the Audit
Treat any FAIL on Items 1–4 and Item 10 as a P1 fix. Product schema errors directly block rich results from appearing on your highest-revenue pages. Address price, availability, and image issues before any other schema work — these are the fields Google validates most aggressively against on-page content.
Items 5–7 carry compliance risk beyond just lost snippets. A review schema violation can result in a manual action that suppresses rich results across the entire domain, not just the offending pages. Audit these with human review, not just automated tooling.
After resolving FAILs, revalidate each URL in the Google Rich Results Test and submit updated sitemaps via Google Search Console. Rich result eligibility updates within days of Googlebot recrawling the fixed pages, but appearance in live search results can take two to four weeks depending on crawl frequency for your domain.