Editorial review workflow

Detect AI-written article

Review article drafts for AI-writing risk, provenance metadata, and editorial QA signals before publication.

Signal reportWatermark, provenance, and text-risk signals stay separate.
Post-Check loadingDetector assets load only after a user starts analysis.
No proof claimsUnknown and unsupported states are first-class results.

Run a signal check

No detector model loads until you press Check.

0 chars

Current support

Article checks combine text features, optional advanced local model checks, and saved reports for editorial triage.

Partially supported

What this checks

  • Longer article excerpts usually produce more useful text feature signals than short snippets.
  • Saved reports can preserve detector versions and limitations for an editorial review trail.
  • Bulk mode is available for reviewing multiple article excerpts in one job.

What this does not prove

  • Formal human writing can resemble AI-generated text.
  • Human-edited AI drafts may produce mixed signals.
  • Editorial decisions should include drafts, notes, and source history.

FAQ

  • Can this prove whether content was written by AI?

    No. AI Detect reports signals such as provenance metadata, watermark support status, and statistical text risk. It does not claim legal or authorship proof.

  • Does text leave my browser during a local check?

    Browser-default checks run local text features and provenance checks after you press Check. Server enhanced checks are separate and will be labelled before use.

  • Why can a result be unknown?

    Many providers do not expose public watermark detectors, and metadata can be absent or stripped. Unknown is a valid result when no reliable public signal exists.

Workflow upgrade

Need repeatable reviews?

Move from one-off checks to saved reports, batch review, and API-ready signal records when the workflow needs it.

Related checks