> ## 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.

# Onboarding for teams using HaloX for the first time

> Use this guide to start your first HaloX workflow through the dashboard, Site Audit, Strategy Map, Content Factory, and Weekly Reports.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-onboarding.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=0c7103a801fd688908ae7df793f8f3bb" alt="HaloX Guides page thumbnail summarizing Onboarding for teams using HaloX for the first time in five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-onboarding.png" />
</Frame>

When you first enter HaloX, do not try to use every feature at once. Follow this operating sequence: **current state → root cause → priority → content execution → reporting**.

<Frame>
  <img src="https://mintcdn.com/afterworklab/_80UGNScApNoAtDW/images/app/dashboard-overview.png?fit=max&auto=format&n=_80UGNScApNoAtDW&q=85&s=75b0c41a3bdfdf8d87b11c26bb066738" alt="HaloX dashboard overview" width="1280" height="633" data-path="images/app/dashboard-overview.png" />
</Frame>

*HaloX dashboard overview*

## What should you prepare?

* A HaloX workspace and the site you want to analyze.
* Google Search Console, GA4, prior SEO reports, or meeting notes if available.
* 5–10 core questions your team or customer needs to answer.
* A place to record findings for internal or customer-facing follow-up.

## How do you verify the result?

| Check         | Good state                                                                         | Next action                                  |
| ------------- | ---------------------------------------------------------------------------------- | -------------------------------------------- |
| Current state | You understand AVI<br />SEO<br />web health<br />and citation rate at a high level | Separate the causes by feature area.         |
| Diagnosis     | Site Audit shows important and warning issues                                      | Split work into developer and content tasks. |
| Priorities    | Strategy Map identifies urgent and GEO-opportunity clusters                        | Move work to Content Factory or tickets.     |
| Deliverables  | Drafts, fixes, or report sentences exist                                           | Export and summarize in Weekly Reports.      |

## What commonly blocks teams?

| Problem                                  | Cause                                                       | Fix                                                               |
| ---------------------------------------- | ----------------------------------------------------------- | ----------------------------------------------------------------- |
| Scores are visible but action is unclear | Metrics were not translated into work items                 | Start with Strategy Map gap types and priority clusters.          |
| Customer explanation is difficult        | Technical metrics were not converted into business language | Add cause, impact, and next action to every report point.         |
| Changes are not immediate                | AI answers update through repeated crawling and evaluation  | Track the same question set weekly.                               |
| Cluster choice is confusing              | Keywords are treated like folders                           | Treat clusters as groups of questions AI may evaluate together.   |
| Quota/error messages feel alarming       | Request state is confused with output quality               | Quota is usage-state information, not a judgment on your content. |

## Recommended first 30 minutes

<Steps>
  <Step title="1. Review the dashboard">
    Check `overall AVI`, `SEO`, `web health`, `citation rate`, and traffic summary. Focus on which area is weak, with the score.
  </Step>

  <Step title="2. Find causes in Site Audit">
    Review SEO, GEO, performance, schema, and crawlability issues. Separate developer work from content work.
  </Step>

  <Step title="3. Pick priorities in Strategy Map">
    Choose only 1–3 clusters for the week based on urgency, GEO opportunity, and gap type.
  </Step>

  <Step title="4. Create deliverables in Content Factory">
    Turn selected clusters into question-led content with definitions, comparisons, FAQ, and sources.
  </Step>

  <Step title="5. Record the week in Reports">
    Leave a short summary of findings, actions, and next steps. GEO works through repeated operations.
  </Step>
</Steps>

## Terms first-time users confuse

| HaloX term             | Plain explanation                                        | Feature                                             |
| ---------------------- | -------------------------------------------------------- | --------------------------------------------------- |
| AVI                    | Overall view of how visible your brand is in AI answers  | [GEO Dashboard](/en/features/geo-dashboard)         |
| Strategic question set | Core AI questions to measure repeatedly                  | [Prompt Analysis](/en/features/prompt-analysis)     |
| Cluster                | A group of related questions and keywords                | [Strategy Map](/en/features/strategy-map)           |
| Citation rate          | How often AI answers show your site as a source          | [Citation Tracking](/en/features/citation-tracking) |
| GEO opportunity        | A candidate topic where AI-answer visibility can improve | [Strategy Map](/en/features/strategy-map)           |

## First explanation by audience

| Audience          | Explain it this way                                                                        | Show first                       |
| ----------------- | ------------------------------------------------------------------------------------------ | -------------------------------- |
| Executive         | “The brand appears in AI search this way, and the next improvement is this.”               | Dashboard, Weekly Reports        |
| Marketing team    | “We group keywords and questions to decide which content to create first.”                 | Strategy Map, Content Factory    |
| PR/communications | “We check whether official messages and external sources shape AI answers.”                | GEO Dashboard, Citation Tracking |
| Web/development   | “We separate technical blockers that prevent AI and search engines from reading the site.” | Site Audit                       |
| Local team        | “We connect local questions to branch pages and recommendation visibility.”                | Strategy Map, local GEO guide    |

## Next docs

* Start technical work with [Run your first Site Audit](/en/guides/first-site-audit).
* Interpret metrics with [Reading HaloX scores](/en/guides/reading-scores).
* Execute content with [Create AI-citable content](/en/guides/creating-content).
* Prepare reporting with [Weekly Reports](/en/guides/reports).