An online fact check is most useful when you understand the exact claim it examined. A headline, rating badge, or search snippet may omit the qualification that explains the result. Before reusing a review in an article or an automated workflow, compare the wording, date, and context of the original claim with the statement you are checking now.
This guide uses Snopes as a reference point for reading published fact checks carefully. FactAPI.com is independent of Snopes and does not claim a partnership, access to a private Snopes feed, or an official Snopes API. The workflow below is an editorial and engineering checklist for finding relevant reviews without stripping away the context that makes them meaningful.
Begin with the specific wording under review
Snopes’ explanation of its fact-check ratings emphasizes that ratings evaluate the particular claim statement on a fact check. That is the key principle to preserve when you reuse a result. A rating should travel with its claim, not become a free-floating label attached to any similar sentence.
Write down the statement you are checking before searching. Include the named people or organizations, the relevant date, and any condition that changes its meaning. A claim that something happened once differs from a claim that it happens routinely. A statement about an old policy differs from a statement about a current policy. Similar keywords do not establish that two claims have the same scope.
Search for the claim, not just the topic
Use the distinctive parts of the statement to find candidate reviews. Search a quoted phrase when wording matters, then try variants for names, dates, and central relationships. If the claim concerns an image or a quotation, keep its accompanying caption or attribution in the search record. The same media item can circulate with different claims attached.
Treat search results as discovery aids. Open the full review before adopting a conclusion. A snippet can omit a correction, a condition, or the part of the analysis that distinguishes a genuine quotation from a misleading interpretation. Keep the candidate review’s URL and title, but do not mark the new claim assessed merely because a search result looks relevant. The review still needs to be compared with the specific statement at hand.
Read the evidence and explanation behind the rating
Identify what material the reviewer used and which part of the claim the evidence addresses. Look for original records, direct statements, images in their original context, and explanations of what could not be established. The value of a review lies in its reasoning and evidence, not only its endpoint label.
Separate the claim being quoted from the conclusion being reached. A fact-check article may reproduce a false assertion in order to analyze it. A retrieval system that selects that quotation without the surrounding evaluation could mistakenly treat the rumor as support. Store a passage’s role in your review notes: original claim, quoted source, analysis, limitation, or conclusion. This makes later summaries less likely to reverse the article’s meaning.
Check time and context before carrying a result forward
Record when the claim circulated, when the review was published, and whether the review identifies a later update. A factual conclusion can be tightly tied to a particular period. A review of whether an organization had announced a project at one time does not automatically resolve whether it announced the project later.
Consider a fictional example: a review establishes that a widely shared photograph shows a 2018 exhibition, not a newly opened event. That review may help identify the image, but it does not by itself answer every later question about the exhibition or the venue. Carry forward the narrow conclusion the evidence supports. Recheck the underlying sources when the new statement concerns a different date or makes a broader assertion.
Preserve a publisher’s rating vocabulary
Do not assume that every publisher’s labels can be mapped safely onto a single true-or-false switch. Keep the original textual rating and the original claim wording in separate fields. When a product needs a normalized status, document the mapping and retain the source label so that reviewers can inspect what was changed.
Use a distinct field for your own assessment of relevance. “Published review found” does not mean “this claim is supported,” and “review only partly matches” does not mean the publisher was uncertain about its original claim. These are different relationships. A good interface shows the source’s conclusion about its claim and your application’s assessment of whether that review applies to the present question. Avoid presenting your normalization as the publisher’s own words.
Compare independent evidence when the stakes warrant it
For a consequential claim, follow the review’s reasoning back to the underlying material where possible. Ask whether the original record supports the interpretation and whether another relevant source changes the context. Multiple pages repeating the same report should not automatically be counted as independent corroboration.
Record disagreements precisely. Two reviews may use different wording, examine different dates, or answer different questions. Compare those boundaries before declaring a contradiction. When sources genuinely conflict, preserve the conflict and explain what remains unresolved. Do not settle it by counting websites or asking an LLM to choose whichever explanation sounds more persuasive. A careful comparison is about evidence and scope, not the volume of repeated assertions.
Design automated discovery with a narrow promise
An automated system can help organize candidate reviews, extract metadata, and flag possible matches. Describe it as discovery unless it also performs and evaluates the assessment step. Keep a human-review path for ambiguous matches, changing claims, and excerpts whose context is difficult to preserve automatically.
Do not invent an endpoint or assume a public integration exists for a named publisher. Check current documentation and permitted access before building an integration. Respect the source’s access conditions and retain only the content your use permits. A link to a published review is not permission to reproduce an entire article. The safest technical contract is explicit about what it retrieves, what it stores, and what it asks the user to inspect directly.
Keep a compact review record
A useful record includes the incoming claim, the candidate review, the claim actually reviewed, the original rating, the publication or update information, and a note about the match. Add the source passages that matter and a conclusion limited to the new question. This structure gives another reviewer enough information to understand why the review was used.
Record an unresolved result when no sufficiently relevant review is found. Lack of a published fact check is not proof that a claim is true or false. It may simply mean the claim has not been reviewed, is hard to find, or falls outside the searched collection. Distinguish that outcome from a technical search failure. The difference determines whether the next step is broader research, a retry, or a request for more context.
Share the conclusion without losing its boundaries
When summarizing a review, keep the claim, date, and key limitation close to the conclusion. Avoid turning a nuanced analysis into a slogan that says more than the evidence establishes. Where the new statement differs materially from the reviewed one, describe the earlier review as relevant background rather than as a direct verdict on the new claim.
Use the online fact-checking guide for the review checklist and the structured fact-data guide for preserving source labels and assessment relationships. A responsible truth check does not borrow authority from a recognizable publisher’s name. It carries forward the actual reasoning, the exact claim, and the limits that make the original review intelligible.
