AI answer evidence

Track what an AI answer can prove.

Revvye connects a finite prompt set to answer runs, cited sources, comparable snapshots, and guarded alerts—without pretending an AI answer is a stable ranking.

Public pages only. The $97 report comes after the result.

Source-backed recordsExecution disabled by defaultScope the operated service
Revenue Guard · evidence schemaguarded runtime
Evidence.

Every displayed rate has a traceable denominator: the finite prompts actually evaluated in a stored run.

  1. 01Prompt recordconfigured
  2. 02Answer runobserved
  3. 03Citation rowattributed
  4. 04Comparable snapshotsampled
prompt → run → citation → snapshotfail-closed scheduler

Sampled, not ranked.

The measurement doctrine

An answer is an observation, not a position.

Model updates, live sources, and generation variance can change an answer. A fixed question set makes the change inspectable; it does not turn the output into a universal score.

Operating protocol

The evidence trail is the product.

Revvye separates configuration, execution, parsing, and comparison so every alert can be traced back to the answer that caused it.

  1. 01
    Lock a finite question set

    A business, market, locale, and competitor context defines the prompts. The prompt set is visible evidence, not a hidden keyword universe.

    input
  2. 02
    Record one answer at a time

    The engine adapter uses live web search, stores the returned answer, and does not force the target business into unsupported results.

    run
  3. 03
    Parse mentions and sources

    Target mentions, competitor presence, position, sentiment notes, and native citations are derived from that returned answer.

    evidence
  4. 04
    Compare only like-for-like samples

    Alert drafts require current and prior snapshots with enough evaluated prompts; a single response is never presented as market truth.

    decision
Current operating boundary

Built. Guarded. Not overclaimed.

The platform foundation and the commercial promise are deliberately separate. Runtime configuration and real customer evidence decide when monitoring can be called operational.

01 · Shipped core

The evidence pipeline exists.

Prompt, run, citation, snapshot, account-summary, scoring, and alert-draft paths are implemented in the repository.

02 · Guarded execution

Sweeps fail closed.

Scheduled prompt runs require an explicit enable flag, authenticated dispatch, a per-sweep cap, a daily budget, and a minimum run interval.

03 · Not promised

No guaranteed placement.

Revvye does not promise inclusion, rank, citation, answer stability, or unattended monitoring until the runtime is enabled and observed.

Choose the narrowest useful next step

Start where the evidence is missing.

01 · baseline

Run the public scan

Start with crawl access, structure, buyer-path, trust, mobile, and conversion evidence from one public URL.

Open the scanner
02 · narrow check

Read crawler directives

Use the live checker when the immediate question is whether named agents are declared allowed or blocked.

Open the live checker
03 · operated service

Scope prompt monitoring

Define the finite question set, competitors, cadence, operating limits, and the human review boundary.

Review the service
How AI visibility is measured

AI search visibility, and why rank tracking does not describe it

In ranked search there is one result list and a position in it. In AI search the answer is assembled per question, per user, and cites a handful of sources chosen for how usable they were. Visibility becomes a question about three separate layers, and only the first two are fully under your control.

04 field notes05 decisions
01

Three layers, in the order they bind

Whether an assistant mentions your business decomposes into three questions. They are strictly ordered — no amount of work at layer three compensates for a failure at layer one.

  • Access. Do the public directives tested by Revvye allow the named agents? The live tool evaluates robots.txt, homepage meta directives, and response headers; agent-specific firewall behavior requires separate inspection.
  • Legibility. Once fetched, do your pages state anything an assistant can extract and repeat — a business type, a location, services, prices, hours — in a form that survives being read by a machine? Largely a structured-data and markup question.
  • Mention. For the questions your buyers actually ask, does the assistant name you? This depends on the first two, on how much of the wider web corroborates what your site claims, and on the model's own behaviour, which changes without notice.

Test the deterministic public surfaces before interpreting a sampled answer. It keeps a fixable access declaration separate from a variable model response.

02

Why rank tracking does not transfer

A rank tracker works because a query returns a stable, ordered list that is roughly the same for everyone. AI answers have none of those properties. Two people asking the same question in the same minute can get different answers with different citations. The same question asked twice can vary. There is no position to occupy.

What can be measured is presence across a defined set of questions, sampled over time. You choose the questions that matter to your business, ask them repeatedly, and record whether you appear, who appears instead, and whether the assistant links to a source. That is a different instrument from a rank tracker and it should be read differently — as a trend across many samples, not as a number.

03

Choosing the questions worth tracking

A useful prompt set is small, specific, and drawn from how buyers actually speak. Four families cover most of it:

  • Branded — questions that name you directly. If an assistant cannot answer 'what does [your business] do', nothing else will work.
  • Category — the service plus the qualifier a buyer would use, with no brand attached. This is where you either appear or a competitor does.
  • Local — the same category questions with a place attached, which is where most service businesses actually compete.
  • Comparison — you against a named alternative. These surface how the assistant characterises you, which is often more revealing than whether you are listed.

A small, documented question set tracked consistently is easier to compare than a sprawling set that changes between runs. The point is to inspect change, not imply universal coverage.

04

What is measurable and what is not

The public directive and page-structure layers are inspectable from outside, within the limits of a successful fetch. The free tools report the exact surfaces they retrieved and expose limited or failed states rather than inferring a clean result.

Layer three is sampled rather than ranked. An assistant's answer is a generated response influenced by sources and system behavior an external tool does not control. Revvye can calculate rates from an evaluated prompt set, but the denominator and run evidence must remain visible. The rate describes that sample, not the whole market.

Inspect the repeatable public surfaces before paying to sample variable answers. Mention monitoring is an ongoing operating cost, and its value depends on a stable question set and preserved run evidence.

Q/A

Common questions

01How do I track whether ChatGPT mentions my brand?

By sampling: choose a fixed set of questions, preserve the locale and context, record each returned answer and citation, and compare like-for-like runs. The result describes those evaluated prompts, not a universal ranking.

02Is AI visibility the same as SEO?

They share foundations — crawlability, clear structure, factual specificity — but differ in target. SEO optimises for a position in a list of links. AI visibility optimises for being the source an assistant chooses to quote when it composes an answer.

03Why do I get a different answer every time I ask?

Generated answers may vary with sources, context, and system behavior. That is why one run is weak evidence and why comparable runs must preserve the question, locale, engine, model, citations, and completion time.

04What should I fix first?

Start with the public access and page-structure evidence because those surfaces are directly inspectable. Then define a finite prompt set and sample answers only when the question, market, and review boundary are clear.

05Can I do this without a paid tool?

The first two layers, entirely — the crawler and citation checkers are free and need no account. Sampling mentions by hand also works: ask your questions in ChatGPT and Perplexity, and keep a dated note of what came back. It is tedious, not impossible, and it is a reasonable way to find out whether the problem is worth paying to monitor.

Continue the investigation

Keep the evidence moving.

01AI Crawler Access CheckerLayer one, checked live against your domain in seconds.02AI Citation Readiness CheckerLayer two — the structured data and metadata that make a page quotable.03Run the full free scanAll 43 published checks across 8 categories before private result delivery.