Agent readiness report

mfluent.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-07 · 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.

1A2
Major AI crawlers allowed
High impact · Low effort
robots.txt blocks GPTBot, ClaudeBot, Google-Extended. If that is deliberate, nothing to do. If it is inherited from a template or a platform default, add explicit Allow directives — these agents are how a growing share of buyers now reach you.
2C1
Form usability
High impact · Medium effort
No pages could be fetched.
3B1
JSON-LD present and valid
High impact · Medium effort
No pages could be fetched.
4B2
Correct schema types for the site type
High impact · Medium effort
No pages could be fetched.
5C4
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.

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": 10,
  "status": 200,
  "sitemaps": 0
}
```
A2Partial
Major AI crawlers allowed
3/6
robots.txt blocks GPTBot, ClaudeBot, Google-Extended. If that is deliberate, nothing to do. If it is inherited from a template or a platform default, add explicit Allow directives — these agents are how a growing share of buyers now reach you.
What we captured
```
{
  "of": 6,
  "allowed": 3,
  "blocked": [
    "GPTBot",
    "ClaudeBot",
    "Google-Extended"
  ]
}
```
A3Partial
XML sitemap valid and referenced
1/3
Fix: sitemap parsed to zero URLs; 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": 0,
  "referencedInRobots": false
}
```
A4Partial
llms.txt present
1/4
llms.txt exists but only 0 links carry a description. Add a short description after each link — an undescribed link list gives a model no basis for choosing what to fetch.
What we captured
```
{
  "present": true,
  "anyLinks": 0,
  "llmsFullTxt": true,
  "describedLinks": 0
}
```

A5Partial

Bot user-agent HTTP health

1/3

GPTBot received 403, ClaudeBot received 403, PerplexityBot received 403. Allow these agents through at the edge as well as in robots.txt.

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 403,
      "ttfbMs": 73
    },
    {
      "name": "ClaudeBot",
      "status": 403,
      "ttfbMs": 26
    },
    {
      "name": "PerplexityBot",
      "status": 403,
      "ttfbMs": 57
    }
  ],
  "medianTtfbMs": 57,
  "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": 0,
  "renderedTextLength": 0
}

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
```
{}
```
D6Partial
security.txt
1/2
security.txt is present but invalid: no Contact field; no Expires field. An expired Expires field makes the whole file non-conformant, so this fails even though the file was correct when it was written.
What we captured
```
{
  "valid": false,
  "hasContact": false
}
```

D7Pass

Multi-page stability

4/4

What we captured

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

23F

Discovery & access15/25

Understanding0/25

Actionability0/25

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

mfluent.com

What to fix first

Major AI crawlers allowed

Form usability

JSON-LD present and valid

Correct schema types for the site type

Machine endpoints and agent manifests

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