Skip to content
Metric VaultHelp Center
Open app

AI visibility checker

Free public tool that scores a page 0-100 on the eleven signals AI answer engines use to read, understand and cite it.

Last updated 2026-08-06

Summary#

The Free AI Search Visibility Checker fetches a page along with its robots.txt and llms.txt, scores eleven weighted signals that answer engines rely on, and returns a 0-100 readiness score with a ranked list of fixes. It runs at /free-tools/ai-visibility-checker with no account. Use it to find out whether ChatGPT, Perplexity, Gemini and Google AI Overviews are able to read and quote a page at all.

Purpose#

When someone asks an assistant about your category, the model either recalls your brand from training or retrieves a page about you in the moment. Both paths fail for the same boring reasons: an AI crawler is blocked in robots.txt, the page carries no structured data, or the content is too vague to quote.

Those causes are all visible in your HTML. This tool checks them in one pass so you stop guessing why the assistants name a competitor instead of you.

Overview#

The checker makes three fetches in parallel: the URL you entered, /robots.txt at the same origin, and /llms.txt at the same origin. It then evaluates eleven checks, each carrying a fixed weight, and turns the weights you passed into a percentage.

Every check reports a specific finding rather than a pass or fail alone. If crawlers are blocked, the detail names which ones. If your title is the wrong length, the detail gives the character count.

This is a readiness measure. It tells you whether an engine can use your page. It does not query any model and does not tell you whether an engine did name you. That measurement is Visibility Overview and Prompt Tracking inside the app.

Benefits#

  • Finds a blocked AI crawler in seconds, which is the single most common reason a site is absent from AI answers.
  • Shows the exact weight behind each signal, so you know which fix is worth most.
  • Gives a ranked fix list rather than a bare score.
  • Works on any public URL, including a competitor's, with no setup.
  • Needs no account, no card and no credits.

Use Cases#

  • Pre-launch check. Run it on a new page before you publish and clear the failed checks while the page is still easy to edit.
  • Diagnosing absence. An assistant recommends three rivals and never you. Run this first, because a Disallow: / for GPTBot explains it outright.
  • Competitor teardown. Run it on the rival the assistants keep naming and compare which signals they carry that you do not.
  • Post-migration verification. New CMS, new robots.txt. Confirm the AI bots are still allowed.

Requirements#

A public URL that returns HTML over HTTP or HTTPS. Nothing else. Private, loopback and internal addresses are refused, and a page behind a login cannot be read.

Permissions#

Anyone. No account, no plan, no role. There is one shared protection: an hourly fair-use limit counted per IP address across all the free tools. Normal use never reaches it.

Cost#

Free. Zero credits, and no account is charged because none is involved.

metricvaultai.com → Free tools → AI Visibility Checker

The page is at /free-tools/ai-visibility-checker. It is also the first card on the /free-tools index and the first item in the site navigation's Free tools dropdown.

Inputs#

FieldLabel / placeholderRequiredValid valueNotes
URLexample.comYesA bare domain or a full URLhttps:// is added for you if you leave it off. Any path works, so you can check one article rather than the homepage.

The form's helper line reads No signup · No credit card · Tests the live page, robots.txt and llms.txt.

Step-by-Step Guide#

  1. Open /free-tools/ai-visibility-checker.
  2. Type the page you want checked into the field marked example.com. Use the full path if you care about a specific article.
  3. Select Check AI visibility. The button changes to Checking… and the result area shows Reading the page, robots.txt and llms.txt, and scoring AI readiness….
  4. Read the score ring first, then work down the Priority fixes list from the top. It is already sorted by weight, so the first entry is the most valuable change you can make.

A run normally completes in a few seconds. Slow origins take longer because the tool waits on your server, not ours.

Reading the Results#

The score ring. A 0-100 number with a tier badge and a plain-language verdict:

ScoreBadgeVerdict line
80-100Strong AI readinessAI answer engines can read and cite this page well.
55-79Partly ready for AI searchSome signals are missing. The fixes below will help AI engines cite you.
0-54AI engines may struggle hereKey signals are missing, so AI engines may skip this page. Start with the fixes below.

Beside the ring, a heading reports <N> of 11 AI-readiness checks passed, and a How to read it strip repeats the bands as 80-100 strong, AI can cite you, 55-79 partly ready and 0-54 at risk.

What AI engines see. Every check, with a tick or a cross, the specific finding and its point value.

CheckWeightPasses when
AI crawlers allowed22No AI bot is disallowed from the whole site in robots.txt
Structured data (schema.org)20At least one JSON-LD block is present
Descriptive title tag12The <title> is 15 to 65 characters
Meta description12A meta description of 50 characters or more exists
Single clear H18Exactly one <h1>
Section headings8Two or more <h2>
Question / FAQ structure8FAQPage or Question schema is present
llms.txt file4/llms.txt returns a text response
Canonical URL3A rel="canonical" link is present
Open Graph tags3At least one og: property is present
Substantial content0300 words or more of visible text

The weights total 100. Substantial content is scored at zero weight on purpose: it is reported as information, not as a penalty, because word count alone is a poor proxy for quality.

