What should you prepare
| Input | Where to open it in HaloX | Ready state |
|---|---|---|
| Target queries | Monitoring Dashboard | GSC queries and pages are connected. |
| Candidate pages | Site Audit | Index/access/meta/schema state is checked. |
| AI answer questions | Prompt Analysis | Search intent is mapped to AI-style questions. |
| Source candidates | Citation Tracking, Knowledge Hub | Official and external URLs are separated. |
When should you use this guide?
| Situation | Signal to inspect | Decision |
|---|---|---|
| Official sources are not in AI Overview | Search visibility exists but answer evidence is missing | Improve page structure and source trust. |
| External or competitor pages are selected | Third-party URLs outperform official pages | Create official FAQ and comparison evidence. |
| Queries and questions do not match | GSC query intent differs from AI questions | Rebuild the prompt set. |
| Before content updates | The team does not know which page to fix | Cross-check monitoring queries and Site Audit issues. |
Workflow
1. Pick queries and pages in Monitoring Dashboard
Start from GSC queries and pages with real impressions or clicks.
2. Check candidate page readability in Site Audit
Review title, meta, headings, schema, and bot access.
3. Convert search queries into AI questions
Use Prompt Analysis to see which answer and citations the query-like question produces.
4. Improve summaries, FAQs, and evidence blocks
Create Content Production briefs for answer-ready definitions, steps, comparisons, FAQs, and links.
How do you verify the result?
| HaloX surface | Value to read | Next action |
|---|---|---|
| Monitoring Dashboard | Target query and page performance | Prioritize candidate pages. |
| Site Audit | Page structure and access | Create technical/content fixes. |
| Citation Tracking | AI answer source URLs | Watch official source share. |
| Content Production | AI Overview improvement briefs | Move to summary/FAQ/schema work. |
AI Overview candidate table
| Criteria | Good candidate | Needs work | HaloX surface |
|---|---|---|---|
| Search demand | Query impressions exist | Little query data | Monitoring Dashboard |
| Page structure | Title, summary, and FAQ are clear | The answer is scattered | Site Audit |
| Source trust | Official docs or cases support the answer | External/competitor URLs dominate | Citation Tracking |
| Execution | Owner and brief exist | Action is abstract | Content Production |
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
AI Visibility Index
Read the core AI visibility score.
Prompt Analysis
Inspect answers and citations by question.
Content Production
Turn findings into briefs.
Weekly Reports
Package changes for meetings.