The evidence pipeline exists.
Prompt, run, citation, snapshot, account-summary, scoring, and alert-draft paths are implemented in the repository.
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.
Every displayed rate has a traceable denominator: the finite prompts actually evaluated in a stored run.
Sampled, not ranked.
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.
Revvye separates configuration, execution, parsing, and comparison so every alert can be traced back to the answer that caused it.
A business, market, locale, and competitor context defines the prompts. The prompt set is visible evidence, not a hidden keyword universe.
The engine adapter uses live web search, stores the returned answer, and does not force the target business into unsupported results.
Target mentions, competitor presence, position, sentiment notes, and native citations are derived from that returned answer.
Alert drafts require current and prior snapshots with enough evaluated prompts; a single response is never presented as market truth.
The platform foundation and the commercial promise are deliberately separate. Runtime configuration and real customer evidence decide when monitoring can be called operational.
Prompt, run, citation, snapshot, account-summary, scoring, and alert-draft paths are implemented in the repository.
Scheduled prompt runs require an explicit enable flag, authenticated dispatch, a per-sweep cap, a daily budget, and a minimum run interval.
Revvye does not promise inclusion, rank, citation, answer stability, or unattended monitoring until the runtime is enabled and observed.
Start with crawl access, structure, buyer-path, trust, mobile, and conversion evidence from one public URL.
Open the scanner →Use the live checker when the immediate question is whether named agents are declared allowed or blocked.
Open the live checker →Define the finite question set, competitors, cadence, operating limits, and the human review boundary.
Review the service →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.
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.
Test the deterministic public surfaces before interpreting a sampled answer. It keeps a fixable access declaration separate from a variable model response.
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.
A useful prompt set is small, specific, and drawn from how buyers actually speak. Four families cover most of it:
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.
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.
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.
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.
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.
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.
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.