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

# Site Audit: separate SEO issues from AI-readiness gaps

> Site Audit checks whether AI bots and search engines can read the site and whether schema, web health, or page issues block GEO execution.

<Frame>
  <img src="https://mintcdn.com/afterworklab/5NGf7Fi0rCLZYAc3/images/concepts/page-thumbnails/en-features-site-audit.png?fit=max&auto=format&n=5NGf7Fi0rCLZYAc3&q=85&s=73637a8c69572c7adcc5eaa93a4c18f7" alt="HaloX Features page thumbnail summarizing Site Audit: Site Audit: separate SEO issues from AI-readiness gaps as five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-features-site-audit.png" />
</Frame>

## What is this feature?

**Site Audit** is the feature for checking whether AI bots and search engines can read the site and whether technical issues block GEO execution. It is a decision point in the HaloX `diagnose → measure → prioritize → execute → report` loop. Teams use it to read the current signal, split the cause, and decide the next content, source, technical, or reporting action.

## HaloX app location

<Frame caption="Site Audit Overview screen">
  <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 showing SEO, GEO and performance trends in the live app" width="1280" height="633" data-path="images/app/site-audit-overview.png" />
</Frame>

*Use Overview to read SEO, GEO and performance trends first. In meetings, split development fixes, metadata work, and content-structure work from this screen.*

<Frame caption="Score summary and issue detail panel">
  <img src="https://mintcdn.com/afterworklab/6BCxNsplfUWn2A0v/images/app/site-audit-score-issue-shell-context-live-20260507.png?fit=max&auto=format&n=6BCxNsplfUWn2A0v&q=85&s=6e8258325cb45248a42e988d5ffb21ae" alt="HaloX Site Audit detail crop showing SEO, GEO, and OTS scores with the prioritized issue panel" width="1280" height="550" data-path="images/app/site-audit-score-issue-shell-context-live-20260507.png" />
</Frame>

*Scores summarize the state, while the issue panel shows which items can become development or SEO tickets.*

When you start a new scan, enter the URL and maximum page count. For feature documentation, the more useful evidence is the result table that remains after the scan, because it shows which URLs become SEO, GEO, or development work.

Site Audit is the Pro-mode diagnosis area for separating technical issues from content and AI-readiness work. Review Overview, Issues, Pages, SEO and GEO before creating the next task.

## Actual tabs and subfeatures

| Tab      | What to inspect                                     | Next action                                  |
| -------- | --------------------------------------------------- | -------------------------------------------- |
| Overview | Web health, AI readiness, diagnosis summary         | Summarize the current risk in one sentence.  |
| Issues   | Critical, warning, and recommendation issues        | Move issues into development or SEO tickets. |
| Pages    | Affected URLs and page-level status                 | Choose the pages to fix first.               |
| SEO      | Metadata, structure, and indexing signals           | Strengthen the search foundation.            |
| GEO      | AI bot access, evidence readiness, answer candidacy | Improve structures that AI answers can cite. |

<Frame caption="URL-level SEO/GEO diagnosis table">
  <img src="https://mintcdn.com/afterworklab/6BCxNsplfUWn2A0v/images/app/site-audit-pages-table-shell-context-live-20260507.png?fit=max&auto=format&n=6BCxNsplfUWn2A0v&q=85&s=bd3e69122df2b74bd4df08fa8604b5a3" alt="HaloX Site Audit Pages table crop showing SEO and GEO scores with metadata status by URL" width="1280" height="633" data-path="images/app/site-audit-pages-table-shell-context-live-20260507.png" />
</Frame>

*The table close-up makes the row-level handoff clearer: development fix, SEO update, or content work.*

## Inputs and outputs

| Area    | What it includes                                                               | Example                                                                         |
| ------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Inputs  | Site<br />brand<br />strategic prompts<br />clusters<br />source candidates    | Brand name<br />non-branded prompts<br />competitors<br />owned URLs            |
| Signals | Scores<br />answers<br />sources<br />citations<br />web health<br />gap types | AVI<br />citation rate<br />source visibility<br />urgency<br />GEO opportunity |
| Outputs | Next priority and reporting sentence                                           | Technical fix<br />content brief<br />source work<br />weekly report note       |

## What should you look at first?

<Steps>
  <Step title="1. Summarize the state in one sentence">
    Replace “the score is low” with a cause-based sentence such as “official citations are weak for non-branded comparison prompts.”
  </Step>

  <Step title="2. Split the cause into four work types">
    Move technical blockers to Site Audit. Send question gaps to Prompt Analysis, source gaps to Citation Tracking, and content gaps to Content Factory.
  </Step>

  <Step title="3. Choose one next action">
    Turn the signal into one next action: a cluster update, page edit, FAQ, source task or weekly report note.
  </Step>
