Quick answer
An AI visibility dashboard should be read as a triage surface, not as proof that the program is working.
Start with five questions:
- What prompt, platform, country, competitor, and date filters are active?
- How many prompts were measured?
- How many responses were collected?
- How often was the brand visibly mentioned?
- Which sources, competitors, and raw answers explain the result?
The mistake is jumping from a home-tab number to a strategy. A dashboard can show activity and presence, but it cannot prove trust, preference, citation quality, or commercial progress until the team reads the underlying answers and assigns work.
For ReachLLM teams, use this order:
- Lock the scope.
- Check prompt coverage and response count.
- Read presence beside rank, sentiment, citation rate, and Share of Voice.
- Open source and competitor evidence.
- Separate measurement hygiene from content, website, technical, PR, or brand-data work.
- Ship one fix.
- Re-measure the same prompt group.
The dashboard tells you where to look. The raw evidence tells you what to do.
What a home dashboard can tell you
The scheduled Scrunch source for this article explains its Home tab as the central place for monitoring how a brand and its competitors appear across AI assistants. It defines early dashboard metrics such as prompts, responses, and presence, and notes that the dashboard may be filtered to non-branded prompts by default.
That is a useful shape for AI visibility review. Before a team discusses trend lines, opportunities, or recommendations, it needs to know what was actually measured.
| Dashboard signal | Useful question | Risk if read alone |
|---|---|---|
| Prompts | Which questions are included in the current filter? | The count may exclude branded prompts, archived prompts, or another segment. |
| Responses | How many AI answers were collected for those prompts? | Failed, skipped, or no-trigger runs can distort the denominator. |
| Presence | Did the brand appear in the visible answer text? | A mention is not automatically a recommendation. |
| Competitors | Who else appears in the same answer set? | The wrong comparison group can make the share look better or worse. |
| Sources | Which pages or domains support the answer? | A cited source may not support the claim the dashboard implies. |
| Trends | Is movement happening over time? | Movement can come from scope changes, freshness, or model variance. |
The first job is not interpretation. It is labeling.
If the dashboard says presence is up, write the scope in plain English: "Unbranded US comparison prompts, ChatGPT and Perplexity, seven-day window, direct competitors only." Without that sentence, the metric is too vague to operate.
Start with filters before metrics
Filters decide what the dashboard means.
Before reviewing a home screen, confirm:
| Filter | Why it matters |
|---|---|
| Prompt type | Branded prompts test entity accuracy; unbranded prompts test discovery. |
| Platform | ChatGPT, Gemini, Perplexity, Claude, Copilot, Meta AI, and Google AI features can surface different sources. |
| Country or market | Local proof, language, and source availability can change the answer. |
| Date range | Daily monitoring and monthly reporting answer different questions. |
| Competitor group | Share of Voice and gap analysis depend on which entities are in the denominator. |
| Topic tags | A strong overall view can hide weak performance in one buying theme. |
Scrunch's public help article notes that its Home dashboard is filtered to non-branded prompts by default. That is not a bad default. It may be exactly what a growth team needs. But it means the home count should not be compared casually with a broader prompts tab or an all-prompts export.
ReachLLM follows the same discipline in its own score documentation. Brand Visibility uses selected direct competitors by default for Share of Voice, rank, trends, the comparison matrix, prompt gaps, and generated reports. It also keeps raw responses and source evidence visible so a team can trace the metric back to the answer.
If the filter changed, start a new baseline. Do not explain the new number as performance.
Separate collection from visibility
Prompts and responses are collection metrics. Presence is a visibility metric.
They should be read in this order:
| Step | Check | Decision |
|---|---|---|
| Prompt count | Did the expected prompt set run? | If not, fix prompt setup before reporting visibility. |
| Response count | Did the expected platforms return usable answers? | If not, label missing data before calculating trends. |
| Presence | Did the brand appear in those answers? | If yes, inspect rank, sentiment, and source support. |
| Citation rate | Did the AI answer cite the brand's own domain? | If no, review owned pages and third-party source paths. |
| Competitor appearances | Which competitors appeared in the same answer set? | If competitors dominate, classify the source gap. |
This matters because a team can have high activity and weak visibility. One hundred prompts and four hundred collected responses may still show poor presence if AI assistants do not name the brand. The reverse can also happen: a small prompt set may look strong because it contains mostly branded or low-competition questions.
The dashboard should make that distinction obvious. If it does not, add the explanation to the reporting note.
Presence is the starting point, not the conclusion
Presence answers a narrow question: was the brand explicitly mentioned in the answer?
That is useful because it reflects what a user can actually see. It is also incomplete.
Use these paired checks:
| Presence pattern | What to inspect next | Possible fix |
|---|---|---|
| Brand present, ranked late | Average Rank and raw answer order | Strengthen differentiation and comparison proof. |
| Brand present, sentiment neutral | Sentiment drivers and cited pages | Add clearer positioning, proof, and current claims. |
| Brand present, own site not cited | Citation rate and source list | Improve answer-first owned pages, schema, internal links, and llms.txt. |
| Brand absent, competitors present | Gap Analysis and competitor sources | Improve the relevant page or pursue legitimate third-party source inclusion. |
| Brand absent, no competitors present | Prompt intent and answer quality | Reclassify or rewrite the prompt before assigning content work. |
| Brand present only on branded prompts | Prompt grouping | Invest in unbranded discovery and comparison prompts. |
This is where dashboards often create bad behavior. A team sees a low presence number and decides to publish more articles. Sometimes that is right. Often the fix is narrower: update one product page, correct an entity fact, add a comparison section, repair crawlability, refresh docs, or pursue one publication that AI systems already cite.
Google's AI feature guidance is a useful technical guardrail. Google says AI Overviews and AI Mode use Search systems and that site owners should keep content crawlable, indexable, useful, text-accessible, and aligned with structured data when used. There is no special schema or AI text file required to appear, and eligibility is not guaranteed.
That means presence work is still evidence work. The model needs accessible, trusted, useful source material.
Use sources to classify the work
Source evidence turns dashboard review into a work queue.
Do not ask "how do we improve the score?" first. Ask "what source path is shaping the answer?"
| Source pattern | What it usually means | First useful action |
|---|---|---|
| Own domain cited and brand present | The page is findable and relevant. | Improve rank, proof, and conversion clarity. |
| Own domain cited but brand absent | The page answers the topic without connecting it to the company. | Add product context and internal links. |
| Brand mentioned but own domain absent | Third-party sources may be carrying entity knowledge. | Strengthen owned evidence and verify external profiles. |
| Competitor pages cited | A rival owns the explanatory source. | Create original, better evidence instead of paraphrasing. |
| Review or directory sites cited | Entity facts and third-party proof matter. | Correct profiles and pursue legitimate reviews. |
| Industry publications cited | Earned authority shapes recommendations. | Pitch a real story, data point, or expert contribution. |
| Forum threads cited | Natural-language user discussion is influencing answers. | Participate helpfully; do not manufacture mentions. |
ReachLLM's Sources and Opportunities workflow is designed for this step. It lets teams review cited domains and URLs, source categories, competitor overlap, source history, and prompt-level gaps. The useful output is specific: "This prompt cites these two competitor-friendly sources; our pricing page lacks the comparison proof; product marketing owns the update; PR owns one legitimate external source."
That is a decision. "Improve AI visibility" is not.
Convert the home tab into a 30-minute triage
Use this review when an AI visibility dashboard is the first screen in a weekly meeting.
| Minute | Step |
|---|---|
| 0-5 | Confirm filters: prompts, platform, country, date range, competitors, topics, and branded versus unbranded scope. |
| 5-10 | Compare prompt count with response count and label missing or failed data. |
| 10-15 | Review presence beside Visibility Score, Share of Voice, Average Rank, sentiment, and citation rate. |
| 15-20 | Open raw answers for the highest-intent win, loss, and zero-presence prompt. |
| 20-25 | Classify the gap as prompt hygiene, owned content, website, technical, source, PR, sentiment, or brand data. |
| 25-30 | Assign one fix, name the owner, and set the re-measurement date. |
The review note should look like this:
| Field | Example |
|---|---|
| Scope | Non-branded US vendor-comparison prompts, ChatGPT and Perplexity, September 1-4. |
| Movement | Presence fell from 42 percent to 35 percent. |
| Evidence | Two high-intent prompts now cite competitor comparison pages. |
| Fix | Update the agency comparison page and add source-backed proof. |
| Owner | Product marketing for page copy, PR for one legitimate source action. |
| Re-check | Same prompt group after the next scheduled run. |
The format is intentionally small. If a home dashboard creates 20 tasks, the team has skipped triage.
When the dashboard should trigger an agent
Automation belongs after the team knows what the dashboard signal means.
Good agent tasks include:
- Pull the raw responses behind a presence drop.
- List the cited sources for competitor-only answers.
- Draft a page-improvement brief for human review.
- Compare the prompt set against the current buyer journey.
- Summarize sentiment drivers with answer evidence.
- Draft schema,
llms.txt, or page-copy changes for review.
Bad agent tasks include:
- Publishing pages from every missing prompt.
- Rewriting competitor documentation.
- Sending outreach without review.
- Treating one answer as a trend.
- Changing competitors or aliases silently to improve the chart.
- Claiming that one technical file guarantees AI citations.
Google's people-first content guidance is the editorial boundary. If content draws on other sources, it should add original value rather than simply copy or rewrite them. In dashboard work, the original value is the decision system: scope, evidence, owner, fix, and re-measurement.
Where ReachLLM fits
ReachLLM is built for teams that need measurement connected to execution.
The platform tracks prompts across enabled AI systems, analyzes brand and competitor mentions, calculates Visibility Score, Share of Voice, Average Rank, sentiment, citation rate, source evidence, query fanout, and raw responses, then connects those findings to GEO audits, content, page rewrites, structured data, llms.txt, PR outreach, integrations, and agent workflows.
The dashboard is not the deliverable. The deliverable is a shipped fix tied to a prompt, source, page, and next measurement.
FAQ
What is an AI visibility dashboard?
An AI visibility dashboard shows how a brand appears across AI-generated answers. A useful dashboard connects prompt scope, response count, brand presence, competitors, sources, sentiment, rank, citations, and raw answers so the team can decide what to fix next.
What should teams check first in an AI visibility dashboard?
Check filters first: prompt type, platform, country, date range, competitor group, and topic scope. Without that context, metrics like presence, Share of Voice, and trends can be misread.
Is brand presence the same as being recommended?
No. Presence usually means the brand was explicitly mentioned in an AI answer. A recommendation also depends on answer wording, rank, sentiment, source support, competitor context, and whether the mention helps the buyer choose.
Why can dashboard prompt counts differ from response counts?
Prompt count reflects the questions in scope. Response count reflects usable AI answers collected for those prompts and platforms. Differences can come from filters, failed runs, no-trigger results, platform coverage, or date scope.
How does ReachLLM turn dashboard metrics into action?
ReachLLM keeps prompt-level evidence, raw answers, competitors, sources, scores, sentiment, query fanout, and GEO audit findings visible, then helps teams ship content, page updates, schema, llms.txt, PR outreach, and follow-up measurement.
Sources reviewed
- Scrunch AI Help Center, "Understanding the Home tab," scheduled source for this article: https://helpcenter.scrunchai.com/en/articles/11971751-understanding-the-home-tab
- Scrunch AI, public product overview: https://scrunch.com/
- ReachLLM Docs, "Understanding Your Dashboard": https://docs.reachllm.com/getting-started/dashboard/
- ReachLLM Docs, "Understanding the Scores": https://docs.reachllm.com/guides/understanding-the-scores/
- ReachLLM Platform page: https://www.reachllm.com/platform
- Google Search Central, "AI features and your website": https://developers.google.com/search/docs/appearance/ai-features
- Google Search Central, "Creating helpful, reliable, people-first content": https://developers.google.com/search/docs/fundamentals/creating-helpful-content