AI website readiness report

example.com

Checked 29 October 2026 Sample report. The site is made up, the arithmetic is real.

47 out of 100 Grade D

AI readiness score

Mostly invisible to AI Falling behind

An AI engine gets about half of what it needs from this page.

  • Crawlability 50%
  • Structure 56%
  • AI understanding 16%
  • Speed 60%
  • Security 100%
  • 3 Critical
  • 1 High
  • 3 Medium
  • 1 Low

All five categories, weighted: crawler access, structure, AI understanding, speed and security. This is the whole audit. The AEO, GEO and ChatGPT checkers read the same scan and lead with a narrower number cut from it.

How to get from where you are to AI ready

Where you are

Half unread

Two engines never reach the page, and the two that do cannot name the business.

Key improvements

  • Crawlability
  • AI understanding
  • Structure

8 findings, ordered by what each one is worth.

What you get

Ready to be quoted

An engine can lift a correct answer off the page and say where it came from.

Ready to strengthen your AI readiness?

A specialist reads the whole site rather than one page, works out which of your page types fail and why, then hands you the list in priority order. What you do with the list, and who does it, is yours to decide.

Get help

How each AI engine scores your site

  • 25/100

    ChatGPT

    At risk
    • Crawl access 0%
    • Structure 57%
    • Understanding 17%
    • Speed 60%
  • 39/100

    Claude

    At risk
    • Crawl access 40%
    • Structure 57%
    • Understanding 17%
    • Speed 60%
  • 58/100

    Gemini

    Falling behind
    • Crawl access 100%
    • Structure 57%
    • Understanding 17%
    • Speed 60%
  • 68/100

    Perplexity

    Gaps to close
    • Crawl access 100%
    • Structure 55%
    • Understanding 15%
    • Speed 60%

Derived from the same signals, not separately measured. Each engine weights them differently: Perplexity leans hardest on crawl access, ChatGPT and Claude on structure and understanding. Nobody queries the engines live.

Detailed analysis

  • 3.4s Load time
  • 86 KB Page size
  • 412 Words on page
  • Secure Connection

Web health

Speed, mobile and security: the basics that keep both people and AI crawlers from giving up.

  • 60

    Speed

    Mobile, real-user data

    Gaps to close
  • 92

    Mobile

    Responsive viewport declared

    Excellent
  • 100

    Security

    HTTPS end to end

    Excellent

Core Web Vitals

Google's loading, interactivity and stability scores, measured on mobile.

  • 3.4s

    Largest contentful paint

    Google wants this under 2.5s

  • 210ms

    Interaction to next paint

    Google wants this under 200ms

  • 0.08

    Cumulative layout shift

    Google wants this under 0.1

What to fix next

A list in priority order. The highest impact items are first.

  • 3 Critical
  • 1 High
  • 3 Medium
  • 1 Low
  1. Critical

    Let OAI-SearchBot and Claude-SearchBot read the site

    • Crawlability
    • Easy fix

    Why. OAI-SearchBot is disallowed, and that is the crawler that fetches pages to answer from, so ChatGPT never reaches this one. Claude-SearchBot is blocked from most of the site. Two of the four engines cannot fully read the page.

    Fix. Remove the two Disallow rules in robots.txt, or narrow them to the paths that genuinely should not be indexed.

  2. Critical

    Put the business name in the page text

    • AI understanding
    • Easy fix

    Why. The company name appears only inside the logo image. An AI reading the page has no name to attach an answer to, so it cites a competitor who does have one.

    Fix. Add the name in a heading or the first paragraph. Alt text on the logo helps, visible text helps more.

  3. Critical

    Say what you sell in the first paragraph

    • AI understanding
    • Medium effort

    Why. The headline is a slogan. The AI could tell this was a business and not a blog, and could not tell what kind of business.

    Fix. One sentence near the top, in the words a customer would use rather than the words the brand prefers.

  4. High

    Name the city or region you work in

    • AI understanding
    • Easy fix

    Why. No location appears anywhere in the visible text. Any question with a place in it will be answered with someone else.

    Fix. Put it in the text and in LocalBusiness structured data, not only in the footer address image.

  5. Medium

    Write a longer meta description

    • Structure
    • Easy fix

    Why. At 92 characters it is short enough that engines rewrite it, which means they choose how you are summarised rather than you.

    Fix. Between 140 and 155 characters, containing the business and what it does.

  6. Medium

    Add LocalBusiness and FAQPage markup

    • Structure
    • Medium effort

    Why. The structured data stops at Organization, WebSite and BreadcrumbList. Nothing on the page tells an engine where this business operates or answers a question it could quote.

    Fix. Add LocalBusiness with the address, and FAQPage on the questions you already answer in the copy.

  7. Medium

    Give the hero image width and height

    • Speed
    • Medium effort

    Why. The unsized hero is most of a 3.4s largest contentful paint. Slow pages lose crawlers part way through.

    Fix. Set width and height attributes and serve it at the size it is displayed.

  8. Low

    Add an llms.txt file

    • Crawlability
    • Easy fix

    Why. No engine has committed to reading it, so this is worth little today. It costs ten minutes and is trivially reversible.

    Fix. A Markdown file at /llms.txt listing your most useful pages with a line of context each.

