> ## 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.
# Agency GEO operations
> How agencies can turn customer-facing GEO questions into repeatable HaloX diagnosis and reporting workflows.
Agencies rarely struggle with the definition of GEO. The harder question is how to package it for clients: what to diagnose first, what to execute next, and how to report progress. In customer and partner meetings, the clearest operating language was **diagnosis → strategy → content/channel execution → weekly reporting**.
## What should you prepare before starting?
* Make sure your HaloX workspace and target site are ready.
* Keep GSC/GA4 access and any existing SEO or meeting notes nearby.
* Decide where the output will live: internal note, client report, or weekly operating document.
## How do you verify the result?
| Check | Healthy state | Next action |
| ------------------ | ----------------------------------------------------------- | ------------------------------------------------------- |
| Workflow completed | The requested audit or reporting task is finished | Reflect the result in Strategy Map and the right report |
| Priority selected | The next keyword, page, or content opportunity is clear | Assign an owner and due date |
| Evidence recorded | The metrics and reasoning can be reused in the next meeting | Track the same signals next week |
## What commonly blocks teams?
| Problem | Cause | Fix |
| --------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------- |
| Scores are visible but next steps are unclear | Metrics were not translated into execution units | Start from Strategy Map GAP types and priority clusters. |
| It is hard to explain to customers | Technical signals were not converted into business language | Add cause, impact, and next action to every report item. |
| Results do not change immediately | AI answer surfaces need time to recrawl and reassess sources | Track the same prompt set and metrics weekly. |
## Questions that repeatedly came up in meetings
| Client question | Public answer | Where to look in HaloX |
| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------- |
| How do we productize GEO/AIO diagnosis? | Package it as a diagnostic report
strategic prompt set
content execution plan
and weekly report instead of a one-off education session. | Dashboard
Site Audit
Strategy Map
Weekly Reports |
| Are Naver
Google
ChatGPT
and Gemini the same? | No. Separate search visibility, AI-answer visibility, and owned-media readiness by channel. | Prompt sets, citation tracking, Strategy Map |
| How do we explain technical metrics simply? | Translate mention/source/citation into: does the brand appear, is it used as evidence, and is it cited as a link? | Citation rate, top AI questions, Content Factory Trust Report |
| What belongs in the first proposal? | Scope
current weaknesses
priority questions
content types to fix
and a 2–4 week execution plan. | Export, Weekly Reports |
## Recommended workflow
Use the Dashboard to inspect AVI Overall Score and Web Health first. In the first report, explain weak areas and why they matter rather than over-emphasizing the score.
Separate brand and non-brand questions first. Keep comparison, buying and location questions as distinct prompt groups.
Use Site Audit to inspect AI bot access, structured data, metadata quality and page performance. If SEO fundamentals are weak, propose SEO recovery before GEO expansion.
Read AIO, GEO and SEO signals together with gap type and urgency. Questions where competitors are repeatedly cited usually create the strongest client case.
Strengthen definitions and FAQ pages first, then add comparison tables, evidence blocks and source links. For agencies, this is where analysis becomes visible execution.
Summarize what changed, what blocked progress, and what the client should do next. Export the deliverables that need to be included in client decks or reports.
## Agency service packages
| Package | Includes | Client-facing deliverable |
| --------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------- |
| One-page diagnosis | Dashboard KPIs, Site Audit issues, AI-answer brand/competitor visibility | Current state, top risks/opportunities, next actions |
| 2–4 week sprint | 20–50 strategic questions, urgent clusters, content improvement plan | Prompt set, priority content list, sample fixes |
| Monthly operations | Repeated audits, Content Factory execution, citation and visibility reporting | Weekly/monthly reports and meeting summaries |
| Joint execution model | Agency runs PR/content; HaloX provides diagnosis, strategy, and verification | Role map, execution calendar, verification report |
## Customer FAQ
### Is GEO a separate project from SEO?
Usually no. GEO sits on top of SEO readiness. Technical SEO, content structure and bot access affect whether AI systems can use a brand as a source. HaloX connects Site Audit, Strategy Map, and Content Factory into one operating loop.
### Is a brand mention enough?
No. Mentions are only the first layer. Track whether the brand is named, used as evidence, and cited against the right prompt set. The stronger question is not “did the brand appear?” but “was the brand used as evidence for the right questions?”
### How should we explain metrics to clients?
Mention means the brand appears. Source means the brand asset is used as evidence. Citation means the answer shows the asset as a link or reference. AVI should be positioned as an operating signal for AI-search visibility, not as a public fixed formula.
### Do we need revenue attribution in month one?
Not necessarily. First establish the baseline: AI visibility, citation health, competitor gaps and Site Audit progress. Revenue attribution is a later-stage measurement layer.
## Reporting example
```text theme={null}
This week, the largest gap was not brand mentions but source and citation visibility.
Strategy Map identified three non-brand comparison clusters as GEO opportunities,
and Site Audit found structured-data and AI-accessibility issues.
Next week, use Content Factory to strengthen those clusters with FAQ pages, comparison tables and evidence links.
```
## Related pages
* [Feature overview](/en/features/overview)
* [Strategy Map](/en/features/strategy-map)
* [Content Factory](/en/features/content-factory)
* [Weekly Reports](/en/guides/reports)
* [AI Share of Voice](/en/glossary/share-of-voice)
## Proposal language by scenario
Agencies should turn GEO into deliverables customers can approve: a diagnostic report, an execution sprint, monthly movement reporting and content briefs.
| Proposal section | What to include | Related doc |
| ------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------- |
| Current state | Weak areas across AVI
citation rate
source visibility
and web health | [Reading scores](/en/guides/reading-scores) |
| Priority prompt set | Branded
non-branded
comparison
local
and buying-review questions | [Prompt analysis](/en/features/prompt-analysis) |
| Execution asset | FAQ
comparison table
entity hub
newsroom or blog improvements | [Content Factory](/en/features/content-factory) |
| Verification | Weekly movement across the same prompts and citation URLs | [Reports](/en/guides/reports) |
### How to anonymize cases
Do not publish customer names, real URLs or meeting transcripts. Convert each case into an industry context, question type, HaloX screen and next action.