Agent readiness report

allegiancemd.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 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.
2C4
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.
3D3
Policies discoverable
Medium impact · Low effort
Fix: no privacy policy linked; no terms page linked.
4A4
llms.txt present
Medium impact · Low effort
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.
5B4
Meta and Open Graph
Medium impact · Low effort
Fix: 1 title(s) outside 15–70 characters; 5 description(s) outside 50–160 characters; 5 page(s) missing og:title, og:description or og:image.

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 exists but contains no parseable directives. Check for HTML being served in its place.
What we captured
```
{
  "bytes": 0,
  "status": 200,
  "directives": 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": 3,
  "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
}
```

A5Pass

Bot user-agent HTTP health

3/3

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 200,
      "ttfbMs": 477
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 164
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 160
    }
  ],
  "medianTtfbMs": 164,
  "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": 8884,
  "renderedTextLength": 8227
}

BUnderstanding

B1Pass

JSON-LD present and valid

5/5

What we captured

{
  "pagesCrawled": 6,
  "pagesWithValidJsonLd": 6,
  "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": [
    "BreadcrumbList",
    "EntryPoint",
    "ImageObject",
    "ListItem",
    "Organization",
    "PropertyValueSpecification",
    "ReadAction",
    "SearchAction",
    "WebPage",
    "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://allegiancemd.com: 12 h1 elements",
    "https://allegiancemd.com: skipped heading level",
    "https://allegiancemd.com: missing main, nav",
    "https://allegiancemd.com/pricing: 3 h1 elements",
    "https://allegiancemd.com/pricing: skipped heading level",
    "https://allegiancemd.com/pricing: missing main, nav",
    "https://allegiancemd.com/company: missing main, nav",
    "https://allegiancemd.com/company/support: 3 h1 elements",
    "https://allegiancemd.com/company/support: skipped heading level",
    "https://allegiancemd.com/company/support: missing main, nav"
  ],
  "singleH1": 2,
  "allLandmarks": 0,
  "pagesCrawled": 6,
  "noSkippedLevels": 2
}

B4Fail
Meta and Open Graph
0/3
Fix: 1 title(s) outside 15–70 characters; 5 description(s) outside 50–160 characters; 5 page(s) missing og:title, og:description or og:image.
What we captured
```
{
  "goodTitles": 5,
  "pagesCrawled": 6,
  "uniqueTitles": true,
  "goodDescriptions": 1,
  "completeOpenGraph": 1
}
```

B5Pass

Clean text ratio

3/3

What we captured

{
  "perPage": [
    0.145,
    0.215,
    0.056,
    0.054,
    0.051,
    0.086
  ],
  "averageRatio": 0.101
}

B6Partial
Alt text coverage
1/2
7 of 19 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": 12,
  "coverage": 0.63,
  "contentImages": 19
}
```

B7Partial

Canonical and duplication hygiene

1/3

Fix: 1 page(s) missing or with a mismatched rel=canonical. Duplicate hosts split whatever authority the page has earned.

What we captured

{
  "hostVariants": [
    {
      "url": "https://www.allegiancemd.com",
      "status": 301,
      "location": "https://allegiancemd.com/"
    },
    {
      "url": "http://allegiancemd.com",
      "status": 301,
      "location": "https://allegiancemd.com/"
    }
  ],
  "pagesCrawled": 6,
  "selfConsistentCanonicals": 5
}

CActionability

C1Pass

Form usability

6.11/6.11

What we captured

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

C2Pass

Navigable link graph

4.89/4.89

What we captured

{
  "anchors": 103,
  "genericLinks": 2,
  "genericRatio": 0.02,
  "hasBreadcrumb": true,
  "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": "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

D1Pass

Transport security

4/4

What we captured

{
  "hsts": true,
  "tlsValid": true,
  "mixedContentReferences": 0
}

D2Pass

Verifiable identity

4/4

What we captured

{
  "sameAsCount": 4,
  "contactDiscoverable": true,
  "hasOrganizationSchema": true
}

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": 3,
  "withLastmod": 0,
  "visibleDates": true,
  "modifiedLast90Days": 0
}
```

D5Fail

Identity consistency

0/3

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

What we captured

{
  "title": "AllegianceMD Medical Software Cloud Solutions",
  "hasFavicon": true,
  "hasOgImage": false,
  "ogSiteName": "AllegianceMD EHR Software",
  "schemaName": "AllegianceMD Medical Software Cloud Solutions"
}

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": 6,
  "consistentTemplate": true
}

63C

Discovery & access19/25

Understanding12/25

Actionability17.89/25

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

allegiancemd.com

What to fix first

Correct schema types for the site type

Machine endpoints and agent manifests

Policies discoverable

llms.txt present

Meta and Open Graph

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