Agent readiness report

acolyte.net

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 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.

1B2
Correct schema types for the site type
High impact · Medium effort
Missing: type-specific markup (Article, FAQPage, Service, SoftwareApplication). For a other site, Article or FAQPage or Service or SoftwareApplication is what lets an agent understand what you actually offer rather than that you exist.
2C1
Form usability
High impact · Medium effort
No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.
3C4
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.
4A4
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.
5D3
Policies discoverable
Medium impact · Low effort
Fix: no privacy policy linked; no terms page linked.

Every check, with the evidence

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

ADiscovery & access

A1Pass
robots.txt exists and parses
2/2
What we captured
```
{
  "groups": 1,
  "status": 200,
  "sitemaps": 0
}
```
A2Pass
Major AI crawlers allowed
6/6
What we captured
```
{
  "of": 6,
  "allowed": 6,
  "blocked": []
}
```
A3Partial
XML sitemap valid and referenced
2/3
Fix: 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": true,
  "urlCount": 2,
  "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
}
```

A5Pass

Bot user-agent HTTP health

3/3

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 200,
      "ttfbMs": 420
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 423
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 417
    }
  ],
  "medianTtfbMs": 420,
  "edgeBlockingDespiteRobots": false
}

A6Pass
No hard interstitial
2/2
What we captured
```
{
  "markers": []
}
```

A7Pass

Server-rendered content parity

5/5

What we captured

{
  "ratio": 1,
  "rawTextLength": 3280,
  "renderedTextLength": 2279
}

BUnderstanding

B1Pass

JSON-LD present and valid

5/5

What we captured

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

B2Partial
Correct schema types for the site type
2/5
Missing: type-specific markup (Article, FAQPage, Service, SoftwareApplication). For a other site, Article or FAQPage or Service or SoftwareApplication is what lets an agent understand what you actually offer rather than that you exist.
What we captured
```
{
  "matched": [],
  "missing": [
    "type-specific markup (Article, FAQPage, Service, SoftwareApplication)"
  ],
  "siteType": "other",
  "typesFound": [
    "SearchAction",
    "WebSite"
  ]
}
```

B3Fail

Semantic HTML structure

0/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://acolyte.net: 2 h1 elements",
    "https://acolyte.net: skipped heading level",
    "https://acolyte.net: missing main, footer"
  ],
  "singleH1": 0,
  "allLandmarks": 0,
  "pagesCrawled": 1,
  "noSkippedLevels": 0
}

B4Partial

Meta and Open Graph

2/3

Fix: 1 page(s) missing og:title, og:description or og:image.

What we captured

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

B5Pass

Clean text ratio

3/3

What we captured

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

B6Pass

Alt text coverage

2/2

What we captured

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

B7Pass

Canonical and duplication hygiene

3/3

What we captured

{
  "hostVariants": [
    {
      "url": "https://www.acolyte.net",
      "status": 200
    },
    {
      "url": "http://acolyte.net",
      "status": 301,
      "location": "http://www.acolyte.net/"
    }
  ],
  "pagesCrawled": 1,
  "selfConsistentCanonicals": 1
}

CActionability

C1Partial
Form usability
3.67/6.11
No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.
What we captured
```
{
  "formsFound": 0
}
```
C2Partial
Navigable link graph
2.44/4.89
Fix: 14% of links use contextless text like "click here"; no breadcrumbs or clear URL hierarchy.
What we captured
```
{
  "anchors": 49,
  "genericLinks": 7,
  "genericRatio": 0.14,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}
```

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 1,
  "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": "other"
}
```
C6Partial
On-site search
2/3
Search exists but posts rather than using a GET query parameter, so an agent cannot construct a results URL directly. Switching to GET is usually a one-line change, and advertising it via WebSite SearchAction schema makes it discoverable.
What we captured
```
{
  "usesGet": false,
  "searchForm": false,
  "searchAction": true
}
```

DTrust & freshness

D1Partial
Transport security
2/4
Fix: no Strict-Transport-Security header; 22 insecure subresource reference(s).
What we captured
```
{
  "hsts": false,
  "tlsValid": true,
  "mixedContentReferences": 22
}
```
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
}

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

D5Partial

Identity consistency

2/3

Fix: no og:image. An unexplained name mismatch reads as a signal the site may not be what it claims.

What we captured

{
  "title": "Acolyte Technologies Corporation - Custom Solutions for your Business",
  "hasFavicon": true,
  "hasOgImage": false,
  "ogSiteName": "Acolyte Technologies Corporation",
  "schemaName": "Acolyte Technologies Corporation"
}

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
}

60C

Discovery & access20/25

Understanding17/25

Actionability13/25

Trust & freshness10/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 acolyte.net with another site →

acolyte.net

What to fix first

Correct schema types for the site type

Form usability

Machine endpoints and agent manifests

llms.txt present

Policies discoverable

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