Agent readiness report

totsys.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-08 · 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.
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 (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.
4C1
Form usability
High impact · Medium effort
Fix: 1 input(s) use the wrong type for their content. A placeholder is not a label — an agent filling your form has no way to know what an unlabelled field wants.
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"
  ]
}
```
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": 404,
  "present": false
}
```

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": 8
    },
    {
      "name": "ClaudeBot",
      "status": 403,
      "ttfbMs": 23
    },
    {
      "name": "PerplexityBot",
      "status": 403,
      "ttfbMs": 7
    }
  ],
  "medianTtfbMs": 8,
  "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": 1963,
  "renderedTextLength": 1761
}

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 (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": [
    "Organization or WebSite sitewide",
    "type-specific markup (Article, FAQPage, Service, SoftwareApplication)"
  ],
  "siteType": "other",
  "typesFound": []
}
```

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://totsys.com: 0 h1 elements",
    "https://totsys.com: missing main, nav, footer",
    "https://totsys.com/Products/Cas?selectedIndex=0: 0 h1 elements",
    "https://totsys.com/Products/Cas?selectedIndex=0: missing main, nav, footer",
    "https://totsys.com/Products/Firmview?selectedIndex=0: 0 h1 elements",
    "https://totsys.com/Products/Firmview?selectedIndex=0: missing main, nav, footer",
    "https://totsys.com/Company: 0 h1 elements",
    "https://totsys.com/Company: missing main, nav, footer",
    "https://totsys.com/Contact: 0 h1 elements",
    "https://totsys.com/Contact: missing main, nav, footer"
  ],
  "singleH1": 0,
  "allLandmarks": 0,
  "pagesCrawled": 6,
  "noSkippedLevels": 6
}

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

B5Pass

Clean text ratio

3/3

What we captured

{
  "perPage": [
    0.139,
    0.258,
    0.245,
    0.131,
    0.058,
    0.119
  ],
  "averageRatio": 0.158
}

B6Fail
Alt text coverage
0/2
57 of 69 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.17,
  "contentImages": 69
}
```
B7Fail
Canonical and duplication hygiene
0/3
Fix: 6 page(s) missing or with a mismatched rel=canonical; www/non-www or http/https variants do not resolve to one canonical host. Duplicate hosts split whatever authority the page has earned.
What we captured
```
{
  "hostVariants": [
    {
      "url": "https://www.totsys.com",
      "status": 200
    },
    {
      "url": "http://totsys.com",
      "status": 521
    }
  ],
  "pagesCrawled": 6,
  "selfConsistentCanonicals": 0
}
```

CActionability

C1Partial
Form usability
4.89/6.11
Fix: 1 input(s) use the wrong type for their content. 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": 1,
  "inputs": 4,
  "realSubmit": true,
  "unlabelled": 0,
  "wrongTypes": 1
}
```

C2Partial

Navigable link graph

3.67/4.89

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

What we captured

{
  "anchors": 35,
  "genericLinks": 9,
  "genericRatio": 0.26,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

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

D1Pass

Transport security

4/4

What we captured

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

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
}
```

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
}

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
Fix: site name differs across title, og:site_name and schema name; no favicon declared; no og:image. An unexplained name mismatch reads as a signal the site may not be what it claims.
What we captured
```
{
  "title": "TSI: The World's Leading Commission Allocation and Sharing Experts",
  "hasFavicon": false,
  "hasOgImage": false,
  "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": 404,
  "present": false
}
```

D7Pass

Multi-page stability

4/4

What we captured

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

40D

Discovery & access13/25

Understanding4/25

Actionability13.45/25

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

totsys.com

What to fix first

Major AI crawlers allowed

JSON-LD present and valid

Correct schema types for the site type

Form usability

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