Site analysis in the report

Read the technical findings and page-content coverage alongside the AI answers, without treating a site score as observed visibility.

Read the site analysis

Site analysis summarises the saved audit when available. SSPS describes standard readiness; SSPS+ describes applicable deep checks. Check page coverage and audit dates separately from the AI-answer date. A high score does not prove that an assistant fetched or cited the site.

The section also reports available access findings, such as citation-bot permissions and llms.txt presence. A file being present is an observation, not proof that an AI service uses it. Missing results are not measured zeroes.

The current report does not reproduce every old domain, homepage, link and performance slide. Open Site audit and Page audit for complete checks and PERF for the separate speed score.

Read page-content coverage

When available, the content breakdown groups eligible content pages by their saved classification: role, format, buyer stage, purpose and target action. It can continue onto further pages. Check the content-analysis date and the counted-page scope; redirects and excluded pages are not content coverage.

Citation columns use answers to questions without brand names. They describe observed citations of the classified pages, not a guarantee that adding a format will earn a citation. Unclassified pages and missing evidence should be checked in Page content analysis.

Choose and verify a fix

Follow the technical and content actions in the app. Review the affected URLs, evidence and priority before changing a page. A crawler receiving no response does not establish that the link is broken for every visitor. Where a manual verdict is available, inspect the destination first.

After implementation, rerun the appropriate audit. A site fix does not itself collect a new AI answer; later visibility must be measured separately.