Agent readiness report

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

1C1
Form usability
High impact · Medium effort
No pages could be fetched.
2B1
JSON-LD present and valid
High impact · Medium effort
No pages could be fetched.
3B2
Correct schema types for the site type
High impact · Medium effort
No pages could be fetched.
4C4
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.
5A7
Server-rendered content parity
High impact · High effort
An agent fetching your HTML sees almost nothing — 0 characters against 186 after rendering. Everything downstream of this is affected: schema an agent never receives may as well not exist. This is the single highest-value fix on the report, and the most involved.

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 202. Serve it as a 200 with plain text.
What we captured
```
{
  "status": 202
}
```
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": 202,
  "present": false
}
```
A5Partial
Bot user-agent HTTP health
1/3
Your robots.txt welcomes these agents, but GPTBot received 202, ClaudeBot received 202, PerplexityBot received 202 — 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": 202,
      "ttfbMs": 271
    },
    {
      "name": "ClaudeBot",
      "status": 202,
      "ttfbMs": 123
    },
    {
      "name": "PerplexityBot",
      "status": 202,
      "ttfbMs": 30
    }
  ],
  "medianTtfbMs": 123,
  "edgeBlockingDespiteRobots": true
}
```
A6Pass
No hard interstitial
2/2
What we captured
```
{
  "markers": []
}
```
A7Fail
Server-rendered content parity
0/5
An agent fetching your HTML sees almost nothing — 0 characters against 186 after rendering. Everything downstream of this is affected: schema an agent never receives may as well not exist. This is the single highest-value fix on the report, and the most involved.
What we captured
```
{
  "ratio": 0,
  "rawTextLength": 0,
  "renderedTextLength": 186
}
```

BUnderstanding

B1Fail
JSON-LD present and valid
0/5
No pages could be fetched.
What we captured
```
{}
```
B2Fail
Correct schema types for the site type
0/5
No pages could be fetched.
What we captured
```
{}
```
B3Fail
Semantic HTML structure
0/4
No pages could be fetched.
What we captured
```
{}
```
B4Fail
Meta and Open Graph
0/3
No pages could be fetched.
What we captured
```
{}
```
B5Fail
Clean text ratio
0/3
No pages could be fetched.
What we captured
```
{}
```
B6Fail
Alt text coverage
0/2
No pages could be fetched.
What we captured
```
{}
```
B7Fail
Canonical and duplication hygiene
0/3
No pages could be fetched.
What we captured
```
{}
```

CActionability

C1Fail
Form usability
0/6.11
No pages could be fetched.
What we captured
```
{}
```
C2Fail
Navigable link graph
0/4.89
No pages could be fetched.
What we captured
```
{}
```
C3Fail
Interactive element semantics
0/4.89
No pages could be fetched.
What we captured
```
{}
```
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"
}
```
C6Fail
On-site search
0/3
No pages could be fetched.
What we captured
```
{}
```

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
No pages could be fetched.
What we captured
```
{}
```
D3Fail
Policies discoverable
0/4
No pages could be fetched.
What we captured
```
{}
```
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": 0,
  "withLastmod": 0,
  "visibleDates": false,
  "modifiedLast90Days": 0
}
```
D5Fail
Identity consistency
0/3
Homepage could not be fetched.
What we captured
```
{}
```
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": 202,
  "present": false
}
```

D7Partial

Multi-page stability

2/4

Fix: 1 page(s) did not return 200: https://blueridgesolutions.net (202).

What we captured

{
  "nonOk": [
    {
      "url": "https://blueridgesolutions.net",
      "status": 202
    }
  ],
  "slowPages": 0,
  "pagesCrawled": 1,
  "consistentTemplate": true
}

14F

Discovery & access9/25

Understanding0/25

Actionability0/25

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

blueridgesolutions.net

What to fix first

Form usability

JSON-LD present and valid

Correct schema types for the site type

Machine endpoints and agent manifests

Server-rendered content parity

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