Skip to main content
HaloX Features page thumbnail summarizing Site Audit: Site Audit: separate SEO issues from AI-readiness gaps as five cards

​
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

HaloX Site Audit Overview showing SEO, GEO and performance trends in the live app

Site Audit Overview screen

Use Overview to read SEO, GEO and performance trends first. In meetings, split development fixes, metadata work, and content-structure work from this screen.
HaloX Site Audit detail crop showing SEO, GEO, and OTS scores with the prioritized issue panel

Score summary and issue detail panel

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

HaloX Site Audit Pages table crop showing SEO and GEO scores with metadata status by URL

URL-level SEO/GEO diagnosis table

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

​
Inputs and outputs

​
What should you look at first?

1

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

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

3. Choose one next action

Turn the signal into one next action: a cluster update, page edit, FAQ, source task or weekly report note.

​
Main cards, tabs, or metrics

​
Practical use cases

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

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

​
The five AI readiness dimensions and weights

​
Pages table and issue detail panel

​
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. Use it when a KPI on this page needs a plain-language definition and a link back to the screen where it appears.