Illustrative number only
What a useful website audit report should show.
A good report turns diagnostic output into a decision: what was observed, where the evidence came from, why a buyer or search system could care, and which action should be considered first.
Search readiness summary
The summary is intended to give an owner a fast orientation before they review page-level evidence. The numbers below are deliberately synthetic.
Illustrative number only
Illustrative number only
Illustrative number only
Different signals answer different questions
Evidence, impact and next steps
A finding should be specific enough to discuss with a web or content team, but it should not pretend that a diagnostic signal proves a ranking, indexing or commercial outcome.
Important service pages use overlapping titles
Observed evidence (illustrative): Two core service pages begin with very similar title language, even though their visible content describes different services and audiences.
Why it matters: Distinct page titles help visitors and search systems tell the pages apart. Overlap can weaken the clarity of the page's purpose in search results and browser tabs.
Recommended next step: Draft a separate, accurate title for each page around its actual service and intended buyer. Check that the title agrees with the visible H1 and page copy before publication.
Example page · /services/Owner · Website teamThe primary buyer question is answered too late
Observed evidence (illustrative): The page introduces the business and its capabilities, but the practical answer to who the service is for and what is included appears much further down.
Why it matters: Visitors should not have to search the page to understand whether an offer is relevant. A direct answer also makes important information easier for assistive systems to interpret accurately.
Recommended next step: Add a concise, qualified answer near the relevant section. Explain the audience, scope and important exclusions, then link to the detailed service description.
Example page · /advisory/Owner · Content leadMachine-readable claims need a content-parity check
Observed evidence (illustrative): A structured-data description appears broader than the service claims visible on the page itself.
Why it matters: Structured data should describe the same organisation, service and facts that a visitor can verify. A mismatch can create uncertainty rather than clarity.
Recommended next step: Compare the schema with the visible copy, remove unsupported statements, validate the resulting markup and retest after deployment.
Example page · /about/Owner · Technical teamA key service claim lacks a nearby proof point
Observed evidence (illustrative): The page makes a broad delivery claim but offers little nearby context about the relevant experience, process or limitations.
Why it matters: Specific, supportable evidence helps buyers assess credibility and understand what a service actually involves.
Recommended next step: Add a genuine case example, verifiable credential or clear description of the delivery process. Keep client-sensitive details private and do not imply results that cannot be substantiated.
Example page · /services/Owner · Business leadA prioritised action plan
This is the type of decision summary a client can take into a planning discussion. It shows workstreams and responsibility, not an automated promise that changes will be made.
Separate service-page intent
Review titles, headings and page purpose across the most commercially important services.
Owner · Website teamEffort · ModerateBring buyer answers forward
Make scope, audience and qualifications easier to find without overstating what is offered.
Owner · Content leadEffort · SmallValidate visible and structured claims
Bring machine-readable descriptions into line with the facts and language a visitor can verify.
Owner · Technical teamEffort · ScopedHuman-reviewed evidence, controlled changes
For an agreed engagement, SALYANT validates the relevant evidence with the website owner, prioritises the work against business context, prepares changes for review, obtains approval before implementation and checks the result after release. Signal's dashboard remains read-only; it does not publish changes to a customer's CMS.
What this sample does not claim
An audit score is a diagnostic summary, not a Google ranking. A technical check cannot, by itself, confirm that a page is indexed. AI-crawler access is not proof that an assistant will cite a page. Recommendations are not implemented changes, and no ranking, traffic, lead or citation outcome is guaranteed.
What is intentionally not included in this public example
This sample does not expose the full diagnostic inventory, proprietary scoring weights, detection thresholds, crawl configuration, internal model prompts or automation logic. It is detailed enough to show the standard of evidence and decision support without publishing the underlying implementation methodology.
