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 HaloXdiagnose → 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
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. |
Inputs and outputs
| Area | What it includes | Example |
|---|---|---|
| Inputs | Site brand strategic prompts clusters source candidates | Brand name non-branded prompts competitors owned URLs |
| Signals | Scores answers sources citations web health gap types | AVI citation rate source visibility urgency GEO opportunity |
| Outputs | Next priority and reporting sentence | Technical fix content brief source work weekly report note |
What should you look at first?
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.”
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.
Main cards, tabs, or metrics
| Area | What to inspect | Decision standard |
|---|---|---|
| Current signal | Score card answer source or page issue | Baseline and week-over-week movement |
| Gap | Weak prompt source content or competitor advantage | Why the team should act |
| Priority | Urgency GEO opportunity AIO fit SEO foundation | What should happen this week |
| Next action | Content technical source 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
Quickstart
Start the first 30-minute workflow.
Reading scores
Translate metrics into meeting language.
GEO glossary
Understand GEO, AVI, citation rate, and source visibility.
Reports
Turn movement into reporting language.
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 asrank, search volume, trend, AI, PAA, Citation Rate, Share of Voice, and gap type are explained in the screen metrics glossary. Use it when a KPI on this page needs a plain-language definition and a link back to the screen where it appears.