AI Visibility Technical-Readiness Scan
No signup · 84-point rubric
Check your site’s technical readiness.
This runs a published 84-point checklist authored by Cleland & Co. 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; Cleland & Co. 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.
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.
Discoverability files & presentation
9Root sitemap.xml with at least one URL, and a limited check that configured crawler agents are not blocked at the site root when robots.txt was fetched. llms.txt, a missing robots.txt, FAQPage type, and Open Graph tags are reported rather than scored. This does not test full robots semantics, indexing, citation, or answer inclusion.
Reviews & listingnot scored
5Needs an external listing data source, so a single page fetch cannot score it. This scan does not call a listing API. Listed in the 84-point rubric, but left out of every score.
Questions
Asked and answered.
- What does the AI Visibility Technical-Readiness Scan actually check?
- It fetches the page you submit, plus robots.txt, llms.txt, and sitemap.xml at the site root. Scored: the page loads; a mobile viewport is set; structured data (JSON-LD) parses and names an Organization or LocalBusiness, with address, phone, and hours checked for a local business; the name or phone in that data matches the page; a usable sitemap.xml; whether robots.txt blocks the named AI crawlers at the root; and the title, description, canonical link, single h1, and page language. Reported but not scored: llms.txt, a missing robots.txt, FAQ markup, Open Graph title and description, and, when that optional check is on, Google's real-user speed data (Core Web Vitals) for the site. Not checked: it does not run PageSpeed Insights or Lighthouse, crawl or render the site, validate what the structured data means, test indexing, call a listing service, or ask any AI assistant anything.
- 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. When the optional speed-data check is on, the site origin (scheme and host, not the full path) is sent to Google's Chrome UX Report API so the result can show origin-level field Core Web Vitals. The submitted URL is not sent to PageSpeed Insights, a listing API, a crawl index, or an answer-engine API. Cleland & Co. 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.