DIY BUILD GUIDE
Build a content evidence audit
Extract page structure, entities, claims, and sources; map them to prompts; then report page-specific evidence gaps.
Prerequisites
- A page list and a small, versioned prompt set.
- Permission to fetch the pages you audit.
- A place to review source and claim evidence with a human editor.
Minimum architecture
Target pages and prompts -> extraction -> prompt mapping -> evidence-gap report.
Implementation steps
- Extract headings, entities, claims, and cited sources from each page.
- Map each prompt to its intended page and evidence.
- Publish page-specific gaps for editorial review instead of a composite score.
Output
A page-by-page evidence-gap report linking prompts, claims, sources, and missing corroboration.
Runtime and cost
Software: Your own code and hosting
Runtime: Crawling, extraction, and storage costs.
Data location: Your chosen storage and report output.
Validate before relying on it
- Check extracted claims.
- Review source mapping.
- Validate page-specific gaps.
Boundary
It finds gaps but cannot create original facts or corroboration.
Follow this build content evidence audit guide to keep costs, validation, and limits visible.