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

# Data readiness checklist: prepare GSC, GA4, and question sets

> Prepare representative URLs, GSC/GA4 connections, Pro question sets, competitors, and source candidates in HaloX before interpreting AI visibility data.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-data-readiness-checklist.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=53f20a7b49320b9423d2dbebac57acb6" alt="Thumbnail summarizing the HaloX guide page Data readiness checklist: prepare GSC, GA4, and question sets as five workflow cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-data-readiness-checklist.png" />
</Frame>

HaloX analysis is not a “paste one URL and wait” workflow. Align **representative URLs, monitoring data, question sets, source candidates, and owners** first so Dashboard, Prompt Analysis, and Weekly Reports use the same baseline.

## What should you prepare

| Input               | Where to open it in HaloX         | Ready state                                                                         |
| ------------------- | --------------------------------- | ----------------------------------------------------------------------------------- |
| Representative URLs | Site Audit, Monitoring Dashboard  | Homepage<br />product<br />blog<br />and help URLs are separated.                   |
| GSC/GA4 access      | Monitoring Dashboard              | Property connection and recent data period are confirmed.                           |
| Question sets       | Click Pro → Prompt Status         | Brand<br />non-brand<br />comparison<br />and buying questions are split into sets. |
| Competitors         | Prompt Analysis, Strategy Map     | Three to five comparison brands are fixed.                                          |
| Source candidates   | Knowledge Hub, Content Production | Official docs<br />FAQs<br />newsroom<br />and external reviews are separated.      |

## When should you use this guide?

| Situation                             | Signal to inspect                                            | Decision                                                               |
| ------------------------------------- | ------------------------------------------------------------ | ---------------------------------------------------------------------- |
| New workspace setup                   | Dashboard scores exist but the question baseline is unclear  | Fix question sets and URL scope before measuring.                      |
| First report after GSC/GA4 connection | Monitoring data is sparse or the wrong property is connected | Separate search/behavior data from AI answer data.                     |
| Competitor comparison request         | Competitors repeat in Prompt Analysis                        | Manage comparison questions and official source candidates separately. |
| Content production starts             | Briefs lack evidence URLs                                    | Use Knowledge Hub and Site Audit as inputs.                            |

## Workflow

<Steps>
  <Step title="1. Read the current state in Lite first">
    In Lite mode the sidebar shows Dashboard, Strategy Map, Content Production, and Site Audit. Use it to read AVI, citation rate, web health, and report readiness quickly.
  </Step>

  <Step title="2. Click Pro and open analysis menus">
    Click the Pro button in the sidebar and confirm Keyword Status, Keyword Analysis, Prompt Status, and Prompt Analysis are visible. Prepare question sets from this Pro surface.
  </Step>

  <Step title="3. Confirm GSC/GA4 in Monitoring Dashboard">
    Open /app/monitoring and check properties, recent periods, query signals, and page signals. If data is empty, fix connection and permissions before reporting.
  </Step>

  <Step title="4. Split question sets in Prompt Status">
    Separate brand, comparison, buying, and problem-led questions. Record each set name and purpose so teams do not measure different things.
  </Step>

  <Step title="5. Fix the baseline for Weekly Reports">
    Record baseline questions, URLs, competitors, and source candidates in Weekly Report. Future movement should be explained against that baseline.
  </Step>
</Steps>

## How do you verify the result?

| HaloX surface        | Value to read                                 | Next action                               |
| -------------------- | --------------------------------------------- | ----------------------------------------- |
| Monitoring Dashboard | GSC/GA4 connection, query and page data       | Return to the connection guide if empty.  |
| Prompt Status        | Question set count and recent runs            | Split mixed question groups.              |
| Prompt Analysis      | Brand mentions, competitors, citation sources | Move gaps into Content Production briefs. |
| Weekly Report        | Baseline questions and key changes            | Prepare meeting-ready language.           |

## Copyable readiness table

| Area               | Value to record       | Example                                             | HaloX surface                     |
| ------------------ | --------------------- | --------------------------------------------------- | --------------------------------- |
| Representative URL | Target URL            | `https://example.com`, `/blog`, `/docs`             | Site Audit                        |
| Data property      | GSC/GA4 property name | `example.com` Search Console property               | Monitoring Dashboard              |
| Question set       | Set name and purpose  | Brand recommendation, alternatives, buying review   | Prompt Status                     |
| Competitors        | Brands to compare     | Competitor A, B, C                                  | Prompt Analysis, Strategy Map     |
| Evidence URL       | Page you want cited   | Product docs<br />FAQ<br />case study<br />newsroom | Knowledge Hub, Content Production |

## What commonly blocks teams

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

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

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

## Related docs

<CardGroup cols={2}>
  <Card title="Connect GSC/GA4" icon="plug" href="/en/guides/connect-gsc-ga4">Align data connections first.</Card>
  <Card title="Prompt Status" icon="message-square" href="/en/features/prompt-status">Review question sets and run status.</Card>
  <Card title="Monitoring Dashboard" icon="chart-line" href="/en/features/monitoring-dashboard">Read query and page signals.</Card>
  <Card title="GEO report template" icon="file-text" href="/en/guides/geo-report-template">Move the baseline into a report.</Card>
</CardGroup>