Site Health
The Site Health section summarizes whether a crawled domain is ready to support grounded chatbot answers. It combines crawl quality, AI understanding, and source-evidence checks into one report.
Use it to decide whether ZENIA can rely on the current crawl as a knowledge source, and what to review first when answer quality or source coverage looks weak.
Location
Where to find it
Open a domain detail page and look for the Site Health panel. The report reflects the latest stored Site Health report for that domain. The Refresh button reloads the newest stored report; it does not start a new crawl by itself.
Readiness pillars
What the report measures
Site Health breaks readiness into three pillars so you can separate crawl issues from answer-quality and source-coverage signals:
| Pillar | What it means |
|---|---|
| Technical health | Issue-based crawl and metadata findings. This is a technical quality signal, not a search-engine ranking score. |
| AI understanding | Checks whether crawled pages contain enough usable text and structure to support grounded answers. |
| Retrieval evidence | Checks whether the content can provide useful source evidence for cited chatbot answers. |
Overall status
How to read the overall status
The headline decision tells you how safely the current crawl can support grounded chatbot answers:
| Status | Meaning |
|---|---|
| Ready | Crawled content, AI understanding, and source evidence are usable for grounded answers. |
| Needs attention | The domain is usable, but some checks should be reviewed to improve answer quality or reliability. |
| Limited | The website has material crawl, content, or source-coverage limits that may reduce answer quality. |
| Blocked | The inspected content is not currently sufficient for reliable grounded answers. |
Recommended actions
Recommended next actions
The Recommended next actions list prioritizes the highest-value fixes across technical health, AI understanding, and retrieval evidence. Start there first. Each action tells you the affected pillar and gives a short explanation of what should be reviewed.
Page readiness
Page readiness table
The Page readiness table shows per-page signals: formal technical findings, whether the page has usable AI content, and whether the page contributes useful source evidence. This is the fastest way to spot weak pages, empty pages, language gaps, or pages that do not help grounded answers.
Report lifecycle
When reports appear
Site Health is tied to crawl output. If you see No site health report yet, the latest crawl for that domain does not have a stored Site Health report yet. Re-running or completing a crawl updates the stored report. The panel can also show how many pages were inspected versus the total pages discovered, which helps explain partial coverage.
Availability
Plan availability
If the panel is locked, the feature is not available on the current subscription. In that state, you can still manage the domain normally, but Site Health insights remain hidden until the plan allows the feature.
Best practices
How to improve Site Health
- Fix crawl blockers first - pages that fail to load or expose little usable text limit every downstream AI check.
- Prefer clear page structure - strong headings, descriptive titles, and meaningful body text improve both AI understanding and retrieval evidence.
- Review weak pages - pages with little text or limited source evidence rarely help grounded answers.
- Re-crawl after material content changes - Site Health reflects the latest stored crawl, not unpublished or newly changed pages.