DocsOpen app
Browse documentation
On this page

Site Health

Inspect website issues, understand Web and AEO scores, and choose changes with supporting page evidence.

A Site Health crawl captures pages from your website and analyzes their technical and content properties. Begin with Run new crawl, then review the crawl’s scope, progress and coverage.

Read the score with its coverage

Web summarizes determinate applicable website checks. AEO summarizes determinate checks across answerability, structure, evidence, machine readability, provenance, freshness and crawlability.

A higher score does not promise rankings, indexing or citations. “No observed blocker” means the captured evidence did not reveal a blocker; it is not confirmation that an engine indexed the page.

A Partial audit can still show a score. Read the accompanying coverage to understand how many pages were scored and which applicable checks remain unresolved.

Open the affected page

For a finding you intend to fix:

  1. Open its affected pages.
  2. Read the captured evidence and page classification.
  3. Check whether the issue applies to that page’s purpose.
  4. Compare with the current website before making changes if the crawl is old.

Page classification affects which checks apply. A product page and an editorial article do not have identical expectations. An unresolved page purpose remains unresolved.

Understand how results roll up

Page scores use determinate applicable checks. Checks marked unknown, error or partial do not receive passing credit. They remain visible in completion and coverage.

Crawl scores average finalized page scores in the selected cohort. A page with many checks does not automatically outweigh one with fewer checks. Avoid rebuilding the score from a filtered issue table.

Work through an issue

Use Ask agent on supported evidence screens, or Work on this on the related Action. Ask for a small, reviewable correction tied to the affected page.

For example: “Explain the confirmed issue on this page, distinguish it from unresolved checks, and prepare a fix brief for our developer.”

Check after implementation

After your team changes the site, declare the relevant Action implemented and run a later crawl when appropriate. Review the resulting checks and comparison scope. Different page coverage or incompatible conditions may limit what can be compared.