Salyant Signal logoSalyant SignalWebsite audit tool ↗
Illustrative example · AI SEO audit

What a useful website audit report should show.

This sample demonstrates the structure of a Salyant Signal report: what was checked, what the page evidence showed, why a finding matters and what a practical next step could look like.

Example data only. This page is synthetic. It does not represent a real business, a real website scan, a customer result, an actual score or a measured improvement. The example findings are illustrative and should not be interpreted as an audit of any live domain.
Sample overview

Search readiness summary

Overall diagnostic score
72/100

Illustrative number only

Technical SEO
78/100

Illustrative number only

Answer readiness (AEO)
69/100

Illustrative number only

AI discovery signals (GEO)
68/100

Illustrative number only

Example findings

Evidence, impact and next steps

High priority · Technical SEO

Important service page has a generic title

Observed evidence (illustrative): The page title describes the business generally and does not identify the service or audience shown in the page content.

Why it matters: A descriptive title helps visitors and search systems understand the page topic. It also makes the result more distinguishable from other pages on the same site.

Recommended next step: Draft a concise page-specific title that reflects the actual service, then check it against the visible H1 and page content before release.

Medium priority · AEO

Key buyer question is not answered directly

Observed evidence (illustrative): The page discusses the service but does not directly answer a common question about who it is for or what is included.

Why it matters: Clear, complete answers improve usability and make important information easier to understand and quote accurately.

Recommended next step: Add a concise, factual answer near the relevant section, include necessary qualifications and link to the detailed service scope.

Medium priority · GEO / structured data

Structured data needs a content-parity check

Observed evidence (illustrative): A schema description appears broader than the claims visible on the page.

Why it matters: Structured data should accurately represent visible page content. A mismatch can create confusing or misleading machine-readable information.

Recommended next step: Align the structured data with what the page visibly states, validate the JSON-LD and retest after deployment.

A useful report should separate signal from certainty

What the sample does not claim

An audit score is a diagnostic summary, not a Google ranking. A technical check cannot confirm that a page is indexed. AI-crawler access is not proof that an assistant will cite a page. Recommendations are not implemented changes.