Agent readiness report

apexdigital.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.
3A7
Server-rendered content parity
High impact · High effort
Roughly 42% of your visible content only appears after JavaScript runs. Agents using a plain fetch miss it. Server-render or prerender the routes that matter commercially.
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.
5D1
Transport security
Medium impact · Low effort
Fix: no Strict-Transport-Security header; 10 insecure subresource reference(s).

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": 1
}
```
A2Pass
Major AI crawlers allowed
6/6
What we captured
```
{
  "of": 6,
  "allowed": 6,
  "blocked": []
}
```

A3Pass

XML sitemap valid and referenced

3/3

What we captured

{
  "exists": true,
  "urlCount": 5,
  "referencedInRobots": true
}

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": 43,
  "llmsFullTxt": false,
  "describedLinks": 0
}
```

A5Pass

Bot user-agent HTTP health

3/3

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 200,
      "ttfbMs": 559
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 161
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 159
    }
  ],
  "medianTtfbMs": 161,
  "edgeBlockingDespiteRobots": false
}

A6Fail
No hard interstitial
0/2
Detected: CAPTCHA, Cookie wall. An agent cannot dismiss a consent dialog or solve a challenge — whatever sits behind it is unreachable. Cookieless analytics removes the need for a banner entirely.
What we captured
```
{
  "markers": [
    "CAPTCHA",
    "Cookie wall"
  ]
}
```
A7Partial
Server-rendered content parity
3/5
Roughly 42% of your visible content only appears after JavaScript runs. Agents using a plain fetch miss it. Server-render or prerender the routes that matter commercially.
What we captured
```
{
  "ratio": 0.577,
  "rawTextLength": 9708,
  "renderedTextLength": 16824
}
```

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"
  ]
}

B3Partial

Semantic HTML structure

1/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://apexdigital.com: skipped heading level",
    "https://apexdigital.com: missing main",
    "https://apexdigital.com/about-apex-digital/: skipped heading level",
    "https://apexdigital.com/about-apex-digital/: missing main",
    "https://apexdigital.com/vcio/: skipped heading level",
    "https://apexdigital.com/vcio/: missing main",
    "https://apexdigital.com/careers/: skipped heading level",
    "https://apexdigital.com/careers/: missing main",
    "https://apexdigital.com/partners/: missing main",
    "https://apexdigital.com/nonprofit/: skipped heading level"
  ],
  "singleH1": 6,
  "allLandmarks": 0,
  "pagesCrawled": 6,
  "noSkippedLevels": 1
}

B4Partial

Meta and Open Graph

2/3

Fix: 2 description(s) outside 50–160 characters.

What we captured

{
  "goodTitles": 6,
  "pagesCrawled": 6,
  "uniqueTitles": true,
  "goodDescriptions": 4,
  "completeOpenGraph": 6
}

B5Pass

Clean text ratio

3/3

What we captured

{
  "perPage": [
    0.083,
    0.09,
    0.133,
    0.156,
    0.14,
    0.138
  ],
  "averageRatio": 0.123
}

B6Fail
Alt text coverage
0/2
109 of 160 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": 51,
  "coverage": 0.32,
  "contentImages": 160
}
```

B7Pass

Canonical and duplication hygiene

3/3

What we captured

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

CActionability

C1Pass

Form usability

6.11/6.11

What we captured

{
  "forms": 12,
  "inputs": 6,
  "realSubmit": true,
  "unlabelled": 0,
  "wrongTypes": 0
}

C2Partial

Navigable link graph

3.67/4.89

Fix: 6% of links use contextless text like "click here".

What we captured

{
  "anchors": 174,
  "genericLinks": 10,
  "genericRatio": 0.06,
  "hasBreadcrumb": true,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 3,
  "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"
}
```

C6Pass

On-site search

3/3

What we captured

{
  "usesGet": true,
  "searchForm": true,
  "searchAction": true
}

DTrust & freshness

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

D3Pass

Policies discoverable

4/4

What we captured

{
  "hasTerms": true,
  "siteType": "other",
  "hasPrivacy": true,
  "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": 5,
  "withLastmod": 0,
  "visibleDates": true,
  "modifiedLast90Days": 0
}
```

D5Pass

Identity consistency

3/3

What we captured

{
  "title": "Responsive, Flexible, and Friendly IT Services | Apex Digital",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "Apex Digital",
  "schemaName": "Responsive, Flexible, and Friendly IT Services | Apex Digital"
}

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

68C

Discovery & access18/25

Understanding16/25

Actionability17.67/25

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

apexdigital.com

What to fix first

Correct schema types for the site type

Machine endpoints and agent manifests

Server-rendered content parity

llms.txt present

Transport security

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