Free AI visibility check. One page, all four dimensions. No signup, nothing installed. Check a page →
Home/Review & Roadmap

Sample report

What a Roadmap actually looks like

A worked example for a fictional field service business, Fernway, scoring 52 before and 91 after.

Updated 5 min read

Interactive sample

Click through a real report.

This is a real report. It opens on the executive summary — the verdict, the four scores and what to do first, in order and in plain words. Beside it sit the full summary and a tab for each pillar, with the technical detail for whoever is doing the work.

aivisibilitytoolkit.com/get-cited/faq-schema/ FIRST RUNAFTER THE FIX 75 / 10093 / 100

Executive summary

Recommended, not yet Agent Ready.Agent Ready on all four.

AI can read this website and describe it accurately. It cannot yet reach your live information or complete an action — which is where the next wave of enquiries is going.AI can now find you, describe you accurately, reach your live information and complete an action. All four pillars sit above the threshold where assistants act with confidence.

7593 AI Visibility Score™ RecommendedAgent Ready

Offering visibility the primary result

Two of your four services will not get recommended. The domain foundation scores 24 of 33 — fixing that lifts all four at once. After that, refrigeration needs its own work.

Across the whole site — the roll-up

Discoverability Find you H7495
Comprehension Describe you H8496
Actionability Use you A5188
Agent readiness Buy from you A7091

61 — Recommended 81 — Agent Ready What the levels mean

What to do, in order

  1. Publish an llms.txt. One file, and the biggest single gain available here. +6 points · 15 min
  2. Write alt text for eleven images. Lifts Discoverability and Comprehension together. +6 points · 40 min
  3. Add FAQ schema to seven answers you already wrote. No new content needed. +8 points · 30 min

All three are set out step by step in the Roadmap. Full technical detail is in the tabs beside this one.

What changed

  1. llms.txt published. Use you moved 51 to 88.
  2. Alt text written for eleven images. Find you and Describe you both moved.
  3. FAQ schema added to seven answers. Describe you moved 84 to 96.

Six changes, about two hours of work. Every pillar moved.

7495Find you
8496Describe you
5188Use you
7091Buy from you
CRITICALEleven pictures have no description, so AI cannot tell what is in them11 <img> elements missing alt attributes · affects Find you and Describe youFix guide
CRITICALNothing tells an AI which pages of yours matter mostNo /llms.txt at the domain root · largest single deduction on Use youFix guide
WORTH ITYour page title gets cut off before the useful part<title> is 84 characters; 60 is the practical limitFix guide
74

Find you

Can AI find you?

PASSINGYour business name and structure are stated in a form AI can readJSON-LD present · Organization · exactly one <h1>
CRITICALEleven pictures have no description AI can read11 <img> elements missing alt attributesFix guide
WORTH ITYour page title gets cut off before the useful part<title> is 84 characters; 60 is the practical limitFix guide
PASSINGNothing is blocking AI from reading your websiterobots.txt permits all known AI user-agents · sitemap.xml fresh
84

Describe you

Can AI describe you correctly?

PASSINGYour page already answers questions in the shape AI looks for9 headings phrased as questions · good retrieval chunking
PASSINGThere is enough real writing here for AI to work with1,840 words · <ul>, <ol> and <table> present
CRITICALYou answer seven questions but have not labelled them as answersNo FAQPage or Question schema despite 7 question headingsFix guide
WORTH ITYour own chatbot has no map of your website to work fromNo /llms.txt for retrieval scopingFix guide
51

Use you

Can AI use your services?

CRITICALNothing tells an AI which of your pages matter mostNo /llms.txt at the domain rootFix guide
CRITICALNothing shows when this was last updated, so it may be treated as staleNo <time>, datetime attribute or dateModified in schemaFix guide
WORTH ITYour contact details only exist inside a form, so AI cannot read themContact info behind a form; no tel: or mailto: in the markupFix guide
PASSINGYour content is visible even when scripts do not runServer-rendered HTML · sitemap.xml present and current
70

Buy from you

Can AI buy from you?

PASSINGYour business identity is stated with a verifiable addressOrganization schema with PostalAddress
CRITICALYour prices are pictures, so software cannot read or compare themPrice values rendered in <img>, absent from the DOMFix guide
WORTH ITYour terms are written out but not labelled, so agents must guessNo OfferShippingDetails or MerchantReturnPolicyFix guide
PASSINGYou use yourself the same thing everywhere, which builds confidenceConsistent name string across schema, title and footer

