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

# Connect GSC and GA4: align search data with HaloX signals

> Check permissions, properties, data latency, and verification screens before connecting Google Search Console and GA4 to HaloX, then interpret SEO data with AVI, citation rate, and weekly reports.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-connect-gsc-ga4.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=02aca417198902a4b49e45ad82f24a8c" alt="HaloX guide thumbnail summarizing how to align GSC and GA4 search data with AI visibility signals" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-connect-gsc-ga4.png" />
</Frame>

GSC and GA4 are supporting datasets for explaining HaloX AI-search signals. The point is OAuth plus team agreement on **which property is connected and how search or traffic movement explains AVI, citation rate, and content execution**.

## 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 | Protocol<br />`www`<br />subdomain<br />market/language property   | Site Audit, Monitoring Dashboard                |
| Priority URLs  | Homepage<br />landing pages<br />blog/guides<br />help center URLs | Site Audit, Keyword Analysis                    |
| Prompt set     | Brand<br />non-brand<br />comparison<br />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

<Steps>
  <Step title="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.
  </Step>

  <Step title="2. Establish the URL baseline in Site Audit">
    Use [Site Audit](/en/features/site-audit) to identify crawl, metadata, schema, and page-level issues, then compare them with URLs that have impressions or clicks.
  </Step>

  <Step title="3. Read search and traffic movement in Monitoring Dashboard">
    [Monitoring Dashboard](/en/features/monitoring-dashboard) is where GSC/GA4 movement is read alongside HaloX operating signals. Separate impressions/clicks from AVI and citation-rate changes.
  </Step>

  <Step title="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.
  </Step>

  <Step title="5. Separate causes in the weekly report">
    Do not merge “search impressions dropped,” “citation rate dropped,” and “site issues increased” into one sentence. Name the cause screen and the next action.
  </Step>
</Steps>

## 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<br />but purchase-intent prompts lack grounded evidence. Add FAQ<br />comparison<br />and case content.”                                         |

## Related docs

<CardGroup cols={2}>
  <Card title="Monitoring Dashboard" icon="chart-line" href="/en/features/monitoring-dashboard">Read GSC/GA4 search and page movement.</Card>
  <Card title="Site Audit" icon="shield-check" href="/en/features/site-audit">Separate URL-level technical and content issues.</Card>
  <Card title="Prompt Analysis" icon="message-square" href="/en/features/prompt-analysis">Compare AI-answer prompts and source signals.</Card>
  <Card title="Weekly reports" icon="calendar-days" href="/en/guides/reports">Turn search and AI-visibility movement into report language.</Card>
</CardGroup>