Sample report

What the report actually says.

A real scan, published in full rather than described. Every number below came out of the analyzer on 29 June 2026, scanning example.com — a domain nobody owns commercially, so nothing is redacted and you can re-run it yourself.

Overall readiness

29/100

Not Ready

Commerce
0%
Content
6%
AI bot accessibility
54%
Technical readiness
38%

Scanned 29 June 2026 · completed in 1030ms

Category breakdown

Where the 29 came from.

Each category is scored on its own applicable checks, then multiplied by a fixed weight. Accessibility scores 75 here and moves the total by less than agent tools scoring 8 — that is the weighting doing its job, not a bug. See the method →

Category Weight Score Pass Warn Fail
AI Agent Tools & Action Surfaces 0.18 8 1 1 18
Content Discoverability 0.15 26 5 2 16
Structured Data & Schema Markup 0.12 17 0 3 6
Technical Readiness & Security 0.09 38 6 4 11
AI Crawler Permissions 0.08 54 2 24 0
Meta Tags & AI Head Elements 0.08 18 3 1 15
Semantic HTML & Content Structure 0.08 54 5 3 4
Generative Engine Optimization 0.08 19 1 1 6
Accessibility & Agent Interaction 0.07 75 7 1 2
Answer Engine Optimization 0.07 20 1 0 4

Findings

Two of them, in full.

Every failing check in the delivered report carries the same four parts: what was found, why it costs you, what to do, and the code to do it with. No check says "improve your structured data" and stops.

1.1

llms.txt exists

Critical
Found
HTTP 404
Impact
llms.txt is the primary entry point for AI agents discovering your site. Without it, models must crawl the whole site blindly, often missing key pages and answering from partial information.
Fix
Create /llms.txt at the site root in markdown: an H1 with your site name, a blockquote summary, then H2 sections linking your key pages with descriptions.
llms.txt markdown
# Your Site Name

> Your site provides X for Y. It covers A, B, and C.

## Pages
- [Home](/): Main landing page
- [About](/about/): Company information

## Resources
- [Sitemap](/sitemap.xml): Full URL list
- [RSS](/rss.xml): Content feed
3.3

Organization schema

High
Found
No JSON-LD blocks found
Impact
Without Organization schema, AI agents cannot confidently attribute content to your brand or show your logo in generated answers. The organization becomes anonymous in AI results.
Fix
Add Organization JSON-LD to the homepage head. Name, url, and logo at minimum; sameAs links and contactPoint if you have them.
index.html json-ld
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "sameAs": [
    "https://linkedin.com/company/yourcompany"
  ]
}

Machine-readable

The same report as JSON.

Every scan is available in the shape below, so readiness can be tracked in your own BI stack rather than screenshotted from a dashboard.

scan-result.json json
{
  "url": "https://example.com",
  "overallScore": 29,
  "scoreTier": "not-ready",
  "readinessVitals": {
    "commerce": 0,
    "content": 6,
    "botAccessibility": 54,
    "technical": 38
  },
  "categories": [
    {
      "id": "agent-tools",
      "weight": 0.18,
      "score": 8,
      "passCount": 1,
      "warnCount": 1,
      "failCount": 18
    }
  ],
  "topFails": [
    {
      "id": "1.1",
      "title": "llms.txt exists",
      "status": "fail",
      "priority": "critical",
      "displayValue": "HTTP 404"
    }
  ]
}

Is this a real report?

Yes. Every score, count, and finding on this page comes from an actual scan of example.com run on 29 June 2026, and the scan completed in about one second. We publish it against a domain nobody owns commercially so no client data is exposed and anyone can re-run the same scan and compare.

What do I get that this page does not show?

The delivered report lists every failing and warning check in all ten categories with its own impact statement, fix, and copy-paste code, ordered by priority rather than by category. This page shows the summary, the category table, and two findings in full.

Does a low score mean the site is badly built?

No. example.com is a valid, fast, accessible page. It scores 29 because it publishes almost nothing machine-readable: no llms.txt, no structured data, no agent action surfaces. Agent readiness is a separate axis from web quality, which is the reason most well-built enterprise storefronts still score low on a first scan.

Run the Free Audit

Same analyzer, your domain, report by email in minutes.