Crawl and classify
Find canonical pages, extractable sections, links, structured data, robots rules, sitemap, and `llms.txt` signals.
CiteAura treats crawlability, extractable facts, model answers, citations, and product-surface observations as different evidence streams. The result is a defined measurement, not a universal ranking claim.
Every visibility result keeps its provenance so teams can compare like with like and see what is still unmeasured.
The canonical domain, page set, rendered HTML, machine files, structured data, and official facts form the inspectable source layer.
Questions are grouped by intent, such as definition, comparison, recommendation, pricing, and problem diagnosis. Brand probes are kept separate from target questions.
Only configured and successfully sampled providers enter a measured cohort. Missing providers remain visible as unmeasured instead of becoming an implied zero.
API · Model knowledge, API · Web-grounded retrieval, and Manual · Product surface answer different questions and are never silently merged.
Before-and-after comparisons use a defined measurement period. Model updates, retrieval changes, and question changes are recorded as cohort changes.
Find canonical pages, extractable sections, links, structured data, robots rules, sitemap, and `llms.txt` signals.
Keep answer text, citations, provider, question ID, and mode so an aggregate can be traced back to its evidence.
Use deterministic page checks for technical work and a comparable re-sample for visibility work. A draft remains a draft until reviewed.
Interpretation boundary: a measured mention or citation is evidence for the defined cohort and period. It is not a promise about every user, model, region, or future answer.
No. API model knowledge, web-grounded retrieval, and manual product-surface observations stay separate.
The question set, provider cohort, model, sampling mode, market, and measurement period must be defined and comparable.
Because insufficient evidence is a result. The product exposes provider and sample coverage instead of estimating missing observations.
Read the operational steps in CiteAura measurement documentation, inspect the sample GEO diagnostic report, or review the AI visibility audit workflow.