What changed. Alt text written for all eleven images, FAQPage schema added, llms.txt published, title cut to 54 characters, a machine-readable date added, and prices moved out of images into text. Six changes, about two hours of work, and every pillar moved.

How the AI Visibility Score™ is built. Twenty-one weighted signals, each mapped to the dimensions it affects — a missing alt attribute costs Discoverability and Comprehension together, a missing llms.txt costs Actionability hardest. Every weight is published, so you can check our arithmetic. The full rubric

Worked example from our own guide page, run before and after the fixes. Not a customer result and not a promise — your website will move by whatever your own gaps are worth.

AI systems evolve rapidly. Every report reflects the standards and best practices current at the time of assessment, and carries the date it was run. We publish rubric changes in the changelog.

The rubric was written by Virtual Planet, who build AI, automation and agentic systems — which is how we knew to score the last three pillars at all.

The starting score

Fernway ran the free checker on their pricing page and scored 52/100.

Every report opens with the same four-pillar scorecard, so before and after are directly comparable.

PillarBeforeAfter
Find you38%91%
Describe you44%88%
Use you29%84%
Buy from you21%79%

And beneath it, the metric breakdown the score is built from:

MetricBeforeAfter
Machine-readable9 / 2929 / 29
Answer-shaped5 / 2724 / 27
Reachable5 / 2525 / 25
Trustworthy8 / 1915 / 19
WHAT A VISITOR SEES marked up WHAT A MACHINE READS "@type""Organization" "name""Your business" "address""Sydney NSW" "openingHours""Mo-Fr 09:00"

Section 1 — Your structured data

The Roadmap includes a complete block, written from their real content, with a note on where it goes.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://fernway.co/#org",
      "name": "Fernway",
      "url": "https://fernway.co",
      "description": "Quoting and invoicing software for field service crews under ten people.",
      "email": "[email protected]",
      "sameAs": ["https://www.linkedin.com/company/fernway"]
    },
    {
      "@type": "Service",
      "name": "Job quoting software",
      "provider": { "@id": "https://fernway.co/#org" },
      "areaServed": { "@type": "Country", "name": "Australia" },
      "offers": {
        "@type": "Offer", "price": "49", "priceCurrency": "AUD"
      }
    }
  ]
}
</script>

Where this goes: layout/theme.liquid, immediately before the closing </head> tag.

Section 2 — FAQ schema from your own page

We read the prose on the page and finds the questions already being answered, then structures them. Nothing is invented.

{
  "@type": "Question",
  "name": "Do you charge per user?",
  "acceptedAnswer": {
    "@type": "Answer",
    "text": "No. Fernway is one flat price per crew regardless of how many
             people use it. A three-person crew and a nine-person crew pay the same."
  }
}

Source: paragraph 3 of your pricing page — "no matter how big your team gets, the price stays the same." Reworded into a direct answer.

Section 3 — Titles and metas

PageBeforeAfter
/pricingPricing - Fernway Software Solutions AustraliaFernway pricing — flat rate, no per-seat fee
/quotesHow It WorksHow to quote a job in five minutes \Fernway
/aboutAbout UsAbout Fernway — Orange NSW since 2019

Section 4 — Your llms.txt

Written from the actual sitemap, with real descriptions rather than a template.

# Fernway

> Quoting and invoicing software for field service crews under ten people.
> Flat price per crew, no per-seat fees. Australian owned, Orange NSW, since 2019.

## Core pages

- [Pricing](https://fernway.co/pricing): all plans in AUD, no per-seat fees
- [How quoting works](https://fernway.co/quotes): the four-step on-site flow
- [Integrations](https://fernway.co/integrations): Xero, MYOB, Stripe

## Optional

- [Changelog](https://fernway.co/changelog): release history

Section 5 — The fix order

Because doing all of it at once is how things get half-done.

  1. robots.txt — five minutes, unblocks everything else
  2. Organization schema in theme.liquid — ten minutes, site-wide effect
  3. FAQ schema and visible copy on /pricing — thirty minutes
  4. Titles across nine pages — twenty minutes
  5. Alt text on 23 images — an hour, do it while listening to something
HONEST NOTE

The "after" scores above are what the same rubric returns once the changes are live. They are not a promise about mentions — no tool can make that promise, and any that does is selling you something it cannot deliver.

Take this to your assistant

Paste it into ChatGPT, Copilot, Claude or Gemini and apply it to your own website.

Nothing is sent anywhere. The text is copied to your clipboard.