Readiness breakdown

The shape of your AI readiness across the five factors that matter most. How each one is measured is on the methodology page.

CrawlabilityStructureUnderstandingSpeedSecurity
  • Crawlability 50%

    ChatGPT is blocked outright. Claude gets part of the site.

  • Structure 56%

    A machine can follow it. The structured data stops at the basics.

  • AI understanding 16%

    The page never says what the business does.

  • Speed 60%

    Read in time, but slower than it should be on a phone.

  • Security 100%

    Nothing to do here.

AEO against SEO

How ready you are for AI answers, next to how ready you are for classic search.

52

AEO

Answer engine optimization

You are reachable but not quotable. The page does not state the facts an answer would need.

86

SEO

Classic search optimization

Crawlability, speed and security. The fundamentals are sound.

Both derived from the same five checks: AEO from structure and understanding, SEO from crawlability, speed and security.

SEO basics

The on-page essentials that classic search and AI engines both rely on.

  • Core Web Vitals 67
    • Largest contentful paint: 3.4s
    • Interaction to next paint: 210ms
    • Cumulative layout shift: 0.08
  • Crawlability 50
    • 2 AI crawlers blocked or partly blocked
    • Sitemap found
    • No llms.txt file
  • Metadata 67
    • Page title, 54 characters
    • Meta description, 92 characters
    • Canonical tag present
  • Technical SEO 100
    • Headings run in order
    • One h1 on the page
    • Served over HTTPS
    • The page is indexable

Schema coverage

Structured data is the machine readable label AI uses to confirm who you are.

60%

Implemented 3

  • Organization
  • WebSite
  • BreadcrumbList

Missing 2

  • LocalBusiness
  • FAQPage

Strengths

  • Gemini and Perplexity are allowed to read your site
  • Valid structured data: Organization, WebSite, BreadcrumbList
  • Headings run in order with a single h1
  • Content is in the HTML and does not wait for JavaScript
  • HTTPS with a valid certificate
  • A sitemap is published at the site root

Your biggest opportunities

  • OAI-SearchBot is disallowed, so ChatGPT has none of this page to answer from
  • AI understanding is at 16 per cent
  • 4 of the five identity checks came back empty
  • Speed is at 60 per cent
  • 3 findings are marked critical and are worth doing before anything else

Frequently asked questions

The key concepts behind this report, in plain English.

Is this a real website?

example.com is a reserved domain used for documentation. The numbers are a worked example, chosen so the arithmetic matches what the engine actually produces.

Did you check my whole site?

No. We read the one page you gave us. Crawler access and security are site-wide by their nature, but structure and understanding are judged on that page alone, which is why the homepage is usually the one worth running.

How is each engine scored separately?

From the same signals, weighted for what that engine leans on. Perplexity leans hardest on crawl access; ChatGPT and Claude lean on structure and understanding between them. Nobody queries the engines live, and we say so rather than implying a measurement we did not take.

What is entity recognition?

We give one AI model your page text with no knowledge of your company, then ask it to name the business, the services, the products, the industry and the location. The ones it cannot name are the ones an engine cannot attribute an answer to.

Why is my score lower than I expected?

Almost always the same reason: the site reads well to a person who already knows the company, and says none of the plain facts a stranger would need. That is a writing problem, not an engineering one, which is good news.

Does my report stay private?

It sits at its own address, reachable by anyone with the link, which is what makes it shareable. Ask us and we take it down the same day, no reason needed. See the privacy policy.

One page is not the whole site

Everything above is free to act on, and most of it is writing rather than rebuilding. When the same problems run across a whole site, a specialist reads all of it and tells you what to change, in order.