AI source analysis · returned context

Trace returned sources without claiming an exhaustive index.

Review sources, search results, Top Pages, and Top Domains only where the selected LLM Mentions operation returns them. A returned source is evidence for that result; an absent source is not proof of exclusion.

Start free trial AI visibility hub

Direct answer

Match the evidence to the decision.

Keep the selected provider, target, operation, locale, and returned fields attached to every interpretation.

Supported workflow

Inspect this evidence question step by step.

Distinguish sources from search results.

A cited source domain and a domain appearing in related search results are different returned fields. Preserve that distinction in analysis and reporting.

Move from domains to pages carefully.

Top Domains helps orient domain-level source evidence, while Top Pages can narrow the view to returned pages. Neither is an exhaustive crawl or citation index.

Use source evidence to form the next question.

A repeated source may justify a content or technical investigation, but the returned record alone does not establish causation or guarantee future citation.

Keep the evidence boundary visible.

Record the provider, target, operation, location, language, and returned fields. The result is bounded evidence—not a guarantee, attribution model, exhaustive index, or automatic optimization outcome.

Related evidence

Continue with the operation that answers the next question.

Keep the product boundary explicit.

Does a missing source mean the model never uses it?

No. Absence from a bounded result is not proof of universal absence.

Does source analysis crawl every answer?

No. It describes fields returned by supported operation contracts.

Continue the workflow

Inspect a real evidence question in Gavix.

Start free trial