Skip to content
ClelandCo

AI Visibility Scanner

No signup · 100-point rubric

Score your site's AI-visibility readiness.

Not a lead-magnet stub. This runs the same 100-point rubric as the paid work, and gaps come back ranked by the points they cost. It is also honest about what a single page fetch cannot measure.

Paste a URL. The scanner honors robots.txt and never stores your input.

What it measures

Seven signals. One published rubric.

Every point is accounted for. Anything a page fetch cannot score is left out of the total rather than counted against you, so the score is your share of what was actually measured — and a page that gets everything right scores 100.

  • Structured data

    25

    JSON-LD presence, LocalBusiness (or subtype) plus Organization, address, phone, opening hours.

  • AI answer-engine readiness

    25

    llms.txt, an explicit AI-crawler policy in robots.txt, sitemap.xml, FAQPage schema, and OG/Twitter cards.

  • Metadata hygiene

    15

    Title length, meta description length, canonical link, exactly one h1, and a lang attribute.

  • Reachability

    10

    Does the URL resolve at all? DNS, TLS, and redirects, checked before anything else.

  • Mobile-ready

    10

    A viewport meta tag. Without it, Google treats the page as desktop-only.

  • NAP self-consistency

    10

    The business name and phone in your schema have to actually appear on the visible page.

  • Reviews & listingnot scored

    5

    Needs Google Places data, so a single page fetch cannot score it. Left out of the total here and measured in the paid work.

Questions

Asked and answered.

What does the AI Visibility Scanner actually check?
Whether your own pages are readable by an answer engine: that the URL resolves, that a viewport meta tag exists, that JSON-LD is present and includes a LocalBusiness or Organization entity with an address, phone, and opening hours, that the name and phone in your schema also appear in the visible copy, that llms.txt, robots.txt, and sitemap.xml exist and permit AI crawlers, that FAQPage schema and Open Graph tags are present, and that the title, meta description, canonical link, single h1, and lang attribute are in order.
Is the score the same as my AI visibility?
No, and the distinction matters. This scores readiness — whether the pages you control can be read and understood. It cannot tell you whether ChatGPT, Perplexity, Google AI Overviews, or Claude actually name you when a buyer asks, because that takes repeated sampling of the engines themselves. A perfect 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.
Do you store the URL I enter?
No. The scan runs on request and the input is not retained. It honors robots.txt, follows a capped number of redirects, reads a bounded amount of the page, and gives up on a fixed deadline rather than holding a connection open.
What should I do with a low score?
Start with the gap at the top of the list — they are ordered by the points they cost, with the foundational ones breaking ties, so the first item is the one worth fixing first. Most of them are a few hours of work. If the foundations are fine and you still cannot tell whether the engines name you, that is the AI Visibility Lead engagement rather than a fix to this page.

After the scan

A score is a starting point, not an answer.

This checks whether your own pages are readable. It cannot tell you whether ChatGPT, Perplexity, Google AI Overviews, or Claude actually name you when a buyer asks — that takes repeated sampling across all four, which is what the AI Visibility Lead engagement does.