> ## Documentation Index
> Fetch the complete documentation index at: https://docs.haloxlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GEO Dashboard: read AI visibility and site readiness

> The GEO Dashboard is the starting point for reading AI visibility, citation health and site readiness before choosing weekly priorities.

<Frame>
  <img src="https://mintcdn.com/afterworklab/5NGf7Fi0rCLZYAc3/images/concepts/page-thumbnails/en-features-geo-dashboard.png?fit=max&auto=format&n=5NGf7Fi0rCLZYAc3&q=85&s=e3a73f973ab43943c6fd5c344a4cdb59" alt="HaloX Features page thumbnail summarizing GEO Dashboard: GEO Dashboard: read AI visibility and site readiness as five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-features-geo-dashboard.png" />
</Frame>

## What is this feature?

**GEO Dashboard** is the starting point for reading AI visibility, citation health and site readiness before choosing weekly priorities. It is a decision point in the HaloX `diagnose → measure → prioritize → execute → report` loop. Teams use it to read the current signal, split the cause, and decide the next content, source, technical, or reporting action.

## HaloX app location

<Frame>
  <img src="https://mintcdn.com/afterworklab/d6Yws9vshM0o3jB7/images/app/geo-dashboard-kpi-actions-live-20260505.png?fit=max&auto=format&n=d6Yws9vshM0o3jB7&q=85&s=fb4a4f3c913b94cdf1f26bdb10647d4e" alt="HaloX dashboard showing AVI, search and citation scores with keyword health status" width="870" height="695" data-path="images/app/geo-dashboard-kpi-actions-live-20260505.png" />
</Frame>

*HaloX dashboard showing AVI, search and citation scores with keyword health status*

The dashboard is the starting point for both Lite and Pro mode. Lite is enough for a quick status read. Use the Pro sidebar when you need cause analysis, execution planning and reporting evidence.

## Inputs and outputs

| Area    | What it includes                                                               | Example                                                                         |
| ------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Inputs  | Site<br />brand<br />strategic prompts<br />clusters<br />source candidates    | Brand name<br />non-branded prompts<br />competitors<br />owned URLs            |
| Signals | Scores<br />answers<br />sources<br />citations<br />web health<br />gap types | AVI<br />citation rate<br />source visibility<br />urgency<br />GEO opportunity |
| Outputs | Next priority and reporting sentence                                           | Technical fix<br />content brief<br />source work<br />weekly report note       |

## What should you look at first?

<Steps>
  <Step title="1. Summarize the state in one sentence">
    Replace “the score is low” with a cause-based sentence such as “official citations are weak for non-branded comparison prompts.”
  </Step>

  <Step title="2. Split the cause into four work types">
    Move technical blockers to Site Audit. Send question gaps to Prompt Analysis, source gaps to Citation Tracking, and content gaps to Content Factory.
  </Step>

  <Step title="3. Choose one next action">
    Turn the signal into one next action: a cluster update, page edit, FAQ, source task or weekly report note.
  </Step>
</Steps>

## Main cards, tabs, or metrics

| Area           | What to inspect                                                   | Decision standard                         |
| -------------- | ----------------------------------------------------------------- | ----------------------------------------- |
| Current signal | Score<br />card<br />answer<br />source<br />or page issue        | Baseline and week-over-week movement      |
| Gap            | Weak prompt<br />source<br />content<br />or competitor advantage | Why the team should act                   |
| Priority       | Urgency<br />GEO opportunity<br />AIO fit<br />SEO foundation     | What should happen this week              |
| Next action    | Content<br />technical<br />source<br />or report work            | Whether it can have an owner and deadline |

## Practical use cases

| Situation                    | What to do with this feature                            | Output                            |
| ---------------------------- | ------------------------------------------------------- | --------------------------------- |
| Before a customer meeting    | Find weak prompt sets and source gaps.                  | One-page diagnostic summary       |
| Internal execution meeting   | Choose this week’s content, technical, or source tasks. | Ticket or content brief           |
| Executive/customer reporting | Explain cause and next action, with the score.          | Weekly report or export           |
| SEO/GEO strategy             | Read SEO foundation and AI answer signals together.     | Strategy Map and keyword clusters |

## How to explain it in meetings

“This feature shows how far the brand travels inside AI search answers and what content, source, or technical action should happen next.” Avoid customer names, real URLs, and internal KPIs in public documentation.

## FAQ

### Does this feature complete the decision by itself?

No. HaloX features are connected. A signal in GEO Dashboard should move into Site Audit, Strategy Map, Content Factory, Citation Tracking, or weekly reporting.

### Do scores map directly to business results?

Most GEO metrics are leading indicators. Mentions and citations usually move first; traffic, branded search and conversion prompts are checked later.

## Related guides and concepts

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/en/introduction/quickstart">Start the first 30-minute workflow.</Card>
  <Card title="Reading scores" icon="chart-line" href="/en/guides/reading-scores">Translate metrics into meeting language.</Card>
  <Card title="GEO glossary" icon="book-open" href="/en/glossary/index">Understand GEO, AVI, citation rate, and source visibility.</Card>
  <Card title="Reports" icon="file-chart-column" href="/en/guides/reports">Turn movement into reporting language.</Card>
</CardGroup>

## How to read the main KPI cards

| KPI                | What it means                                                            | Basis                                                 | How to interpret it                                                                 |
| ------------------ | ------------------------------------------------------------------------ | ----------------------------------------------------- | ----------------------------------------------------------------------------------- |
| Brand Coverage     | Share of AI answers that mention the brand                               | Runs where the brand appears in answer text           | Low coverage means AI answers do not recall the brand often enough.                 |
| Source Coverage    | Share of runs where the brand domain is used as evidence                 | Runs where a brand source is detected                 | Source without Citation is a hidden opportunity.                                    |
| Citation Coverage  | Share of runs where the brand URL/domain appears as a final cited source | Runs with detected brand citation                     | This is the strongest GEO signal; read it before generic visibility.                |
| Share of Voice     | Brand share among AI-answer cited sources                                | Per-engine citation share, interpreted across engines | A high value in one engine only may mean engine bias, not full coverage.            |
| Hidden Opportunity | Questions where the brand is sourced but not cited                       | Source exists, but final citation is missing          | These pages may convert to citations with better answer fit and evidence structure. |

## Brand, Source, Citation funnel

| Stage    | Meaning                                                   | Next action                                                               |
| -------- | --------------------------------------------------------- | ------------------------------------------------------------------------- |
| Brand    | AI answer mentions the brand name                         | Check whether positioning and brand description are clear.                |
| Source   | AI uses the brand domain as supporting evidence           | Review official docs, pricing, feature, and case pages for trust signals. |
| Citation | AI answer displays the brand URL/domain as a final source | Treat this as the strongest GEO signal and compare it with competitors.   |

## Turning dashboard signals into actions

| Situation                              | Interpretation                                       | Next action                                                               |
| -------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------- |
| Brand is high, but Citation is low     | AI knows the brand but does not select brand sources | Strengthen source credibility, structured data, and FAQ-style evidence.   |
| Source exists, but Citation is missing | AI considered the source but did not expose it       | Treat it as a hidden opportunity and improve title and answer paragraphs. |
| Competitor SOV is high                 | Competitors own AI-answer source visibility          | Compare competitor source pages with the matching brand pages.            |

## If you need the service metric definitions

Terms such as `rank`, `search volume`, `trend`, `AI`, `PAA`, `Citation Rate`, `Share of Voice`, and `gap type` are explained in the [screen metrics glossary](/en/glossary/screen-metrics). Use it when a KPI on this page needs a plain-language definition and a link back to the screen where it appears.