Verify your help center articles
Verification reads every published article, checks each claim against your connected product sources, and flags sentences that no longer match your product. Fern drafts the fix for you to review and publish. Open Verification from the dashboard sidebar to start.
Verification is included in the Pro and Enterprise plans. If your workspace doesn't include it, the Verification page shows an Upgrade to Pro button.
Before you start
Fern verifies articles against the sources connected to your workspace: your codebase, your website, API references, and support tickets. The more sources she can read, the more of your docs she can verify. Connecting your codebase is the one the verification wizard recommends most.
Run a verification
Start a full pass from the Verification page. You can also get there from the Find your outdated docs item on the onboarding checklist.
Open Verification from the dashboard sidebar.
Click Verify docs.
Choose what Fern checks. Pick Verify what needs it for articles that are due, changed, or not yet verified, or Re-verify everything for all published articles, even ones verified recently. This step only appears when some articles are already verified.
Review your sources. Connected integrations show as Connected, and Connect another source opens your integrations settings. If nothing is connected yet, the button reads Connect a source.
Check the summary on the Ready to verify screen, then click Start verification.
You'll see a confirmation that verification started, and you get an email when the run finishes.
Read the results
The Verification page groups every published article into four tabs:
Needs review: articles with claims that no longer match your product
Up to date: articles Fern checked and found accurate
Can't verify: articles Fern couldn't check because she couldn't establish a comparison: no connected source covers them, a source couldn't be reached, a check didn't finish, or the article isn't published on the configured website
Activity: the history of your verification runs
Fix an article Fern flagged
Open an article in Needs review. The What's wrong list shows each outdated claim with the quoted article text, Fern's suggested fix, and supporting evidence when she has it.
Click Draft the fix. Fern rewrites the flagged sentences and the draft appears in the same view.
Review the draft and edit it as needed.
Click Publish changes to update the article.
If Fern got it wrong, click Not an issue and she won't flag it again.
Verify a single article
Default-language articles show a Verification panel in the article editor. Click Verify this article to check just that article, or Verify again to re-run it. The panel lists each claim with its evidence, lets you dismiss claims that aren't actually wrong, offers Draft fix with Fern, and keeps the article's verification history.
What Can't verify means
Fern marks an article as Can't verify when she couldn't establish a comparison: no connected source covers its claims, a source couldn't be reached, a check didn't finish, or the article isn't published on the configured website. When coverage is the issue, connect another source and run verification again; articles she can then check move into a checked state or into Needs review.
Verification freshness
Verification results stay fresh for 30 days. After that, an article counts as due for another check, and Verify what needs it picks it up on the next run.
Turn on Continuous verification
Continuous verification re-checks published articles against your codebase and website on a rolling schedule, so every article stays verified. It's included in the Pro, Scale, and Enterprise plans and is off until you enable it.
Open Settings from the dashboard sidebar and select Automations.
Turn on Continuous verification.
Fern then works through your published articles in batches, comparing each claim against the sources she can reach. Use Verify all articles now on the same card to start a run immediately. You get an email whenever a run turns up articles that drifted.
Verification emails
When a run finishes, every active workspace member gets a summary email with how many articles were checked, how many were verified, and how many need fixes. The email includes a See the verification report link back to the Verification page. Scheduled runs only email you when at least one article has outdated claims; a clean scheduled run stays silent.