ClaimReview: What It Is, and Why It Is Not for Your Product Reviews
ClaimReview keeps showing up in schema advice for stores. It is the wrong tool. Here is what it actually does, and what to use instead.
What is ClaimReview actually for?
ClaimReview is a structured-data type for fact-checking. It lets a publisher mark up a claim someone made, the rating that publisher assigned to it, and the article where they explain the verdict. The output is the fact-check appearance in search: the claim, the reviewer, and a verdict like "False" or "Mostly true."
The intended authors are fact-checking organisations and newsrooms. The subject is a statement that can be true or false. None of that describes a product page, where the subject is an item for sale and the input is buyer sentiment, not a factual verdict.
Why does ClaimReview keep getting recommended for stores?
The word "review" is doing the damage. Schema advice gets copied between blog posts, and "ClaimReview" looks like the review type a store should reach for, especially next to the less obvious Product and aggregateRating pairing. The name is the trap.
The two types share almost nothing. ClaimReview rates a claim. Product reviews rate a thing customers bought. Putting the first on a product page does not bend it toward the second; it just attaches the wrong schema to the wrong subject.
What should I use for product reviews instead?
Use Product as the wrapper for the item, then nest the customer feedback inside it. Individual reviews go in Review. The summary across all reviews goes in aggregateRating, and that aggregateRating is what powers the star ratings buyers see in search results.
- Product: the item itself, with name, image, and identifiers.
- Review: a single customer review, with its rating, author, and body.
- aggregateRating: the average score and review count, the field that drives star snippets.
- Offer (optional but useful): price and availability, so the listing carries commercial context.
What happens if I leave ClaimReview on a product page?
You get no product stars from it, because ClaimReview does not feed the product rich result. The star snippet is driven by aggregateRating inside Product, and ClaimReview supplies neither.
At best the markup is inert and ignored. At worst it signals that the page is making fact-check claims it cannot support, which is not a flag you want on a commercial page. The honest move is to remove ClaimReview entirely from store pages and let Product do its job.
How do I tell the two apart at a glance?
Ask one question: what is being rated? If the answer is a statement that could be true or false, ClaimReview may apply, and only if you are a fact-checker explaining a verdict. If the answer is a product a customer bought and is reacting to, you want Product with Review and aggregateRating.
- Subject is a factual claim, author is a fact-checker: ClaimReview.
- Subject is a product, author is a customer: Product plus Review plus aggregateRating.
- Subject is a service or business reputation: Review on the relevant Organization or LocalBusiness type, not ClaimReview.
My reviews are correct schema but still not cited. Why?
Correct markup is necessary, not sufficient. Even Product schema only works if the review text is present in the page HTML the crawler reads, rather than injected later by a widget the crawler sees as empty. Valid schema wrapped around an empty container still validates and still earns you nothing.
Most review apps were built for the on-page shopper and stop there: the stars render for a human, but the underlying text stays trapped in script. Getting your existing reviews readable, corroborated, and quotable in search and AI answers is the gap BetterReviews is built to close.
What this adds up to
ClaimReview is a fine type used by the right authors for the right subject, which is fact-checking, not retail. For a store, it produces no stars and invites confusion. Use Product with Review and aggregateRating, put the review text in the server HTML so a machine can read it, and reserve ClaimReview for the fact-checkers it was designed for.
- Will ClaimReview give my product page star ratings?
- No. Product star snippets come from aggregateRating nested inside Product. ClaimReview describes a fact-checker's verdict on a claim and feeds the fact-check result, not the product rich result, so it produces no stars on a store page.
- Is ClaimReview ever right for an ecommerce site?
- Only if you genuinely publish fact-checks, which a store almost never does. The customer feedback on a product page is sentiment about an item, not a verdict on a factual claim, so Product with Review and aggregateRating is the correct schema, not ClaimReview.
- I already added ClaimReview. What should I do?
- Remove it from your product and store pages, then add Product with Review and aggregateRating instead. Leaving ClaimReview in place earns no stars and can read as misapplied markup on a commercial page, so the cleanest fix is to take it out.
- Does correct review schema guarantee I get cited?
- No. Schema is necessary but not sufficient. The review text also has to be in the page HTML a crawler can read, rather than injected by a widget the crawler sees as empty. Valid schema around an empty container still earns nothing.