> ## 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 report example: explain HaloX results to clients and executives

> A practical GEO report example that turns HaloX AVI, citation rate, source visibility, site issues, and content execution into client and executive reporting language.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-geo-report-example.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=48c7674eb1ccb868428a7e622e1de554" alt="HaloX GEO report example thumbnail summarizing client and executive report wording" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-geo-report-example.png" />
</Frame>

Use the examples below by replacing the client name, prompt group, numbers, and URLs. A good report does not list scores only; it says **which HaloX screen proves the change, what decision was made, and what will be checked next**.

## Example 1: client-facing weekly summary

```md theme={null}
Document title: Weekly AI Search Visibility Summary

This week, [brand] remained stable in brand prompts, but competitor sources were cited more often in comparison and purchase-intent prompts.

- AVI: slightly up week over week
- Citation rate: down in comparison prompts
- Source visibility: third-party reviews and comparison pages appear more often than official blog pages
- Site audit: two priority landing pages need metadata and FAQ-structure improvements

The decision this week is not to create more articles at random. We will strengthen official evidence for the comparison prompt group, move the `comparison/alternatives` cluster from Strategy Map into Content Production, and prepare one brief with FAQ and comparison-table sections.
```

## Example 2: executive one-page summary

| Area            | This week’s decision                                  | Evidence screen                  | Next action                              |
| --------------- | ----------------------------------------------------- | -------------------------------- | ---------------------------------------- |
| AI visibility   | Brand prompts are stable; comparison prompts are weak | Dashboard, Prompt Analysis       | Prioritize comparison prompts            |
| Citations       | External sources outperform official URLs             | Citation Tracking                | Add official FAQ and comparison evidence |
| Site foundation | Some priority URLs lack strong structured signals     | Site Audit                       | Create schema/meta/FAQ tickets           |
| Execution       | Cluster improvement matters more than one-off content | Strategy Map, Content Production | Create and review one brief              |

## Example 3: meeting language

| Question                                     | Answer                                                                                                                      |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| “Did the score improve?”                     | “Overall AVI is stable, but the main issue this week is citation quality in comparison prompts.”                            |
| “Why do competitors appear more?”            | “Prompt Analysis shows recurring competitor sources in comparison prompts, while our official comparison evidence is weak.” |
| “Should we create more content immediately?” | “First, strengthen official FAQ and comparison-table evidence so answer engines have something to cite.”                    |
| “What is next week’s success criterion?”     | “We will rerun the same prompt set and check whether official URL citations increase and Site Audit issues decrease.”       |

## Workflow in HaloX

<Steps>
  <Step title="1. Pick the representative weekly change in Dashboard">
    Choose only one or two changes from AVI, citation rate, web health, and key-change cards.
  </Step>

  <Step title="2. Attach the prompt group from Prompt Analysis">
    Split the change by brand, non-brand, comparison, and purchase-intent prompts. Include real prompt wording when possible.
  </Step>

  <Step title="3. Confirm citation evidence in Citation Tracking">
    Separate official URLs, competitor URLs, and third-party review/media URLs so the source problem is explicit.
  </Step>

  <Step title="4. Turn the cause into action with Site Audit and Strategy Map">
    Technical issues become development tickets; prompt/source gaps become content briefs; source-trust problems become Evidence Library or PR work.
  </Step>
</Steps>

## Weak vs strong report wording

| Weak                           | Strong                                                                                                                       |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| “AVI increased by 3 points.”   | “Brand-prompt AVI improved, but comparison-prompt citations remain weak, so we will strengthen FAQ and comparison evidence.” |
| “We will create more content.” | “Move the `comparison/alternatives` cluster into Content Production and create one FAQ plus one comparison table.”           |
| “There are site issues.”       | “Two priority landing pages have schema/meta issues that should be fixed before expecting official citation recovery.”       |

## Related docs

<CardGroup cols={2}>
  <Card title="Weekly GEO report template" icon="file-text" href="/en/guides/geo-report-template">Copy the report structure.</Card>
  <Card title="Read scores" icon="gauge" href="/en/guides/reading-scores">Interpret AVI and citation rate.</Card>
  <Card title="Citation Tracking" icon="link" href="/en/features/citation-tracking">Check citation URLs and competitor sources.</Card>
  <Card title="Content brief template" icon="pen-nib" href="/en/guides/content-brief-template">Turn the next action into execution.</Card>
</CardGroup>