Agent readiness report

case-track.com

What an AI agent can and cannot do on this site, measured by an unauthenticated crawl and scored against the published rubric.

Scanned 2026-09-06 · rubric v1.0.1 · scored as a general site · re-scan (results are cached for seven days)

What to fix first

Ranked by impact first, then by how cheap the fix is — the same ordering the engine uses.

1C4
Machine endpoints and agent manifests
High impact · High effort
Found API documentation link. A second machine surface — an OpenAPI spec or an MCP server — takes this to full marks.
2A4
llms.txt present
Medium impact · Low effort
Publish an llms.txt at the root: an H1, a one-line summary, then described links to your most useful pages. It is a text file and it takes an hour — the cheapest points on this rubric.
3D3
Policies discoverable
Medium impact · Low effort
Fix: no privacy policy linked; no terms page linked.
4A3
XML sitemap valid and referenced
Medium impact · Low effort
Fix: no sitemap.xml at the root; not referenced from robots.txt. A sitemap referenced from robots.txt is how a crawler discovers pages that are not linked from the homepage.
5A5
Bot user-agent HTTP health
Medium impact · Low effort
Your robots.txt welcomes these agents, but GPTBot received 429, ClaudeBot received 429 — the block is happening at your CDN or WAF, before robots.txt is ever read. Cloudflare in particular blocks AI crawlers by default on every plan. One setting change, and it is invisible until someone tests it.

Every check, with the evidence

No finding without evidence: each result shows what we actually captured during the crawl.

ADiscovery & access

A1Fail
robots.txt exists and parses
0/2
robots.txt returned 0. Serve it as a 200 with plain text.
What we captured
```
{
  "error": "fetch failed",
  "status": 0
}
```
A2Pass
Major AI crawlers allowed
6/6
What we captured
```
{
  "of": 6,
  "allowed": 6,
  "blocked": []
}
```
A3Fail
XML sitemap valid and referenced
0/3
Fix: no sitemap.xml at the root; not referenced from robots.txt. A sitemap referenced from robots.txt is how a crawler discovers pages that are not linked from the homepage.
What we captured
```
{
  "exists": false,
  "urlCount": 0,
  "referencedInRobots": false
}
```
A4Fail
llms.txt present
0/4
Publish an llms.txt at the root: an H1, a one-line summary, then described links to your most useful pages. It is a text file and it takes an hour — the cheapest points on this rubric.
What we captured
```
{
  "status": 0,
  "present": false
}
```
A5Partial
Bot user-agent HTTP health
1/3
Your robots.txt welcomes these agents, but GPTBot received 429, ClaudeBot received 429 — the block is happening at your CDN or WAF, before robots.txt is ever read. Cloudflare in particular blocks AI crawlers by default on every plan. One setting change, and it is invisible until someone tests it.
What we captured
```
{
  "probes": [
    {
      "name": "GPTBot",
      "status": 429,
      "ttfbMs": 476
    },
    {
      "name": "ClaudeBot",
      "status": 429,
      "ttfbMs": 90
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 393
    }
  ],
  "medianTtfbMs": 393,
  "edgeBlockingDespiteRobots": true
}
```
A6Partial
No hard interstitial
1/2
Detected: Cookie wall. An agent cannot dismiss a consent dialog or solve a challenge — whatever sits behind it is unreachable. Cookieless analytics removes the need for a banner entirely.
What we captured
```
{
  "markers": [
    "Cookie wall"
  ]
}
```

A7Pass

Server-rendered content parity

5/5

What we captured

{
  "ratio": 1,
  "rawTextLength": 15141,
  "renderedTextLength": 7343
}

BUnderstanding

B1Pass

JSON-LD present and valid

5/5

What we captured

{
  "pagesCrawled": 1,
  "pagesWithValidJsonLd": 1,
  "homepageHasValidJsonLd": true,
  "pagesWithInvalidJsonLd": 0
}

B2Pass

Correct schema types for the site type

5/5

What we captured

{
  "matched": [
    "FAQPage"
  ],
  "missing": [],
  "siteType": "other",
  "typesFound": [
    "Answer",
    "BreadcrumbList",
    "EntryPoint",
    "FAQPage",
    "ImageObject",
    "ListItem",
    "PropertyValueSpecification",
    "Question",
    "ReadAction",
    "SearchAction",
    "WebPage",
    "WebSite"
  ]
}

B3Partial
Semantic HTML structure
1/4
Headings and landmarks are how a machine builds an outline of the page. One h1, no skipped levels, and real main/nav/footer elements — all template-level fixes, applied once.
What we captured
```
{
  "problems": [
    "https://case-track.com: skipped heading level",
    "https://case-track.com: missing main, footer"
  ],
  "singleH1": 1,
  "allLandmarks": 0,
  "pagesCrawled": 1,
  "noSkippedLevels": 0
}
```

B4Pass

Meta and Open Graph

3/3

What we captured

{
  "goodTitles": 1,
  "pagesCrawled": 1,
  "uniqueTitles": true,
  "goodDescriptions": 1,
  "completeOpenGraph": 1
}

B5Pass

Clean text ratio

3/3

What we captured

{
  "perPage": [
    0.104
  ],
  "averageRatio": 0.104
}

B6Pass

Alt text coverage

2/2

What we captured

{
  "withAlt": 50,
  "coverage": 1,
  "contentImages": 50
}

B7Pass

Canonical and duplication hygiene

3/3

What we captured

{
  "hostVariants": [
    {
      "url": "https://www.case-track.com",
      "status": 302,
      "location": "http://www.mitratech.com/"
    },
    {
      "url": "http://case-track.com",
      "status": 302,
      "location": "http://www.mitratech.com/"
    }
  ],
  "pagesCrawled": 1,
  "selfConsistentCanonicals": 1
}

