What should you prepare
| Input | Where to open it in HaloX | Ready state |
|---|---|---|
| Official sources | Knowledge Hub, Content Production | Product docs FAQ pricing cases and newsroom URLs are separated. |
| External sources | Prompt Analysis, Citation Tracking | Press review partner and community URLs are tracked separately. |
| Technical accessibility | Site Audit | Robots schema titles meta and page status have been checked. |
| Question-source mapping | Prompt Analysis | Expected sources and actual citations can be compared per question. |
| Owner | Content Production, Weekly Reports | The page to improve and the owner are assigned. |
When should you use this guide?
| Situation | Signal to inspect | Decision |
|---|---|---|
| The brand is mentioned but citations are weak | Prompt Analysis cites third-party sources | Improve official sources through Knowledge Hub and Content Production. |
| Competitor sources repeat | Comparison questions cite competitor pages first | Add comparison pages, FAQs, and cases. |
| AI Overview needs source readiness | Official pages are not used as evidence | Review Site Audit and schema/summary structure. |
| Client reporting needs evidence | Source quality must be explained clearly | Create good/watch/improve source tables. |
Workflow
1. Open Prompt Analysis in Pro
In the Pro sidebar analysis section, open Prompt Analysis and inspect answer text, brand mentions, and citation URLs per question.
2. Classify citations as official, external, or competitor
Separate official docs, external reviews/press, competitor pages, and generic knowledge pages. The repeated type matters more than raw count.
3. Validate technical trust in Site Audit
Check whether candidate pages are crawlable and have titles, summaries, and schema that can work as answer evidence.
4. Move source gaps into Knowledge Hub and Content Production
For questions missing official evidence, create briefs for FAQs, comparison tables, case pages, or definition pages.
How do you verify the result?
| HaloX surface | Value to read | Next action |
|---|---|---|
| Prompt Analysis | Citation URLs by question | Classify source types. |
| Citation Tracking | Official, external, and competitor source movement | Prioritize repeated citations. |
| Site Audit | Schema meta headings bot access | Send technical issues to the right owner. |
| Content Production | Briefs for source improvements | Turn source gaps into pages. |
Source trust classification
| Source type | Good state | Risk signal | HaloX follow-up |
|---|---|---|---|
| Official | Product pricing FAQ or case pages are cited | Only old landing pages repeat | Knowledge Hub, Content Production |
| External | Press, reviews, and partner pages support the answer | Unofficial blogs explain product facts | PR or external page update |
| Competitor | Appears only in comparison context | Competitor URLs cite our brand questions | Comparison page and FAQ work |
| Technical | Schema and metadata explain the answer | Access is blocked or summaries are vague | Site Audit issue |
What commonly blocks teams
Is it a bug if GSC/GA4 numbers and HaloX scores do not match exactly?
Is it a bug if GSC/GA4 numbers and HaloX scores do not match exactly?
No. GSC and GA4 describe search traffic and user behavior, while HaloX AVI, citation rate, and source visibility describe how the brand and sources appear in AI answers. They support the same operating decision but use different measurement units.
Should the same question set be reused forever?
Should the same question set be reused forever?
Keep baseline questions, but add separate sets when products, competitors, or buyer questions change. Do not overwrite the baseline; split the comparison axis so weekly reports can explain the cause of movement.
Where should the guide output be recorded?
Where should the guide output be recorded?
Move evidence into Weekly Report and Exports, and convert actions into Content Production briefs or Site Audit issues. In meetings, report the question group, source gap, and next action together, with the score.
Related docs
Citation Tracking
Inspect citation URL movement.
Knowledge Hub
Organize source candidates.
Site Audit
Check access and structured signals.
Content brief template
Turn source gaps into briefs.