Only mark up reviews that are genuinely visible on the page, came from real customers, and are first-party (collected by you, not aggregated from elsewhere). Google's 2019 review snippet update made fake or third-party-aggregated review markup ineligible for rich results.
Review and AggregateRating schema is one of the most-abused schema types — and one Google has progressively cracked down on since 2019.
**Google's current rules (2026):**
1. **The reviews must be visible on the same page** that includes the schema. Marking up reviews displayed on a different page (or hidden via JavaScript) is a violation. 2. **The reviews must be first-party** — collected by your business directly. Aggregating reviews from Google, Yelp, or third-party platforms and marking them up as your own is explicitly forbidden. 3. **Self-serving reviews are not eligible for rich snippet treatment.** A "About us" page with AggregateRating is allowed but won't earn star snippets. 4. **Specific product, service, or business entity required.** AggregateRating must attach to a real entity (Product, Service, LocalBusiness, etc.) — not a generic page. 5. **Reviews must include all required properties.** The reviewer name (Person type), the rating value, and the review body. Missing any of these makes the markup ineligible.
**The correct implementation:**
{ "@context": "https://schema.org", "@type": "Service", "name": "Drain Cleaning", "provider": {"@type": "LocalBusiness", "name": "Your Business"}, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "reviewCount": "47", "bestRating": "5", "worstRating": "1" }, "review": [ { "@type": "Review", "author": {"@type": "Person", "name": "Sarah K."}, "reviewRating": {"@type": "Rating", "ratingValue": "5"}, "reviewBody": "Showed up within an hour, cleaned the main drain in 30 min, charged exactly the quote. Would call again.", "datePublished": "2025-11-14" } ] }
**Where to source reviews legitimately:**
- Reviews collected through your own intake form, survey, or post-job follow-up - Reviews submitted directly via your website's review form - Customer testimonials that customers gave you permission to publish
**Where NOT to source:**
- Scraping Google Business Profile reviews and republishing them with markup (violation) - Pulling Yelp reviews via API and marking them up on your own site (violation) - Aggregating BBB review scores into your AggregateRating (violation) - Inflating reviewCount with reviews from different products or services (violation)
**The "summary aggregator" exception:** Sites that exist primarily to aggregate reviews (Yelp, TripAdvisor, RateMDs) can mark up their aggregated review data because aggregation IS their service. A typical business website cannot.
**What happens when you violate:**
Google has manual actions specifically for spammy structured data ("Spammy Structured Markup"). Penalty: rich snippet eligibility revoked across the entire domain — typically 6–12 months. Recovery requires removing offending markup and submitting a reconsideration request.
**Realistic 2026 reality check:** even properly-implemented review schema on a small business site rarely triggers the gold-stars rich snippet anymore. Google reserves it primarily for high-authority sites, e-commerce product pages with real review counts in the hundreds, and verified review-platform integrations. Most service businesses should implement the schema correctly (helps with AI Overview eligibility and Knowledge Panel) but not expect the visual star treatment.
- **Should I use JSON-LD, Microdata, or RDFa for schema markup?** — JSON-LD, period. Google has explicitly stated JSON-LD is preferred since 2017. Microdata and RDFa still parse correctly but add no benefit and complicate maintenance. Strip out any old Microdata when you migrate. - **Is FAQ schema still worth implementing in 2026?** — Yes, but with reduced expectations. Google removed FAQ rich snippets from most non-authoritative sites in August 2023 and continued tightening through 2024–2025. FAQ schema still helps with semantic understanding and AI Overview citations, even when rich snippets don't display. - **Can I use Product schema for service businesses?** — Yes — Service schema (a Product subtype) is the right choice for service businesses. Don't use the generic Product schema for services; use Service, with proper offers, areaServed, and provider properties. - **Should I add Author schema for E-E-A-T?** — Yes — Author/Person schema with sameAs links to professional profiles is one of the few concrete technical things you can do to signal E-E-A-T. Pair it with a real bio page, byline on every article, and verified author identity across platforms.