features · verification

Fact-checking and link verification

A draft you can’t trust costs more to review than it saved to write. So before a draft reaches you, the agent checks each claim against the source it cites, fixes or cuts what doesn’t hold up, and writes down what it found, link by link. That record ships with the draft.

What gets checked

Every URL in the post, external sources and links to your own pages alike, gets its own check. The agent works through them as small, separate checks, one per link and one per claim, never as a single skim of the finished text.

  • The link resolves. A dead page, a redirect to an unrelated page or a parked domain doesn’t count as a source, and a page that blocks the fetch is treated as unverified until the fact is found on one that doesn’t.
  • The page supports the claim. The same number, the same scope (US or global, this year or last), the same wording for a quote.
  • Your own links point somewhere real. Internal links come from the pages the site scan actually found, so the agent doesn’t guess paths that 404.
  • The metadata fits. Title and description lengths, slug, tags and target keyword are validated against the schema before the draft is saved.

What happens when a check fails

The fix happens at the claim, not just at the link. If a source died, the agent replaces it with a working one that supports the same claim, or cuts the claim. If a number moved, it corrects the number and anything calculated from it, or softens the sentence into an observation.

Its instructions rule out citing a URL from memory: every source in the post has to come from the research findings or from a page the agent fetched during the run.

The report you review

Each draft carries a link-verification report: one row per URL, with its type (external or internal), a status and the exact claim it backs. The status says what happened:

StatusMeaning
verifiedFetched, and the page supports the claim as written.
replacedThe original source failed and a working one took its place.
removedThe link was dropped and its claim cut or softened.

So reviewing a draft means reading the post and spot-checking the rows you care about, not opening thirty tabs. The report is part of every plan, the free one included.

How fresh the check is

Research and writing are separate phases. The deep dive fetches every source it records. When the post is written within a week of that research, each claim in the draft is cross-checked against those findings and the report says so. The writer still fetches your internal links, any source it added and the handful of figures the post leans on hardest, such as a number in the title. When the research is older, it fetches every source again before saving, because links die and figures change.

What it doesn’t do

A checked link proves the source says it. It doesn’t prove the source is right, and it can’t judge whether a claim fits your audience. That’s why the draft still waits for you: verification makes the review fast, it doesn’t replace it. See how the approval flow works.

The link checks are the agent’s own work. It follows written verification steps and reports what it did, and the app turns that report into the table above. The app validates the metadata itself, but it doesn’t re-fetch your links or hold a draft back over one, which is one more reason a row you doubt is worth opening.

It also checks at writing time. A source that changes after you publish isn’t re-checked on its own, so older posts still deserve a periodic look.

Read a verified draft of your own

Add your URL and review your first draft with its verification report. The first 3 posts are free.

Plant your first post