How to fact-check news articles on Chrome with an AI fact-checker browser extension.
Start with one suspicious article claim, keep the wording close to the page, run a FactSentinel first pass, then inspect sources before you share, cite, edit, teach, or publish.
Do not start by checking the whole article.
Articles often mix facts, interpretation, quotes, background, and speculation. A practical browser workflow starts with one claim that can be checked: a number, quote, attribution, policy statement, source claim, or causal assertion.
1. Find the claim
Highlight the exact sentence that carries the factual burden. Keep names, dates, numbers, source labels, and nearby context.
2. Run FactSentinel
Use the extension or web checker to review verdict, confidence, model agreement, reasoning, caveats, and sources.
3. Inspect sources
Open the source links and ask whether they support the exact wording, not just the general topic.
Article claims worth checking first.
The best first checks are concrete enough that a reader can inspect evidence without becoming a full-time researcher.
Statistics
- Percent changes and rankings.
- Polls, counts, and totals.
- Claims sourced to unnamed reports.
Attributions
- Quotes from named people.
- Claims about official statements.
- Source labels such as "experts say".
High-risk context
- Medical, legal, or financial claims.
- Breaking-news casualty or damage claims.
- AI-generated summaries of articles.
What a useful first pass should show.
The result should give you enough structure to decide whether to trust, slow down, or escalate. A one-word answer is not enough when the article will be shared or cited.
Evidence
- Source links attached to the claim.
- Caveats when context is thin.
- Reasoning that can be challenged.
Model signal
- Verdict and confidence.
- Agreement or disagreement.
- Reasons to inspect manually.
Next action
- Open primary sources.
- Check whether wording shifted.
- Verify AI-generated sources on Chrome.
Keep the install path measurable.
Weekly metrics showed that install and first-success activation events need clearer paths. This page sends install-intent readers through `/download` first, so download clicks, Chrome Web Store handoffs, and successful checks can be reviewed together.
Download step
Use the download page as the measurable site step before the browser-store handoff.
First-success step
Run one meaningful article-claim check so the install has an immediate verification moment.
Return step
Use the extension again when a headline, statistic, source, or quote needs a source trail.
Install, then check one article claim.
Open the download page, install the Chrome extension, and run a first-success check on one claim from a news article you already have open.