Agent readiness report

anypresence.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-05 · rubric v1.0.1 · scored as a content 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
No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.
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.
3D2
Verifiable identity
Medium impact · Low effort
Fix: no contact page or mailto link found; Organization schema has no sameAs links. sameAs links to a company profile are how a model corroborates that you are who the page says you are.
4D3
Policies discoverable
Medium impact · Low effort
Fix: no privacy policy linked; no terms page linked.
5A3
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.

Every check, with the evidence

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

ADiscovery & access

A1Partial
robots.txt exists and parses
1/2
Publish a robots.txt. A missing file leaves the site open by default, so nothing is blocked — but it also means crawlers get no sitemap reference and no explicit signal about AI agents.
What we captured
```
{
  "status": 404
}
```
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": 404,
  "present": false
}
```
A5Partial
Bot user-agent HTTP health
1/3
Your robots.txt welcomes these agents, but GPTBot received 406 — 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": 406,
      "ttfbMs": 591
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 249
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 143
    }
  ],
  "medianTtfbMs": 249,
  "edgeBlockingDespiteRobots": true
}
```
A6Pass
No hard interstitial
2/2
What we captured
```
{
  "markers": []
}
```

A7Pass

Server-rendered content parity

5/5

What we captured

{
  "ratio": 1,
  "rawTextLength": 10818,
  "renderedTextLength": 10514
}

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": [
    "Article"
  ],
  "missing": [],
  "siteType": "content",
  "typesFound": [
    "Article",
    "ImageObject",
    "Organization",
    "Person",
    "WebPage"
  ]
}

B3Pass

Semantic HTML structure

4/4

What we captured

{
  "problems": [],
  "singleH1": 1,
  "allLandmarks": 1,
  "pagesCrawled": 1,
  "noSkippedLevels": 1
}

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.136
  ],
  "averageRatio": 0.136
}

B6Partial
Alt text coverage
1/2
13 of 42 content images have no alt text. An agent cannot see the image; the alt attribute is the only description it gets.
What we captured
```
{
  "withAlt": 29,
  "coverage": 0.69,
  "contentImages": 42
}
```

B7Pass

Canonical and duplication hygiene

3/3

What we captured

{
  "hostVariants": [
    {
      "url": "https://www.anypresence.com",
      "status": 301,
      "location": "https://anypresence.com/"
    },
    {
      "url": "http://anypresence.com",
      "status": 301,
      "location": "https://anypresence.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

3.67/4.89

Fix: no breadcrumbs or clear URL hierarchy.

What we captured

{
  "anchors": 66,
  "genericLinks": 0,
  "genericRatio": 0,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 2,
  "positiveTabindex": 0,
  "clickableNonButtons": 0,
  "keyboardTrapsTested": false
}

C4Fail
Machine endpoints and agent manifests
0/6.11
No machine-readable endpoint of any kind. Most sites score zero here, which is exactly why it is the cheapest differentiation on this rubric: an agents.json is a static file, and a documented read-only API is usually a subset of something you already run.
What we captured
```
{
  "found": []
}
```
C5Not applicable
Commerce actionability
0/4
Not a commerce site; these points are redistributed across C1–C4.
What we captured
```
{
  "siteType": "content"
}
```
C6Fail
On-site search
0/3
No on-site search found. If you have search, expose it as a GET form with a query parameter so an agent can jump straight to results.
What we captured
```
{
  "searchForm": false,
  "searchAction": false
}
```

DTrust & freshness

D1Partial
Transport security
3/4
Fix: no Strict-Transport-Security header.
What we captured
```
{
  "hsts": false,
  "tlsValid": true,
  "mixedContentReferences": 0
}
```
D2Fail
Verifiable identity
0/4
Fix: no contact page or mailto link found; Organization schema has no sameAs links. 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": false,
  "hasOrganizationSchema": true
}
```

D3Fail

Policies discoverable

0/4

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

What we captured

{
  "hasTerms": false,
  "siteType": "content",
  "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
}
```

D5Partial

Identity consistency

1/3

Fix: site name differs across title, og:site_name and schema name. An unexplained name mismatch reads as a signal the site may not be what it claims.

What we captured

{
  "title": "競馬の初心者のためのノウハウまとめ",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "競馬の初心者のためのノウハウまとめ",
  "schemaName": "競馬の初心者のためのノウハウまとめ"
}

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
}
```

D7Pass

Multi-page stability

4/4

What we captured

{
  "nonOk": [],
  "slowPages": 0,
  "pagesCrawled": 1,
  "consistentTemplate": true
}

63C

Discovery & access15/25

Understanding24/25

Actionability14.67/25

Trust & freshness9/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 anypresence.com with another site →

anypresence.com

What to fix first

Machine endpoints and agent manifests

llms.txt present

Verifiable identity

Policies discoverable

XML sitemap valid and referenced

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