The AI Visibility ReportCloud
The Report tab on a brand page is the single source of truth for what AI engines are saying about your brand. One Run Check, one report, three result families — never blended into one number.
One Run Check
Every brand page has one customer-facing trigger: Run Check, in the brand header. You don't pick engines, you don't pick surfaces. The check runs across the engines configured for the brand, generates a single unified report, and writes it to the Report tab.
While the check runs, the button reads Checking… and a progress card under the brand header shows live status. The Report tab continues to show the last completed report; when the new run finishes the tab reloads automatically.
Visibility by surface
The report separates results into three output types. They're shown as three cards across the top of the tab. AI engines often disagree across these types — the same brand can be #1 in ChatGPT's AI app and missing from its Agent Search Visibility results for the same query. Blending them hides that signal, so we never do.
AI Visibility
What real people see when they open ChatGPT, Gemini, Perplexity, Claude, or Grok and ask about your category.
Best barber in Almere → ChatGPT surfaces Barber Sadka at #1 with a local-pack module.
Agent Search Visibility
What programmatic queries and search-grounded calls return. This is where AI agents, integrations, and embedded search experiences read from.
Best barber in Almere → Gemini Agent Search Visibility returns competitor brands; your brand is missing.
Local & Maps
What Maps-grounded AI answers return for location-intent questions about your brand.
Gemini Maps grounding (Almere) → ranks Barber Sadka at #1 even when Gemini Agent Search Visibility misses it.
Each card has a status chip: Measured, Partial, Awaiting data, or Blocked. Below the status are the headline (e.g. "Mentioned in 2 of 2 reporting engines"), a per-engine pill strip, and metrics (presence rate, avg rank, citations, stability).
Focus recommendation
What to prioritize for this brand, this run.
Sits directly under the report headline. Server-supplied, grounded in the brand's segment, target locations, and actual run results. The confidence chip (high / medium / low) reflects how much evidence the recommendation is built on — hover for an interpretation.
Each focus card carries: a headline (the one thing to focus on), the rationale, a Based on evidence list, one or two suggested Next actions, and explicit Watchouts — typical misreads to avoid.
Confidence rises naturally as you accumulate more runs and observations for a brand. Low-confidence reports still ship — they're framed as starting hypotheses, not verdicts.
Per-engine drill-down
Below the surface family cards, each engine gets one collapsible row summarizing how it handled the run — across every surface it reported on. Click a row to expand.
- Collapsed row shows the engine label, result count, and a presence pill per result type ( AI Visibility · mentioned, Agent Search Visibility · absent, etc.).
- Expanded view shows each prompt the engine answered, what the brand's presence looked like (mentioned, rank, mention type), the top results the engine returned, citation sources, and a short "What we saw" interpretation.
- An Evidence details expander on each prompt row carries observation-level references. It stays collapsed by default so support detail never becomes the lede.
Source readiness
The inputs AI engines read from when they answer about your category.
Source readiness is an explanatory layer, not a peer result family. It tells you why a brand may or may not surface — the result family cards above remain the source of truth for what AI actually showed.
Local Entity
PreviewGoogle Business Profile, Maps, reviews, NAP consistency.
External Authority
Measured (when available)Reddit, listicles, YouTube, comparison pages — the third-party sources engines cite.
Owned Content
PreviewService pages, FAQs, comparison and case-study content on your own domain.
Technical AI
PreviewSchema, sitemaps, llms.txt where supported, MCP/docs surfaces.
Layers marked Preview describe what the layer will track once it's measured for your brand. As observations accumulate, the status moves to Measured with a summary count.
Caveats and limitations
When a run can't deliver every stage of the report, the tab shows a caveats section near the bottom. Each caveat carries: a customer-safe message, a severity icon, and the affected surface family.
Example: "Agent Search Visibility results are not available for this run."
Affects: Agent Search Visibility
Caveats are designed to be agency-readable. Internal trace identifiers are kept off-screen (available on hover for support), so you can show the report to a customer without seeing runtime messages.
What the report does not do
- No blended score. The surface families disagree on purpose; collapsing them would erase the most useful signal. The score ring on the brand-detail header is the legacy organic V2 score, not the Report.
- No auto-fix. Fix actions are surfaced as recommendations and (where supported) workflow-backed drafts that require human approval. The Report tells you what to look at; the Improve tab is where you act.
- No exposure of mechanism. How S6S captures live results is an internal concern. The Report shows what AI surfaces returned, not how they were observed.
See it on your own brand
Run a free public audit, or add a brand to start tracking the Report tab over time.