How Citevera works

Every audit runs the same four-stage pipeline. Total wall time per scan is 30 - 90 seconds.

1. 1
   Crawl

   We fetch robots.txt, sitemap.xml, llms.txt, and the homepage, then pick up to 9 additional internal pages (product, pricing, docs, blog, about, FAQ, how-to) based on your sitemap structure. Each page is rendered with headless Chromium at a 10-second timeout and 5MB response cap.

2. 2
   Classify

   A Claude Haiku pass identifies each page's type and extracts structured facts - visible CTAs, FAQ blocks, price points, stats with sources, and JSON-LD types. Prompt cached, budget under $0.03 per scan.

3. 3
   Audit

   Claude Sonnet 4.6 runs the full 35-point AI search readiness checklist against the classified page data. System prompt is the entire ai-seo skill (prompt cached), which covers AEO, GEO, and crawlability patterns that currently get cited by AI answer engines. Output is a strict JSON report with a score, axis scores, audit items, generated fix artifacts, and a priority plan.

4. 4
   Render

   The report is validated against a strict Zod schema (schema-violation reports are retried, not returned), typography is normalized, and the result is stored and rendered on scan.citevera.com/r/[id]. Paid reports also get a PDF export.