01
Search Readiness
Technical and on-page signals that help search engines discover, crawl, index, and understand the site. This contributes to the Website Visibility Score.
Methodology
A website score should be explainable.
The Website Visibility Score is a diagnostic measurement of observable website signals. It shows what was checked, what was found, and where improvement may be useful.
What we measure
One score, two drivers.
Search Readiness and AI Readiness determine the Website Visibility Score. Customer Trust and Actionability remain separate findings so owners can improve the business experience without confusing those improvements with a search or AI visibility guarantee.
02
AI Readiness
Crawler access, clear business information, and machine-readable structure that help AI-search systems understand the website. This contributes to the Website Visibility Score.
03
Customer Trust
Signals such as attributable reviews and clear business identity that help visitors evaluate credibility. Reported separately; not score-driving.
04
Actionability
Clear contact, booking, quote, or purchase paths that help visitors take the next step. Reported separately; not score-driving.
Evidence before opinion
AI can explain the evidence. It does not invent the score.
The scoring system uses deterministic, versioned checks. AI can improve the clarity of explanations and recommendations, but verified scoring data remains authoritative.
✓
Observable checks
Findings are tied to evidence identified on the website.
Findings are tied to evidence identified on the website.
✓
Versioned scoring
Methodology changes can be tracked instead of silently rewriting history.
Methodology changes can be tracked instead of silently rewriting history.
✓
Same scoring truth
The public analyzer and internal technical workflow use the same deterministic scoring foundation.
The public analyzer and internal technical workflow use the same deterministic scoring foundation.
Coverage
Analyze the website as a site.
Website-level analysis starts with discovery rather than assuming one page represents everything. Signals such as robots.txt, XML sitemaps, and internal links help establish the relevant page set. The public analyzer and internal technical workflow use the same eligible scored page set, up to the published page cap.
Understand site structure.
Identify relevant URLs, sitemap signals, and page relationships so the analysis has website-level context.
Go deeper when implementation work begins.
MSQ2I can use the same site-wide evidence to produce detailed repair guidance and implementation planning without changing the public scoring truth.
What the score cannot promise
Diagnosis is not a ranking guarantee.
Search engines and AI systems use complex systems outside our control. A strong score means the website performs well against the checks included in the current methodology. It does not guarantee a particular ranking, AI citation, traffic level, lead volume, or revenue outcome.