Review Schema Markup: Get Star Ratings in Google Search (2026)

I am Adam, editor at BGR Review. I have spent the last three years watching sites gain and lose review stars in Google - sometimes overnight, sometimes for reasons the site owner never traced. The rules have tightened three times since 2019 and again in the September 2025 spam update. This is the guide I wish existed then: which pages qualify, exact templates that pass validation, and the mistakes that get stars stripped.

What review stars actually are

The gold stars under a search result come from structured data - specifically JSON-LD markup that tells Google "this page has a rating and here is the score." They are not a ranking factor directly. They are a click-through factor. Sites with stars in the SERP average 35% higher CTR at the same position, which pulls rankings up over time. That is why they are worth the work.

Which page types Google will show stars for in 2026

This is the list that matters. Marking up any type outside it will validate but not render stars, and marking up types Google has explicitly banned can trigger a manual action.

Eligible

• Product - a single product page with a price, stock status and reviews from real buyers.
• LocalBusiness and its subtypes (Restaurant, Dentist, HomeAndConstructionBusiness, etc.) - the business's own page describing the business.
• Recipe, Book, Movie, Course - self-contained content items that users rate.
• SoftwareApplication - app or SaaS product pages with real user ratings.
• Event - specific dated events with attendee reviews.
• Organization - only when the reviews are of the organisation itself and only in narrow cases. Google has been aggressive here since 2023.

Not eligible

• Blog posts, category pages, homepages, contact pages, "about us" pages.
• Service pages unless they are marked up as LocalBusiness with a physical business behind them.
• Aggregator or comparison pages that rate other companies (Google now treats these as third-party review platforms, not publishers of first-party reviews).
• Landing pages built specifically to catch star traffic. These get manual actions fast.

Review vs AggregateRating - and when to use both

These are two separate schema types and they answer two different questions.

Review is a single reviewer's rating - one name, one date, one score, one body. Use it when you display individual reviews on the page.

AggregateRating is the summary - average score, review count. Use it when you show the overall rating.

Most product and business pages carry both: an AggregateRating for the summary plus multiple Review entries for the individual reviews shown on the page. The critical rule Google added in 2024: the rating value in the schema must match a rating value visible on the page. Marking up a 4.8 average when the page shows "12 reviews" without a visible average is grounds for the schema being ignored.

The template that works for a product page

This is the shape Google's own documentation shows and the one that passes Rich Results Test cleanly. Wrap it in a script tag with type="application/ld+json" and place it in the head or the top of the body.

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Acme Wireless Headphones Model X",
  "image": "https://example.com/photos/x/front.jpg",
  "description": "Over-ear wireless headphones with 40-hour battery.",
  "sku": "AWH-X-BLK",
  "brand": {
    "@type": "Brand",
    "name": "Acme"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/headphones-x",
    "priceCurrency": "USD",
    "price": "199.00",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "324"
  },
  "review": [
    {
      "@type": "Review",
      "author": { "@type": "Person", "name": "Jamie L." },
      "datePublished": "2026-01-14",
      "reviewBody": "Sound is clean, battery lasts the flight.",
      "reviewRating": {
        "@type": "Rating",
        "ratingValue": "5",
        "bestRating": "5"
      }
    }
  ]
}

Notice: real name (not "Anonymous"), real date, real body. Google's 2024 update penalises schema with dummy reviewers.

The template that works for a local business page

{
  "@context": "https://schema.org",
  "@type": "Dentist",
  "name": "Riverside Dental",
  "image": "https://example.com/riverside.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 River Road",
    "addressLocality": "Boulder",
    "addressRegion": "CO",
    "postalCode": "80301",
    "addressCountry": "US"
  },
  "telephone": "+1-303-555-0148",
  "priceRange": "$$",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.9",
    "reviewCount": "186"
  }
}

For local businesses, the AggregateRating alone is usually enough. Google pulls individual reviews from Google Business Profile, not from your schema.

The six mistakes that lose sites their stars

1. Self-serving reviews on your own product with no visible source

You wrote 12 five-star reviews yourself, put them in schema, and stars appeared. Google's spam classifier now catches this within a few weeks. When it does, stars vanish and often will not return without a manual review. The fix is to display real reviews from real buyers on the page - and match the schema to what is visible.

2. Marking up reviews on pages that do not qualify

Blog posts with "star ratings" for tools you reviewed. Homepage with "4.9 stars from 2,000 customers." Google may show stars briefly and then strip them. Since 2023 this can trigger a partial manual action against the property.