The bots checked in robots.txt are GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, anthropic-ai, PerplexityBot, Google-Extended, CCBot and Applebot-Extended. A blanket User-agent: * with Disallow: / fails the check on its own.

Priority fixes. The failed checks, numbered and sorted by weight, each with the same detail text shown above. Work top down.

Examples#

Example

Example: A B2B software homepage scores 61 with Partly ready for AI search. Eight of eleven checks pass. The failures are Question / FAQ structure (8 points), llms.txt file (4) and Open Graph tags (3). The Priority fixes list puts the FAQ structure first. Adding an FAQ block with FAQPage schema and publishing an llms.txt moves the score to 73 without touching a single word of the marketing copy.

Example

Example: An agency runs the checker on a client site and scores 34. The top fix reads robots.txt blocks: GPTBot, ClaudeBot, PerplexityBot. A developer had pasted a "block the AI scrapers" snippet a year earlier. Removing three lines takes the score to 78.

Screenshots#

Screenshot
The AI Search Visibility Checker hero with the eyebrow "100% Free · No signup", the H1, the input showing example.com and the "Check AI visibility" button.
Screenshot
A completed result showing the score ring at 61, the "Partly ready for AI search" badge, the "<N> of 11 AI-readiness checks passed" heading and the How to read it band strip.
Screenshot
The "What AI engines see" card listing all eleven checks with tick and cross icons, detail text and the per-check point weights.
Screenshot
The "Priority fixes" card with the numbered, weight-sorted list of failed checks.

Tips#

  • Check an important article, not just the homepage. Assistants cite pages, and a homepage often scores well while the pages you want quoted score poorly.
  • Hover the small i marker beside a check name for a sentence on what the signal is and what a good result looks like.
  • The crawler check reads robots.txt at the origin, so it is the same answer for every page on the domain. Fix it once.
  • Run the same URL after each fix. The score updates immediately because nothing is cached.

Best Practices#

  • Clear the 22-point and 20-point checks before anything else. Crawler access and structured data are worth 42 of the 100 points between them.
  • Treat 80 as the working target rather than 100. Substantial content scores zero weight, so the highest achievable weighted total is reached without it.
  • Re-check after every template change. Structured data and canonical tags are usually template-level, so one deploy can move every page at once.
  • Pair this with AI citation audit on the same URL. This tool asks whether engines can read you, that one asks whether they have a reason to name you.

Common Mistakes#

  • Assuming the score predicts mentions. It measures readiness. A perfect 100 on an unknown site will not make ChatGPT recommend you tomorrow.
  • Blocking AI crawlers by accident. Boilerplate robots.txt snippets that block "AI scrapers" are common and cost 22 points instantly.
  • Reading the homepage score as the site score. Each run covers one URL.
  • Expecting the result to be saved. Nothing is stored for an anonymous run. Copy anything you need before you close the tab.

Limitations#

  • One URL per run. There is no crawl.
  • Readiness only. No model is queried, so the tool cannot report whether any assistant actually cites you.
  • Server-rendered HTML only. Content injected by JavaScript after load is not seen, so a heavily client-rendered page can under-score.
  • Question / FAQ structure in this tool requires FAQPage or Question schema. Question-shaped headings alone do not pass it here, although they do in GEO audit.
  • No history, no export, no scheduling and no Get Recommendations panel. Those are in-app features; see Free tools, no account needed.
  • A site that blocks our fetch returns an error rather than a score.

Troubleshooting#

SymptomLikely causeFix
That does not look like a valid domain. Try example.comThe value is not a plausible hostnameEnter a domain such as example.com or a full URL
Check failed: Could not fetch that page (HTTP 403). Check the URL and try again.The site blocks non-browser requestsTest a page without bot protection, or allow our fetch
Check failed: Could not fetch that page (no response). Check the URL and try again.The origin did not answerConfirm the site is up and the domain resolves
Score looks far too low for a good pageThe page renders its content with JavaScriptCompare with the page's raw HTML source; consider server-side rendering for key pages
Hourly fair-use limit reached (100 light-tool calls/hour)…Too many free-tool runs from one network in an hourWait for the next hourly reset

FAQs#

Is this really free? Yes. No account, no card, no credits, and no cap other than the shared hourly fair-use limit.

Does a high score mean ChatGPT will recommend me? No, and we will not claim it does. It means the mechanical barriers are gone. Whether an engine names you also depends on your authority and on what else it finds. Tracking actual mentions over time is Visibility Overview.

How is this different from the GEO Audit and the AI Citation Audit? Same fetch, different scoring sets. This tool scores the broadest set of eleven readability signals. GEO audit weights answer-shaped structure more heavily. AI citation audit weights concrete facts, author and date signals. Running all three on one URL is a reasonable use of five minutes.

Do you store the URL I check? An anonymous run is not attached to an account and is not written to any user history. See What data we store for what the platform stores in general.

Can I run this across every page on my site? Not from the free page. Site-wide checking is Site Audit in the app.

What does the paid product add on top of this? Repeat measurement. The app queries the models on a schedule, records whether you were named, compares you with competitors and alerts you when it changes. Start with What you get on Free.

See also

Was this article helpful?