AI Visibility Technical-Readiness Scan
No signup · 100-point rubric
Check your site’s technical readiness.
This runs a published, ClelandCo-authored 100-point checklist and ranks gaps by its stated weights. The weights express implementation priorities; they are not validated predictors of answer inclusion, traffic, leads, or revenue.
Paste a public URL. The scan returns a result for this visit; ClelandCo does not keep a scan-results database. Hosting and rate-limit systems still see ordinary request metadata. Privacy details.
What it measures
Seven signals. One published rubric.
Every checklist point is accounted for. Anything a page fetch cannot inspect is left out of the denominator. A score of 100 means the page satisfies every measured item in this authored checklist—not that an answer engine will include or cite it.
JSON-LD entity fields
25Parseable JSON-LD plus an Organization or LocalBusiness type; local address, phone, and hours checks apply only when LocalBusiness is declared. Presence is not semantic validation.
Discoverability files & presentation
25A ClelandCo checklist for root llms.txt/robots.txt/sitemap responses, limited crawler-root policy, FAQPage type presence, and social metadata. It does not test visible FAQ parity, full robots semantics, indexing, citation, or answer inclusion.
HTML metadata checks
15Authored checks for title and description length, canonical link, h1 count, and lang attribute. Passing does not establish search quality.
Page fetch
10Whether this request returned a page through DNS, TLS, and redirects. One successful fetch is not an uptime test.
Viewport configuration
10Presence of a viewport meta tag. This does not test responsive layout, touch targets, rendering, or mobile usability.
Visible/schema agreement
10Any business name or phone found in JSON-LD is compared with text extracted from this HTML response. A missing schema field is not treated as a visible match.
Reviews & listingnot scored
5Needs an external listing data source, so a single page fetch cannot score it. Left out of this checklist total.
Questions
Asked and answered.
- What does the AI Visibility Technical-Readiness Scan actually check?
- It fetches one submitted public HTML response plus root robots.txt, llms.txt, and sitemap.xml paths. The authored checklist looks for a successful page response, viewport configuration, parseable JSON-LD and an Organization or LocalBusiness type; address, phone, and hours fields apply only to LocalBusiness. It compares any schema name or phone it finds with extracted page text; checks selected discovery-file responses, literal root blocks for configured crawler names, FAQPage type presence, and social metadata; and applies authored title, description, canonical, h1, and lang checks. It does not render the page, validate schema meaning, compare visible FAQs with schema, implement a complete robots standard audit, test indexing, or test answer-engine readability.
- Is the score the same as my AI visibility?
- No, and the distinction matters. This scores readiness—evidence exposed by the pages you control. It does not ask ChatGPT, Google, or any provider whether they name the business, so it cannot tell you whether any assistant actually names the business. A perfect readiness score is a foundation, not an outcome.
- How is the 0–100 calculated?
- As your share of the weight that was actually measured. Anything a single page fetch cannot score — reviews and Google Business Profile data, for instance — leaves both sides of the fraction rather than being counted against you, so a page that gets everything measurable right scores 100 and a site that does not load scores 0. Gaps come back ranked by the rubric points they cost.
- What data does the scanner process?
- The submitted URL is fetched to produce this result. ClelandCo does not keep a scan-results database. Rate limiting and hosting logs still process ordinary request metadata. See the privacy notice on this site for what is stored and for how long.
- What should I do with a low score?
- Start with the first gap: findings are ordered by lost rubric weight, with foundational items breaking ties. Verify the recommendation against your actual stack before changing production code. If the site foundations are sound but you still cannot tell whether answer engines name the business, that is a measurement problem for the AI Visibility Measurement, not another page-readiness fix.
After the scan
A score is a starting point, not an answer.
This checks technical evidence on one public page. It does not ask ChatGPT, Google, or any provider whether they name the business. AI Visibility Measurement is a separate service and is still in live-provider validation.