Do I need both Claim and ClaimReview on the same page?

Not always. ClaimReview already accepts inline text in itemReviewed, which is sufficient for the Fact Check Tools API. Adding a separate Claim node is recommended when the same claim appears across multiple pages or reviewers, because it gives every consumer a stable @id to deduplicate against.

How does Claim differ from Quotation?

Claim represents a factual assertion meant to be evaluated for accuracy. Quotation represents any cited utterance, including opinion, rhetoric, or color, without an implied truth value. Use Quotation when attribution matters but factuality does not, and Claim when a verdict is the point.

How is Claim used by AI engines?

AI engines that ground answers prefer pages whose factual assertions are explicit, structured nodes rather than buried in prose. A Claim node with appearance and sameAs links tells the engine "this assertion has these published occurrences and this canonical identity," which improves both citation accuracy and dedup.

Can I model anonymous or rumored claims?

Yes. Omit author, set text to the verbatim rumor, and use appearance to list every place it has surfaced. Pair with a ClaimReview whose reviewRating reflects the verdict (typically False or Misleading) to complete the record.

schema.org Claim Type for AI Fact-Checking

Q: Does Google still consume schema.org Claim and ClaimReview?

Yes, but in a narrower surface than before. Google phased out ClaimReview snippets in regular Search results in mid-2025, but the Factcheck Explorer Tool and the Fact Check Tools API continue to ingest the markup. Bing and several AI grounding pipelines still treat both types as authoritative claim signals.

schema.org Claim is a CreativeWork subtype that represents a specific, factually-oriented assertion that can be the itemReviewed of a ClaimReview or stand alone as a citable, machine-readable fact. It is the underlying primitive that AI engines and fact-checking platforms use to ground assertions to their original publication context.

TL;DR

Claim is the schema.org type for the assertion itself ("Marsha Blackburn voted against the VAWA reauthorization"), while ClaimReview is the verdict written about it. Use Claim to mark a discrete factual statement, appearance to list every CreativeWork in which the claim shows up, and firstAppearance to point at the earliest known occurrence. Google retired ClaimReview from regular Search snippets in 2025, but the Factcheck Explorer Tool, Bing, and several AI engines still consume both Claim and ClaimReview markup as grounding signals.

Definition

Claim is a schema.org type defined under the path Thing > CreativeWork > Claim and canonically published at https://schema.org/Claim. The vocabulary describes it as "a specific, factually-oriented claim that could be the itemReviewed in a ClaimReview." The claim's text is carried by the text property, common identity is signalled with sameAs URLs (typically Wikipedia or Wikidata identifiers when they exist), and a short label can be carried by name.

Two key properties extend CreativeWork specifically to support claim tracking:

appearance indicates an occurrence of the claim in some CreativeWork (every article, broadcast, or post in which it appears).
firstAppearance indicates the first known occurrence of the claim, providing a stable provenance anchor.

The type is still flagged as "new" in the schema.org vocabulary, meaning implementation feedback continues to shape its definition. It is intentionally lighter than ClaimReview: a Claim instance does not require a verdict, a reviewer, or a rating—only enough context to identify the assertion unambiguously.

Why this matters

AI answer engines and fact-checking platforms increasingly treat the claim itself as a first-class entity, separate from any single article that quotes or evaluates it. Marking the assertion with Claim lets a downstream system follow appearance links to every place the claim is published, follow firstAppearance to the original source, and join Claim instances to one or more ClaimReview verdicts.

Google's retirement of ClaimReview snippets from regular Search results in mid-2025 (covered by Poynter) reduced the SEO benefit of ClaimReview, but the underlying Claim graph remained valuable. The Factcheck Explorer Tool and the Fact Check Tools API still ingest the markup, AI engines that ground answers (Perplexity, ChatGPT Search, AI Overviews) prefer pages whose factual assertions are explicitly enumerated, and trust-and-safety teams use the same vocabulary for cross-platform claim deduplication.

The upside is high signal at low cost: a few extra JSON-LD nodes turn a flat article into a queryable claim graph that survives every consumer's roadmap change.

How it works

A Claim node lives alongside the rest of a page's structured data graph, typically inside the same