Agent readiness report

helprace.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-06 · rubric v1.0.1 · scored as a SaaS 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
Fix: 4 of 4 inputs have no associated label; 1 input(s) use the wrong type for their content; at least one form has no real submit button. A placeholder is not a label — an agent filling your form has no way to know what an unlabelled field wants.
2B1
JSON-LD present and valid
High impact · Medium effort
Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.
3B2
Correct schema types for the site type
High impact · Medium effort
Missing: Organization or WebSite sitewide; type-specific markup (SoftwareApplication, Article, FAQPage, Service). For a saas site, SoftwareApplication or Article or FAQPage or Service is what lets an agent understand what you actually offer rather than that you exist.
4C4
Machine endpoints and agent manifests
High impact · High effort
Found API documentation link. A second machine surface — an OpenAPI spec or an MCP server — takes this to full marks.
5A4
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.

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": 85,
  "referencedInRobots": true
}

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": 240
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 160
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 160
    }
  ],
  "medianTtfbMs": 160,
  "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": 7640,
  "renderedTextLength": 3005
}

BUnderstanding

B1Fail
JSON-LD present and valid
0/5
Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.
What we captured
```
{
  "pagesCrawled": 6,
  "pagesWithValidJsonLd": 0,
  "homepageHasValidJsonLd": false,
  "pagesWithInvalidJsonLd": 0
}
```
B2Fail
Correct schema types for the site type
0/5
Missing: Organization or WebSite sitewide; type-specific markup (SoftwareApplication, Article, FAQPage, Service). For a saas site, SoftwareApplication or Article or FAQPage or Service is what lets an agent understand what you actually offer rather than that you exist.
What we captured
```
{
  "matched": [],
  "missing": [
    "Organization or WebSite sitewide",
    "type-specific markup (SoftwareApplication, Article, FAQPage, Service)"
  ],
  "siteType": "saas",
  "typesFound": []
}
```

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://helprace.com: missing main",
    "https://helprace.com/pricing: 0 h1 elements",
    "https://helprace.com/pricing: missing main",
    "https://helprace.com/docs/api/: missing main, footer",
    "https://helprace.com/docs/style-guide/: 7 h1 elements",
    "https://helprace.com/docs/style-guide/: missing main, footer",
    "https://helprace.com/contact: 0 h1 elements",
    "https://helprace.com/contact: missing main",
    "https://helprace.com/blog: skipped heading level",
    "https://helprace.com/blog: missing main"
  ],
  "singleH1": 3,
  "allLandmarks": 0,
  "pagesCrawled": 6,
  "noSkippedLevels": 5
}

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

B5Pass

Clean text ratio

3/3

What we captured

{
  "perPage": [
    0.224,
    0.129,
    0.042,
    0.397,
    0.059,
    0.127
  ],
  "averageRatio": 0.163
}

B6Pass

Alt text coverage

2/2

What we captured

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

B7Partial

Canonical and duplication hygiene

1/3

Fix: 2 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.helprace.com",
      "status": 301,
      "location": "https://helprace.com/"
    },
    {
      "url": "http://helprace.com",
      "status": 301,
      "location": "https://helprace.com/"
    }
  ],
  "pagesCrawled": 6,
  "selfConsistentCanonicals": 4
}

CActionability

C1Fail
Form usability
0/6.11
Fix: 4 of 4 inputs have no associated label; 1 input(s) use the wrong type for their content; at least one form has no real submit button. A placeholder is not a label — an agent filling your form has no way to know what an unlabelled field wants.
What we captured
```
{
  "forms": 2,
  "inputs": 4,
  "realSubmit": false,
  "unlabelled": 4,
  "wrongTypes": 1
}
```

C2Partial

Navigable link graph

3.67/4.89

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

What we captured

{
  "anchors": 79,
  "genericLinks": 5,
  "genericRatio": 0.06,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 0,
  "positiveTabindex": 0,
  "clickableNonButtons": 0,
  "keyboardTrapsTested": false
}

C4Partial
Machine endpoints and agent manifests
3.67/6.11
Found API documentation link. A second machine surface — an OpenAPI spec or an MCP server — takes this to full marks.
What we captured
```
{
  "found": [
    "API documentation link"
  ]
}
```
C5Not applicable
Commerce actionability
0/4
Not a commerce site; these points are redistributed across C1–C4.
What we captured
```
{
  "siteType": "saas"
}
```
C6Fail
On-site search
0/3
No on-site search found. If you have search, expose it as a GET form with a query parameter so an agent can jump straight to results.
What we captured
```
{
  "searchForm": false,
  "searchAction": false
}
```

DTrust & freshness

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

D3Pass

Policies discoverable

4/4

What we captured

{
  "hasTerms": true,
  "siteType": "saas",
  "hasPrivacy": true,
  "hasReturns": true,
  "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": 85,
  "withLastmod": 0,
  "visibleDates": true,
  "modifiedLast90Days": 0
}
```
D5Partial
Identity consistency
1/3
Fix: site name differs across title, og:site_name and schema name. An unexplained name mismatch reads as a signal the site may not be what it claims.
What we captured
```
{
  "title": "Customer Service | Help Desk Software for Customer Support | Helprace",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "",
  "schemaName": ""
}
```
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": 403,
  "present": false
}
```

D7Pass

Multi-page stability

4/4

What we captured

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

53D

Discovery & access21/25

Understanding6/25

Actionability12.23/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 helprace.com with another site →

helprace.com

What to fix first

Form usability

JSON-LD present and valid

Correct schema types for the site type

Machine endpoints and agent manifests

llms.txt present

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