What Citable observes
- HTTP status, redirect, header, robots, sitemap, canonical, hreflang, and link-discovery conditions exposed to the selected audit target.
- Declared desktop, mobile, JavaScript-disabled, or crawler-specific evidence only when those collectors are explicitly run.
- The exact target, configuration, tool version, and collection time attached to the run.
Evidence artifacts
- Run manifest and checksums
- Captured headers, robots.txt, and sitemap responses
- Link graph, findings.json, and report.md
- Optional render or crawler observations when their required collectors completed
What the observation cannot establish
- A successful fetch does not establish that a search engine or answer engine crawled, indexed, ranked, or cited the resource.
- A local build audit does not establish the state of a live deployment.
- Missing credentials, browser dependencies, logs, or owner exports leave the corresponding evidence incomplete.
Next operational step
Act on the bounded result
Resolve deterministic blockers first, preserve the source run, then repeat the same collection profile so the before-and-after observations remain comparable.