What to prepare
| Item | Check | HaloX screen |
|---|---|---|
| Google access | Read access for GSC and GA4, approved OAuth account | Integration/settings flow, Monitoring Dashboard |
| Property match | Protocolwwwsubdomain market/language property | Site Audit, Monitoring Dashboard |
| Priority URLs | Homepage landing pages blog/guides help center URLs | Site Audit, Keyword Analysis |
| Prompt set | Brand non-brand comparison purchase-intent prompts | Prompt Status, Prompt Analysis |
| Reporting rule | Which metrics and owners will be reported weekly | Weekly Report |
What to verify after connecting
| Check | Good state | If it is wrong |
|---|---|---|
| Property alignment | The HaloX workspace domain and GSC/GA4 property represent the same site | Scores and traffic movement will not explain each other. |
| Data latency | Recent 2–3 days are not treated as final | Teams overreact to short-term movement. |
| URL comparison | Site Audit issue URLs are compared with impression/click URLs | You cannot decide which page to fix. |
| Prompt comparison | Prompt groups are compared with search-query groups | AI-answer problems and search-demand problems get mixed. |
Workflow
1. Confirm the Google account and property
Make sure the connecting account has read access to the real production domain. If multiple properties exist, choose the one matching the HaloX workspace URL.
2. Establish the URL baseline in Site Audit
Use Site Audit to identify crawl, metadata, schema, and page-level issues, then compare them with URLs that have impressions or clicks.
3. Read search and traffic movement in Monitoring Dashboard
Monitoring Dashboard is where GSC/GA4 movement is read alongside HaloX operating signals. Separate impressions/clicks from AVI and citation-rate changes.
4. Match Prompt Analysis with search queries
If a prompt has search demand but weak AI-answer presence, move the cluster into Strategy Map or Content Production.
Report wording examples
| Situation | Sentence |
|---|---|
| Search demand is stable, citation rate drops | “Search demand is stable, but AI-answer citations shifted toward competitors or third-party sources. Prioritize the comparison prompt group in Prompt Analysis.” |
| Site issues overlap with search decline | “The URLs losing impressions overlap with Site Audit issues. Technical fixes come before new content this week.” |
| Search queries exist but AI answers omit the brand | “GSC confirms demand, but the brand is missing in AI-answer prompt groups. Move the cluster into Strategy Map and Content Production.” |
| GA4 sessions exist but purchase prompts are weak | “Traffic exists but purchase-intent prompts lack grounded evidence. Add FAQ comparison and case content.” |
Related docs
Monitoring Dashboard
Read GSC/GA4 search and page movement.
Site Audit
Separate URL-level technical and content issues.
Prompt Analysis
Compare AI-answer prompts and source signals.
Weekly reports
Turn search and AI-visibility movement into report language.