ClaimReview is a structured data markup defined by schema.org that allows publishers to explicitly label a specific claim and its corresponding fact-check rating within an article. By embedding this machine-readable code, a publisher communicates the exact statement being evaluated, the author of the claim, and the final veracity judgment—such as True, False, or Mixture—directly to search engine crawlers.
Glossary
ClaimReview Markup

What is ClaimReview Markup?
A standardized schema.org vocabulary used by publishers to tag fact-checked articles, enabling search engines to identify and prominently display verified information in search results.
This markup is the technical backbone of automated fact-check labeling in Google News and Search. When implemented correctly, it triggers rich results that display a fact-check snippet directly beneath the article link, increasing the visibility of verified information. The schema relies on a standardized reviewRating system, often using a 1-to-5 scale, to allow platforms to aggregate trust signals and combat misinformation algorithmically.
Core Properties of ClaimReview
The ClaimReview schema is a structured data vocabulary that enables publishers to tag fact-checked articles with machine-readable verdicts, allowing search engines to surface verified information directly in results.
claimReviewed
The exact textual assertion being fact-checked. This property captures the claim in its original wording to ensure precision.
- Must be a short, self-contained statement
- Avoid paraphrasing; preserve the original phrasing
- Example: "The Earth is flat" rather than "A claim about the Earth's shape"
- Search engines use this field to match queries against verified claims
reviewRating
A nested Rating type that encodes the factual verdict. This is the core machine-readable output of the fact-checking process.
- ratingValue: A numeric score (e.g., 1 for false, 5 for true)
- alternateName: The human-readable label ("False", "Mostly True", "Pants on Fire")
- bestRating/worstRating: Define the scale boundaries
- Enables search engines to display visual truth indicators
author
Identifies the Organization or Person that conducted the fact-check. This property is critical for establishing source credibility.
- Must reference a recognized fact-checking entity
- Used by Google to verify publisher eligibility for fact-check features
- Links to the publisher's Knowledge Graph entity
- Non-credentialed authors may cause markup to be ignored
itemReviewed
Describes the creative work or statement that contains the claim. This contextualizes where the assertion originated.
- @type: Typically Claim, CreativeWork, or Statement
- author: The original speaker or writer of the claim
- datePublished: When the claim was made
- appearance: Links to the URL where the claim appeared
- Provides provenance tracking for the disputed information
url
The canonical URL of the full fact-check article. This property directs both users and crawlers to the complete analysis.
- Must point to the fact-check page itself, not the homepage
- Used as the landing page in search result displays
- Should be a stable, permanent link
- Critical for citation integrity in AI-generated summaries
datePublished
The ISO 8601 timestamp when the fact-check was published. Temporal metadata is essential for assessing recency and relevance.
- Format: YYYY-MM-DD or full ISO 8601 datetime
- Enables filtering by freshness in search results
- Combined with dateModified for update tracking
- Stale fact-checks may be deprioritized by ranking algorithms
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about implementing and understanding the ClaimReview structured data schema for fact-checking.
ClaimReview is a structured data schema (a specific @type within Schema.org) used by publishers to tag fact-checked articles, enabling search engines like Google to identify, extract, and display verified information directly in search results. It works by embedding a JSON-LD object in the HTML of a fact-check article that explicitly defines the claim being reviewed, the author of the claim, and the review rating (e.g., 'True', 'False', 'Misleading'). This machine-readable annotation allows algorithms to bypass natural language ambiguity and programmatically understand the veracity of a statement. The schema connects a CreativeWork (the fact-check article) to a ClaimReview object, which contains a claimReviewed property and an itemReviewed property pointing to the Claim. The definitive reviewRating is then assigned, creating a high-confidence signal for platforms prioritizing authoritative content.
Related Terms
ClaimReview markup is one component of a broader automated fact-checking pipeline. These related terms define the end-to-end process from claim detection to verifiable justification.
Claim Detection
The NLP task of identifying check-worthy factual assertions within a text that can be verified against an evidence corpus. This is the critical upstream step before ClaimReview markup can be applied.
- Distinguishes factual claims from opinions and questions
- Prioritizes claims with high potential impact or virality
- Uses transformer-based classifiers fine-tuned on annotated datasets
- Outputs span annotations marking claim boundaries
Evidence Retrieval
The process of searching a document corpus to find the most relevant text passages that can support or refute a given claim. ClaimReview's appearance field often links to these retrieved evidence documents.
- Employs dense retrieval with bi-encoders for semantic matching
- Ranks passages by relevance and probative value
- May query structured knowledge graphs or unstructured web corpora
- Returns top-k passages for downstream veracity prediction
Veracity Prediction
The machine learning task of classifying a claim as true, false, or mixed based on aggregated evidence and source reliability signals. This classification populates the reviewRating field in ClaimReview markup.
- Standard ratings: True, Mostly True, Half True, Mostly False, False, Pants on Fire
- Models combine textual entailment scores with source credibility features
- Outputs a confidence-calibrated probability distribution
- Feeds directly into structured data generation for search engines
Explainable Fact-Checking
A verification framework that produces human-readable justifications and evidence provenance alongside a veracity label. ClaimReview's itemReviewed and reviewBody fields carry this explanatory content.
- Generates natural language summaries of reasoning chains
- Cites specific evidence passages with provenance URLs
- Enables auditability and user trust in automated decisions
- Required for compliance with journalistic transparency standards
Source Reliability Scoring
A dynamic assessment model that quantifies the historical trustworthiness and factual accuracy of a specific domain or publisher. This score informs which sources are used as evidence in ClaimReview-backed fact-checks.
- Aggregates signals: correction frequency, editorial policies, citation networks
- Updated continuously as new fact-checks are published
- Prevents circular verification loops
- Integrated into evidence ranking and veracity prediction pipelines

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us