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

# Run your first Site Audit and read the results

> Learn how to read SEO, GEO, performance, and important issues in HaloX Site Audit and choose the first improvements for AI search readiness.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-first-site-audit.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=ab23dcb761c7f2a2deee1fc883c55508" alt="HaloX Guides page thumbnail summarizing Run your first Site Audit and read the results in five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-first-site-audit.png" />
</Frame>

The goal of Site Audit is not to admire a score. It is to find what prevents AI and search engines from reading and trusting your site.

<Frame>
  <img src="https://mintcdn.com/afterworklab/FASovyiIgMPqpeOo/images/app/site-audit-overview.png?fit=max&auto=format&n=FASovyiIgMPqpeOo&q=85&s=0c8ccc4c517a293eb3da7ee779859362" alt="HaloX Site Audit overview" width="1280" height="633" data-path="images/app/site-audit-overview.png" />
</Frame>

*HaloX Site Audit overview*

## What should you prepare?

* The representative domain and key URLs you want to analyze.
* Page groups such as homepage, product pages, newsroom/blog, FAQ, and local pages.
* A place to create development tickets or content tasks.
* A simple table for reporting cause, impact, and next action.

## How do you verify the result?

| Check             | Good state                                                                                | Next action                                       |
| ----------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------- |
| Critical issues   | No crawl blockers, missing core metadata, or major rendering blockers                     | If present, create development tickets first.     |
| SEO foundation    | Titles<br />descriptions<br />internal links<br />canonical<br />and sitemap are coherent | Decide content and technical fixes.               |
| GEO foundation    | Schema<br />FAQ<br />structured body<br />and source candidates exist                     | Connect to Content Factory and Citation Tracking. |
| Page-level issues | Priority URLs are clear                                                                   | Start with high-impact pages.                     |

## What commonly blocks teams?

| Problem                              | Cause                                            | Fix                                                                             |
| ------------------------------------ | ------------------------------------------------ | ------------------------------------------------------------------------------- |
| “We only want to improve GEO”        | SEO and GEO are treated separately               | SEO accessibility is the foundation for GEO.                                    |
| Too many issues                      | The team tries to fix the entire site at once    | Start with brand<br />conversion<br />newsroom<br />and local priority pages.   |
| Owner is unclear                     | Metrics are not translated into responsibilities | Robots/rendering/schema are technical; headings/FAQ/body structure are content. |
| The team wants only external content | Official-source readiness is underestimated      | Fix owned sources first, then design offsite support.                           |

## Reading order

<Steps>
  <Step title="1. Start with important issues">
    A high score matters less than whether AI and search engines can read the site at all.
  </Step>

  <Step title="2. Separate SEO and GEO">
    SEO is the search foundation. GEO is readiness for AI-answer sources. Weak SEO usually makes GEO unstable.
  </Step>

  <Step title="3. Assign roles to pages">
    Homepage defines the brand, product pages explain value, newsroom pages provide official messages, FAQ answers questions, and local pages provide branch signals.
  </Step>

  <Step title="4. Split work by owner">
    Developers, content teams, PR teams, agencies, and customer approvers should each get different tasks.
  </Step>

  <Step title="5. Move priorities into Strategy Map">
    Do not fix everything at once. Connect high-impact URLs to clusters and questions.
  </Step>
</Steps>

<Frame>
  <img src="https://mintcdn.com/afterworklab/FASovyiIgMPqpeOo/images/app/site-audit-pages.png?fit=max&auto=format&n=FASovyiIgMPqpeOo&q=85&s=c35e68ddd9cbf3a5d91e1febf728249b" alt="HaloX Site Audit page results" width="1280" height="633" data-path="images/app/site-audit-pages.png" />
</Frame>

*HaloX Site Audit page results*

## Interpretation patterns from meetings

| Scenario                            | Interpretation                                                                 | Report sentence                                                                                              |
| ----------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| Large platform or financial service | Technical SEO and trust pages should be checked before non-brand GEO expansion | “Before expanding non-brand acquisition, we need to stabilize official sources and technical accessibility.” |
| Communications team                 | Newsroom and official statements need to be usable as AI sources               | “For AI to cite official messages, newsroom structure and source signals need improvement.”                  |
| Local business                      | Branch URLs and regional FAQ should be separated                               | “Local recommendation visibility requires branch pages and local question sets.”                             |
| Global expansion                    | English pages<br />SSR/CSR<br />schema<br />and hreflang should be checked     | “English GEO starts with crawlable category definitions.”                                                    |

## Next action categories

| Category           | Examples                                                      | Related doc                                     |
| ------------------ | ------------------------------------------------------------- | ----------------------------------------------- |
| Development ticket | robots<br />sitemap<br />rendering<br />schema<br />canonical | [Site Audit](/en/features/site-audit)           |
| Content fix        | titles<br />descriptions<br />H2<br />FAQ<br />internal links | [Content Factory](/en/features/content-factory) |
| Strategy decision  | which URL or keyword to fix first                             | [Strategy Map](/en/features/strategy-map)       |
| Reporting          | weekly improvement and expected impact                        | [Weekly Reports](/en/guides/reports)            |