Evidence you can inspect
Each finding names the file, rule and excerpt. Markdown findings use source lines where available; HTML findings identify elements.
Use this tool Jump to inputs and settings
DOCUMENTATION · EVIDENCE BEFORE EDITINGFind the gaps.
Find the gaps.
Hand over a useful fix list.
Review your docs for unresolved links, missing headings, duplicate pages and conflicting limit statements. Turn the uploaded set into a clear audit and draft export package.
Free full findings previewUS$9 export packageNo subscription
Drafts you can own
Export normalized Markdown, navigation, findings in JSON/CSV, a printable HTML report and an llms.txt map. Review the drafts before publishing.
Your files stay local for preview
No AI request or public-URL crawl. Preparing checkout uploads the finished package for 30-day order recovery.
1. Choose your documentation
Ready when you are.
2. Review the evidence
Documents inspected
ZIP: audit.json, findings.csv, audit-review.html, navigation.md, llms.txt or llms-template.txt, and normalized Markdown drafts. Original assets are excluded.
What the audit checks
- Links and anchors that cannot be resolved within the uploaded set.
- Missing main headings, multiple H1s and skipped heading levels.
- Duplicate titles, exact repeated text and ambiguous published routes.
- Explicit update dates older than your chosen cutoff.
- Different “up to” values for common limits, flagged for manual context review.
What needs your judgment
A missing uploaded target may still exist online. Different limits may belong to different plans. Markdown renderer anchor rules may differ. External links are counted, not fetched. No result certifies factual accuracy, accessibility, search rankings or an AI assistant’s answer quality.
Markdown support includes common ATX/Setext headings, basic inline/reference links and fenced code. MDX, custom components and advanced syntax need manual review. HTML conversion extracts main/article content where present and drops scripts/styles; images become alt-text descriptions and complex layout may change.
From audit to a reviewed handover
- Upload the docs and inspect each finding with its source.
- Export the review package when the audit is useful.
- Resolve findings in your original documentation and rerun the audit.
- Review generated drafts and routes, then publish through your own system.
Without a docs-root URL, the package includes llms-template.txt linking to local drafts. With a docs-root, it includes proposed URLs that you must verify before publishing. This tool has no automatic hosting, article publishing or help-center integration.
Preview data stays in memory and is cleared when the page closes. Preparing checkout sends the package—including draft source content and excerpts—to the existing checkout storage. Avoid uploading material you do not have permission to process. Nothing is posted or sent to another person.