Fact Check Schema Generator — Publish Clear Claim Reviews
Generate valid ClaimReview JSON‑LD with the claim, verdict text, author, and publish date so search engines can understand your fact checks.
Why many fact checks underperform
Pain points we solve
- Claims are vague or not explicitly captured in `claimReviewed`.
- Verdict text (`reviewRating.alternateName`) is missing or inconsistent.
- Authors and dates aren’t represented, reducing credibility.
- Manual JSON‑LD drifts out of sync with the review article.
How SwiftSchema helps
Solution
The generator guides the essentials: a clear `claimReviewed` sentence, a concise verdict in `reviewRating.alternateName` (e.g., True, False, Mixed), and accurate `author` and `datePublished` fields.
It outputs copy‑ready ClaimReview JSON‑LD that pairs well with Article/NewsArticle for the supporting write‑up.
How it works
How it works
- Choose FactCheck (ClaimReview) in the generator below.
- Write a clear claim sentence for `claimReviewed` and select a verdict for `reviewRating.alternateName`.
- Add `author` (organization or person), `datePublished`, and the canonical page `url`.
- Copy JSON or Script, paste on your fact check page, and validate in the Rich Results Test.
Paste once per fact check. Validate. Ship.
What is ClaimReview structured data?
Fact checks are published using ClaimReview, which includes the reviewed claim, a verdict text, and author/publish details. This helps search engines understand your assessments.
Essential properties
- claimReviewed— concise sentence stating the claim being evaluated.
- reviewRating.alternateName— textual verdict (“True,” “False,” “Needs Context”).
- author— Person or Organization publishing the fact check.
- datePublished/dateModified— ISO dates.
- url— canonical fact-check page URL.
- itemReviewed— optional; use Claim or CreativeWork referencing the original source (article, video, post).
- image/headline— optional but helpful for display.
- reviewRating.ratingValue— include if you use numeric scales; accompany with best/worst rating.
Content prep checklist
- Extract a clear claim statement in one sentence. Avoid summarizing multiple claims in one ClaimReview.
- Decide on the verdict taxonomy (True, False, Partially True, etc.) and keep it consistent across the site.
- Provide context explaining why the claim is rated as such; include sources and citations.
- Ensure the fact-check article includes the same claim and verdict text users see in search.
- Link to the original source of the claim (article, social post, video) and cite supporting evidence.
Implementation workflow
- Write the fact-check article and highlight the claim and verdict clearly.
- Generate ClaimReview JSON‑LD with claimReviewed, verdict, author, datePublished, and url.
- Reference the original claim source via itemReviewedor within the article content.
- Embed the schema once per fact-check page.
- Validate via Rich Results Test; fix warnings (missing claimReviewed, author, or reviewRating).
- Monitor Search Console for Fact Check enhancements and adjust if issues arise.
Handling multiple claims per article
- Use one ClaimReview per claim. If a fact-check article covers multiple statements, embed multiple ClaimReview objects, each with its own claimReviewed and verdict.
- Structure the page with clear headings for each claim to keep the content aligned with schema.
Troubleshooting checklist
- Missing verdict text: always include reviewRating.alternateName.
- Wrong author: use the actual publisher or journalist; ensure it matches the visible byline.
- Ambiguous claim: rewrite claimReviewedto be specific (“The city built 10 new parks in 2024”).
- No canonical link: include urland ensure it matches the page the user sees.
- Outdated date: update dateModifiedwhen you revise a fact check and note the change in the article.
Common Errors & Fixes
- Missing verdict text: include reviewRating.alternateNameeven if you use numeric ratings.
- Wrong author: use the organization/person actually publishing the fact check.
- Ambiguous claims: write a clear, single claim sentence in claimReviewed.
Required properties
@type=ClaimReviewclaimReviewedreviewRating.alternateNameauthor.namedatePublished
Recommended properties
urlitemReviewed.namereviewRating.ratingValuereviewRating.bestRatingreviewRating.worstRatingimage
{
"@context": "https://schema.org",
"@type": "ClaimReview",
"headline": "Fact check: Product schema always boosts rankings",
"datePublished": "2025-06-10",
"author": {
"@type": "Organization",
"name": "SwiftSchema Fact Lab"
},
"claimReviewed": "Adding Product structured data guarantees higher rankings.",
"reviewRating": {
"@type": "Rating",
"alternateName": "False"
},
"url": "https://example.com/fact-checks/product-schema-rankings"
}