Editorial Policy
Clarivy treats public product claims and audit methodology pages as evidence-bearing content. This policy explains how we review public pages, correct errors, and keep AI-search visibility claims tied to visible evidence.
Content standards
- Product facts must match /llms.txt and the Methodology page.
- Claims about endpoints, pricing, delivery windows, and product status must be visible on the page where they are used.
- Historical artifacts must carry a visible historical warning when old pricing, endpoint counts, or matrices are preserved.
- Public pages do not use aggregate ratings, customer counts, certifications, or external profiles unless they exist and are approved for publication.
Fact-checking process
- Check product facts against /llms.txt.
- Check endpoint and methodology claims against /audit/methodology.html.
- Run the public trust test suite before deployment.
- Update sitemap `lastmod` when a public page materially changes.
Corrections
If a public page contains an incorrect product fact, pricing statement, endpoint list, or legal reference, we correct the page and update the visible version or last-updated line where the page uses one. For corrections, email [email protected].
Use of AI assistance
Clarivy may use AI assistance for drafting, summarizing, and consistency checks. Human review is required before public pages or customer-facing audit content ships. AI assistance does not replace the raw evidence links in an audit deliverable.
Audit report guardrails
- Every report claim must trace back to raw response evidence.
- Reports distinguish a missing result from a missing datapoint.
- Reports disclose endpoint stochasticity and do not forecast future rankings.
- Reports do not invent customer facts, citation URLs, or competitor rankings.