CActionability

C1Pass

Form usability

6.11/6.11

What we captured

{
  "forms": 1,
  "inputs": 1,
  "realSubmit": true,
  "unlabelled": 0,
  "wrongTypes": 0
}

C2Partial
Navigable link graph
2.44/4.89
Fix: 1 clickable element(s) that are not anchors — an agent cannot follow a div.
What we captured
```
{
  "anchors": 228,
  "genericLinks": 4,
  "genericRatio": 0.02,
  "hasBreadcrumb": true,
  "clickableNonAnchors": 1
}
```
C3Partial
Interactive element semantics
2.44/4.89
Fix: 1 element(s) act as buttons without being buttons. A div with a click handler is invisible to anything driving the page programmatically.
What we captured
```
{
  "realButtons": 3,
  "positiveTabindex": 0,
  "clickableNonButtons": 1,
  "keyboardTrapsTested": false
}
```
C4Partial
Machine endpoints and agent manifests
3.67/6.11
Found API documentation link. A second machine surface — an OpenAPI spec or an MCP server — takes this to full marks.
What we captured
```
{
  "found": [
    "API documentation link"
  ]
}
```
C5Not applicable
Commerce actionability
0/4
Not a commerce site; these points are redistributed across C1–C4.
What we captured
```
{
  "siteType": "other"
}
```

C6Pass

On-site search

3/3

What we captured

{
  "usesGet": true,
  "searchForm": true,
  "searchAction": true
}

DTrust & freshness

D1Partial
Transport security
3/4
Fix: 1 insecure subresource reference(s).
What we captured
```
{
  "hsts": true,
  "tlsValid": true,
  "mixedContentReferences": 1
}
```
D2Partial
Verifiable identity
2/4
Fix: no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.
What we captured
```
{
  "sameAsCount": 0,
  "contactDiscoverable": true,
  "hasOrganizationSchema": false
}
```

D3Fail

Policies discoverable

0/4

Fix: no privacy policy linked; no terms page linked.

What we captured

{
  "hasTerms": false,
  "siteType": "other",
  "hasPrivacy": false,
  "hasReturns": false,
  "hasShipping": false
}

D4Partial
Freshness signals
1/4
Fix: sitemap has no lastmod values; only 0% of sitemap URLs modified in the last 90 days. Staleness is a ranking signal for models deciding what to cite.
What we captured
```
{
  "sitemapUrls": 0,
  "withLastmod": 0,
  "visibleDates": true,
  "modifiedLast90Days": 0
}
```

D5Pass

Identity consistency

3/3

What we captured

{
  "title": "Mitratech | Empower Decisions. Elevate Outcomes.",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "Mitratech",
  "schemaName": "Mitratech | Empower Decisions. Elevate Outcomes."
}

D6Fail
security.txt
0/2
Publish /.well-known/security.txt with a Contact field and a future-dated Expires field. It is a five-line text file.
What we captured
```
{
  "status": 404,
  "present": false
}
```

D7Partial

Multi-page stability

2/4

Fix: 5 page(s) did not return 200: https://case-track.com/products/hq (404), https://case-track.com/products/aries/ (404), https://case-track.com/products/alyne/ (404), https://case-track.com/products/circa/ (404), https://case-track.com/products/leave/ (404).

What we captured

{
  "nonOk": [
    {
      "url": "https://case-track.com/products/hq",
      "status": 404
    },
    {
      "url": "https://case-track.com/products/aries/",
      "status": 404
    },
    {
      "url": "https://case-track.com/products/alyne/",
      "status": 404
    },
    {
      "url": "https://case-track.com/products/circa/",
      "status": 404
    },
    {
      "url": "https://case-track.com/products/leave/",
      "status": 404
    }
  ],
  "slowPages": 0,
  "pagesCrawled": 6,
  "consistentTemplate": true
}

64C

Discovery & access13/25

Understanding22/25

Actionability17.66/25

Trust & freshness11/25

Keep this report

Get the permanent link and the ranked fix list by email. One message, no list.

Want this fixed?

We audit in depth and implement the fixes — in your codebase or your CMS, scoped by architecture.

Request a full audit Book a call

Own this site?

This report and its leaderboard entry come from a public crawl. Prove you own the domain with an email address on it, and you can hide the report or publish it again yourself, in minutes.

Claim this site

To block future scans instead, disallow AgentFriendlyRankBot in your robots.txt — see how our crawler works.

Scan your own site

Same rubric, same evidence standard, about a minute.

Run a free scan →

Compare case-track.com with another site →

case-track.com

What to fix first

Machine endpoints and agent manifests

llms.txt present

Policies discoverable

XML sitemap valid and referenced

Bot user-agent HTTP health

Every check, with the evidence

ADiscovery & access

robots.txt exists and parses

Major AI crawlers allowed

XML sitemap valid and referenced

llms.txt present

Bot user-agent HTTP health

No hard interstitial

Server-rendered content parity

BUnderstanding

JSON-LD present and valid

Correct schema types for the site type

Semantic HTML structure

Meta and Open Graph

Clean text ratio

Alt text coverage

Canonical and duplication hygiene

CActionability

Form usability

Navigable link graph

Interactive element semantics

Machine endpoints and agent manifests

Commerce actionability

On-site search

DTrust & freshness

Transport security

Verifiable identity

Policies discoverable

Freshness signals

Identity consistency

security.txt

Multi-page stability

Keep this report

Want this fixed?

Own this site?

Scan your own site