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
Site Audit scans a domain or URL to answer a practical question: can search engines and AI systems read, understand, and cite this site? GEO does not start with more content. It starts with crawlability, structured data, accessible HTML, performance, and clear page meaning.
Where it is in the app
| Item | Detail |
|---|---|
| App menu | Site Audit |
| Main tabs | Overview, Issues, Pages |
| Main actions | New scan, PDF download, View all issues, View improvement guide |
| Core scores | SEO, GEO, Performance |
| Typical signals | Crawl status, AI accessibility, structured data, JS dependency, page count |
How to read it
1. Select the latest completed scan
Failed or partial scans usually mean crawlability, access control, rendering, or server response issues.
2. Split SEO, GEO, and performance
SEO covers search readiness, GEO covers AI-source readiness, and performance affects crawl efficiency and user experience.
3. Fix critical issues first
Critical AI accessibility, rendering, schema, LCP, or TBT issues can block citation potential.
4. Use the Issues tab by severity and type
Group related SEO, GEO, and performance issues instead of fixing rows one by one.
Common issue types
| Issue | Why it matters | Typical fix |
|---|---|---|
| AI accessibility | AI crawlers cannot use blocked or unreadable pages as sources. | Check robots, firewall, server response, rendering |
| Missing structured data | AI systems need stable meaning and entity signals. | Add Article, FAQPage, Organization, Product, or HowTo schema |
| JavaScript dependency | Critical content may not appear in static HTML. | Use SSR/SSG and expose core copy in HTML |
| Poor performance | Slow pages reduce crawl efficiency and UX. | Improve LCP/TBT, images, unused JavaScript |
| Duplicate or weak metadata | Engines struggle to distinguish page purpose. | Fix title, description, canonical, headings |
Meeting-based use cases
| Customer situation | What to check first | Why it matters |
|---|---|---|
| B2B SaaS needs SEO recovery | Titles, descriptions, canonicals, categories, tags, internal links | If the core search topic is broken, recover SEO before expanding GEO. |
| Enterprise newsroom or official site | AI accessibility, schema, FAQ/fact-sheet structure, HTML body | Many official assets can still fail if they are not citation-ready. |
| Regulated/platform service | Bot access, trust/policy pages, comparison/FAQ structure | Trust and before-signup questions need official evidence. |
| Local/multi-location business | Branch URL structure, LocalBusiness schema, consistent hours/address | Local recommendation answers depend on consistent branch facts. |
| Global/English expansion | English pages, hreflang, SSR/CSR, external sources | Models and locales can use different source pools. |
How to explain the feature
Do not present Site Audit as only a score check.“Site Audit checks whether AI systems can use your pages as source candidates. Even strong content may fail if accessibility, structured data, rendering, or metadata are weak.”Turn findings into either developer tickets or content fixes.