3. Mismatched rating between schema and page

Schema says 4.8. Page displays "Rated Excellent" with no number. Google ignores the schema. Fix by displaying the number on the page.

4. Using AggregateRating without any Review entities

Legal but low quality. Some sites still get stars this way, most do not. Add at least three real Review entries and quality goes up.

5. Reviews with future dates or dates from before the product existed

Common mistake in headless CMSes that default datePublished to something wrong. Rich Results Test flags this. Google ignores schema that fails validation.

6. Copying schema between templates and forgetting to update the values

Every product page ends up with the same name, same review count, same reviewer names. Google's duplicate detection catches this in bulk and often demotes the whole property.

How long until stars appear

Once your schema validates and the page qualifies, Google typically shows stars within 3-14 days of the next crawl. For high-traffic pages that get crawled daily, it can be under a week. For low-traffic pages, request indexing in Search Console to speed it up.

If two weeks pass and no stars, the usual causes are: the page type does not qualify, the reviews are marked as owner-provided rather than third-party, or the site is under a policy review from a previous violation.

How to validate your schema before shipping

1. Rich Results Test at search.google.com/test/rich-results - this is the only tool that tells you what Google specifically parses and whether stars are eligible.
2. Schema.org Validator at validator.schema.org - checks the JSON-LD is syntactically valid but does not tell you whether Google will render stars.
3. Search Console Rich Results report - after deploying, this shows how many pages Google detected the schema on, and any errors.

Do not treat "valid" as "eligible for stars." Rich Results Test says whether Google will consider showing stars. The other two only say the code is well-formed.

The 2025-2026 policy changes worth knowing

• September 2025 spam update: Google now cross-checks the rating in schema against reviews visible in the DOM. Hidden or JavaScript-loaded reviews that never render count as absent.
• Organization self-reviews: Marking up your own company page with an AggregateRating built from reviews on Trustpilot or Google is allowed if the review count matches what those platforms show and you display the source. Fabricating this is the fastest way to lose stars sitewide.
• Service business categories: Service pages under LocalBusiness now need a real address and phone in the schema, not a virtual office.

What actually moves CTR - and what doesn't

A 4.7 average with 300 reviews outperforms a 5.0 with 6 reviews. Users trust volume with a few complaints more than perfection with few voices. If you have 20 real reviews averaging 4.6, ship the schema. Do not wait for 100.

Once stars are showing, add the review count in the meta description too - "Rated 4.7 (300+ reviews)" - and CTR rises another 5-8% on average.

When schema is not the bottleneck

If you have valid schema on a qualifying page and stars still are not appearing, the issue is usually one of these: page has thin content, page has low authority in the site, page has quality signals against it, or the reviews on the page are too obviously templated. Schema alone does not overcome a page that Google does not trust.

The pages that earn and keep stars long-term share a pattern: real reviewers, visible ratings, matching schema, updated regularly, and content that is genuinely useful beyond the rating. Everything else is a shortcut Google eventually closes.

Frequently Asked Questions

What are the eligible page types for review stars in Google Search?

Google shows review stars for pages detailing Products, LocalBusinesses, Recipes, Books, Movies, Courses, SoftwareApplications, and Organizations (under strict conditions for self-reviews). Marking up any other page type will not result in star ratings and could lead to penalties if misused.

Why are my review stars not showing up despite having valid schema?

Review stars might not appear if the page type is ineligible, the rating value in the schema does not match a rating visibly displayed on the page, or the content violates Google's policies like faking reviews or hiding the rating source from users. Always ensure on-page transparency.

What is the difference between Review and AggregateRating schema?

Review schema is for individual user reviews, capturing one person's rating, score, and comments. AggregateRating schema summarises multiple reviews into an average score and total count. Most eligible pages use both: AggregateRating for the overall summary and individual Review entries for each displayed review.

How long does it take for review stars to appear in Google Search results?

Once valid review schema is correctly implemented on an eligible page and Google re-crawls and processes the data, star ratings typically appear within one to two weeks. However, there is no guaranteed timeframe, and consistent compliance is key to maintaining them.

Can I get review stars for blog posts or category pages?

No, Google explicitly states that blog posts, category pages, homepages, and abstract service pages are not eligible for review stars. Attempting to apply review schema to these page types will not render stars and can lead to schema being ignored or even manual actions for policy violations.