</Steps>

## Main cards, tabs, or metrics

| Area           | What to inspect                                                   | Decision standard                         |
| -------------- | ----------------------------------------------------------------- | ----------------------------------------- |
| Current signal | Score<br />card<br />answer<br />source<br />or page issue        | Baseline and week-over-week movement      |
| Gap            | Weak prompt<br />source<br />content<br />or competitor advantage | Why the team should act                   |
| Priority       | Urgency<br />GEO opportunity<br />AIO fit<br />SEO foundation     | What should happen this week              |
| Next action    | Content<br />technical<br />source<br />or report work            | Whether it can have an owner and deadline |

## Practical use cases

| Situation                    | What to do with this feature                            | Output                            |
| ---------------------------- | ------------------------------------------------------- | --------------------------------- |
| Before a customer meeting    | Find weak prompt sets and source gaps.                  | One-page diagnostic summary       |
| Internal execution meeting   | Choose this week’s content, technical, or source tasks. | Ticket or content brief           |
| Executive/customer reporting | Explain cause and next action, with the score.          | Weekly report or export           |
| SEO/GEO strategy             | Read SEO foundation and AI answer signals together.     | Strategy Map and keyword clusters |

## How to explain it in meetings

“This feature shows how far the brand travels inside AI search answers and what content, source, or technical action should happen next.” Avoid customer names, real URLs, and internal KPIs in public documentation.

## FAQ

### Does this feature complete the decision by itself?

No. HaloX features are connected. A signal in Site Audit should move into Site Audit, Strategy Map, Content Factory, Citation Tracking, or weekly reporting.

### Do scores map directly to business results?

Most GEO metrics are leading indicators. Mentions and citations usually move first; traffic, branded search and conversion prompts are checked later.

## Related guides and concepts

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/en/introduction/quickstart">Start the first 30-minute workflow.</Card>
  <Card title="Reading scores" icon="chart-line" href="/en/guides/reading-scores">Translate metrics into meeting language.</Card>
  <Card title="GEO glossary" icon="book-open" href="/en/glossary/index">Understand GEO, AVI, citation rate, and source visibility.</Card>
  <Card title="Reports" icon="file-chart-column" href="/en/guides/reports">Turn movement into reporting language.</Card>
</CardGroup>

## How to read the score cards: SEO, GEO, and Performance

| Score                       | What it means                       | Basis                              | Example reading                                                              |
| --------------------------- | ----------------------------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
| SEO Score                   | Site health for search engines      | Site health score from the scan    | 80+ is healthy, 50-79 needs attention, below 50 is urgent.                   |
| GEO Score                   | AI-search readiness                 | AI readiness score                 | Combines crawler access, schema, content, trust, and freshness.              |
| Performance                 | Lighthouse performance score        | Shown when performance data exists | Weak performance can still hurt user experience even when SEO/GEO is strong. |
| Critical / Warning / Notice | Issue counts by severity            | Similar issue types are grouped    | Fix Critical first; treat Warning as next sprint candidates.                 |
| Crawled Pages               | Number of URLs included in the scan | Crawled URLs versus maximum pages  | Check whether the scan covered enough pages.                                 |

## The five AI readiness dimensions and weights

| Dimension     | Weight | Meaning                                                      |
| ------------- | -----: | ------------------------------------------------------------ |
| Accessibility |    20% | Whether AI and search crawlers can access the page           |
| Schema        |    20% | Whether structured data such as JSON-LD is present           |
| Content       |    25% | Whether title, body, and answer structure are readable       |
| Trust         |    20% | Whether author, company, source, and trust signals exist     |
| Freshness     |    15% | Whether content, maintenance, and infrastructure are current |

## Pages table and issue detail panel

| Item           | What it means                                                      | Basis                                                             |
| -------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------- |
| T/D/S          | Title, Description, and Schema status                              | Title 30-60 chars, description 70-160 chars, and schema presence. |
| Status Code    | URL response status                                                | 2xx is OK, 3xx redirect, 404 missing, other codes are errors.     |
| Word Count     | Page word count                                                    | Below 300 is treated as thin content.                             |
| Issues         | Issue count per URL                                                | Five or more issues should be prioritized.                        |
| Engine Impact  | Impact by ChatGPT, Gemini, Perplexity, Claude, and similar engines | Shows whether an issue is engine-specific.                        |
| Fix Difficulty | Expected effort to fix                                             | Use low, medium, high to sequence work.                           |

## If you need the service metric definitions

Terms such as `rank`, `search volume`, `trend`, `AI`, `PAA`, `Citation Rate`, `Share of Voice`, and `gap type` are explained in the [screen metrics glossary](/en/glossary/screen-metrics). Use it when a KPI on this page needs a plain-language definition and a link back to the screen where it appears.