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

# Frequently asked questions

> Frequently asked questions for teams evaluating HaloX and GEO operations, from setup and feature use to reporting decisions.

<Frame>
  <img src="https://mintcdn.com/afterworklab/5NGf7Fi0rCLZYAc3/images/concepts/page-thumbnails/en-faq.png?fit=max&auto=format&n=5NGf7Fi0rCLZYAc3&q=85&s=c0301d39a5f3ccf35fbfc35e4fbca5ec" alt="HaloX FAQ page thumbnail summarizing Frequently asked questions in five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-faq.png" />
</Frame>

## HaloX and GEO

<AccordionGroup>
  <Accordion title="What is HaloX?">
    HaloX is an AI search visibility platform for understanding how a brand appears in AI answers and which sources support it. Teams move from diagnosis to strategy, content work, and weekly reporting in one workflow.
  </Accordion>

  <Accordion title="Is GEO different from SEO?">
    GEO builds on SEO. SEO helps search engines crawl and understand a site; GEO manages how AI answers describe the brand and which evidence they use.
  </Accordion>

  <Accordion title="What should we do first?">
    Start with overall AVI and web health on the Dashboard. Then review important Site Audit issues and choose the next GEO opportunity cluster in Strategy Map.
  </Accordion>
</AccordionGroup>

## Adoption and plans

<AccordionGroup>
  <Accordion title="What should we prepare before adoption?">
    Prepare the main site URL and product description first. Key questions and competitors make the diagnosis stronger. GSC or GA4 access can be added after the first baseline.
  </Accordion>

  <Accordion title="Do we still need HaloX if we already use SEO tools?">
    Yes. Existing SEO tools show rankings and traffic. HaloX shows whether the brand appears in AI answers, whether official sources are cited, and which questions are missing coverage.
  </Accordion>

  <Accordion title="How should we measure success?">
    Early success starts with AVI and citation rate. Source visibility and question coverage should move before traffic and conversions become reliable indicators.
  </Accordion>

  <Accordion title="Can agencies use HaloX for client proposals?">
    Yes. Use the client proposal template to scope the diagnosis and the GEO report example to package ongoing execution results.
  </Accordion>
</AccordionGroup>

## Data and trust

<AccordionGroup>
  <Accordion title="Do we have to connect GSC or GA4?">
    It is recommended, but not required for the first diagnosis. Connecting search and traffic data improves interpretation of AI search signals.
  </Accordion>

  <Accordion title="How do we trust AI citations and sources?">
    Do not rely on one answer. Track repeated question sets and watch how official sources, citation URLs, and question coverage change together.
  </Accordion>

  <Accordion title="Does low AI traffic mean GEO is not useful?">
    No. In GEO, brand mentions and citation rate can move before traffic. Treat traffic as a lagging indicator.
  </Accordion>
</AccordionGroup>

## Product usage

<AccordionGroup>
  <Accordion title="What does site audit check?">
    It checks crawl status and AI accessibility first. Then it reviews structured data and JavaScript dependence before listing page-level issues.
  </Accordion>

  <Accordion title="When should we use the strategy map?">
    Use it when deciding which keyword clusters and question groups to execute first. Search volume and gap type show where the next GEO opportunity sits.
  </Accordion>

  <Accordion title="How is Content Factory different from generic AI writing?">
    Generic AI writing focuses on body generation. Content Factory connects strategy analysis, content drafting, and trust reporting to make content easier for AI systems to cite.
  </Accordion>

  <Accordion title="How should weekly reports be used?">
    Use them for client and executive reporting. Summarize metric movement, open site issues, and the next content action.
  </Accordion>
</AccordionGroup>

## Problem-led AI search

<AccordionGroup>
  <Accordion title="Where should we start if our brand is missing from AI search?">
    Separate branded prompts from non-branded prompts first. If the brand appears only when named directly, use [Brand missing from AI search](/en/guides/brand-missing-in-ai-search) and [Get mentioned in ChatGPT](/en/guides/chatgpt-brand-visibility) to review the missing question coverage.
  </Accordion>

  <Accordion title="What if AI answers mention only competitors?">
    Record the prompt groups and citation URLs that support competitors. Then use [Competitor-only AI answers](/en/guides/competitor-only-ai-answers) to break down Share of Voice, official-source gaps, and comparison content needs.
  </Accordion>

  <Accordion title="Can we create free AI visibility diagnosis lead assets?">
    Yes. Keep the docs as the method explanation and route input/results UX to product or marketing pages. Use [Free AI visibility diagnosis keyword strategy](/en/guides/free-ai-visibility-diagnosis) to design brand-mention and source-check paths.
  </Accordion>

  <Accordion title="Where do we start the actual diagnosis after reading the docs?">
    The app entry is `https://haloxlabs.ai/app`. Prepare the primary URL and brand name, then follow the [Quickstart](/en/introduction/quickstart) 30-minute flow to create the first baseline.
  </Accordion>
</AccordionGroup>

## Related docs

* [Quickstart](/en/introduction/quickstart)
* [Adoption planning](/en/introduction/plans)
* [Data readiness checklist](/en/guides/data-readiness-checklist)
* [AI search optimization checklist](/en/guides/ai-search-optimization-checklist)
* [GEO report example](/en/guides/geo-report-example)