Agent readiness report

glemser.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.

1C4
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.
2D5
Identity consistency
Medium impact · Low effort
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.
3A4
llms.txt present
Medium impact · Low effort
Add an llms-full.txt containing your key content as one markdown document. Agents that need the substance can then read it in a single fetch instead of a dozen.
4C6
On-site search
Medium impact · Medium effort
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.
5B5
Clean text ratio
Medium impact · Medium effort
Visible text is 7.8% of your markup. Deeply nested wrapper elements make a page expensive to parse and dilute the content an agent extracts. Script and style contents are already excluded from this measure, so this is markup weight, not framework overhead.

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

A4Partial
llms.txt present
3/4
Add an llms-full.txt containing your key content as one markdown document. Agents that need the substance can then read it in a single fetch instead of a dozen.
What we captured
```
{
  "present": true,
  "llmsFullTxt": false,
  "describedLinks": 23
}
```

A5Pass

Bot user-agent HTTP health

3/3

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 200,
      "ttfbMs": 479
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 84
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 93
    }
  ],
  "medianTtfbMs": 93,
  "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": 7320,
  "renderedTextLength": 7091
}

BUnderstanding

B1Pass

JSON-LD present and valid

5/5

What we captured

{
  "pagesCrawled": 6,
  "pagesWithValidJsonLd": 6,
  "homepageHasValidJsonLd": true,
  "pagesWithInvalidJsonLd": 0
}

B2Pass

Correct schema types for the site type

5/5

What we captured

{
  "matched": [
    "SoftwareApplication"
  ],
  "missing": [],
  "siteType": "saas",
  "typesFound": [
    "AboutPage",
    "BreadcrumbList",
    "CollectionPage",
    "ContactPage",
    "ContactPoint",
    "ImageObject",
    "ListItem",
    "Organization",
    "SoftwareApplication",
    "WebPage",
    "WebSite"
  ]
}

B3Pass

Semantic HTML structure

4/4

What we captured

{
  "problems": [],
  "singleH1": 6,
  "allLandmarks": 6,
  "pagesCrawled": 6,
  "noSkippedLevels": 6
}

B4Pass

Meta and Open Graph

3/3

What we captured

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

B5Partial
Clean text ratio
2/3
Visible text is 7.8% of your markup. Deeply nested wrapper elements make a page expensive to parse and dilute the content an agent extracts. Script and style contents are already excluded from this measure, so this is markup weight, not framework overhead.
What we captured
```
{
  "perPage": [
    0.1,
    0.064,
    0.062,
    0.067,
    0.041,
    0.136
  ],
  "averageRatio": 0.078
}
```
B6Partial
Alt text coverage
1/2
6 of 16 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": 10,
  "coverage": 0.63,
  "contentImages": 16
}
```

B7Pass

Canonical and duplication hygiene

3/3

What we captured

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

CActionability

C1Pass

Form usability

6.11/6.11

What we captured

{
  "forms": 1,
  "inputs": 7,
  "realSubmit": true,
  "unlabelled": 0,
  "wrongTypes": 0
}

C2Pass

Navigable link graph

4.89/4.89

What we captured

{
  "anchors": 55,
  "genericLinks": 1,
  "genericRatio": 0.02,
  "hasBreadcrumb": true,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 10,
  "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": "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

D1Pass

Transport security

4/4

What we captured

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

D2Pass

Verifiable identity

4/4

What we captured

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

D3Pass

Policies discoverable

4/4

What we captured

{
  "hasTerms": true,
  "siteType": "saas",
  "hasPrivacy": true,
  "hasReturns": false,
  "hasShipping": false
}

D4Partial
Freshness signals
3/4
Fix: no visible dates on content. Staleness is a ranking signal for models deciding what to cite.
What we captured
```
{
  "sitemapUrls": 127,
  "withLastmod": 127,
  "visibleDates": false,
  "modifiedLast90Days": 32
}
```
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": "Structured Content for Life Sciences | Glemser",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "Glemser Technologies",
  "schemaName": "Glemser Technologies"
}
```
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
}

83B

Discovery & access24/25

Understanding23/25

Actionability15.89/25

Trust & freshness20/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

Show off your score

Grade B or better earns the badge. It links back to this report and updates when your score does.

<a href="https://agentfriendlyrank.com/site/glemser.com">
  <img src="https://agentfriendlyrank.com/badge/glemser.com.svg"
    alt="Agent Readiness Score 83/100, grade B" height="20">
</a>

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 glemser.com with another site →

glemser.com

What to fix first

Machine endpoints and agent manifests

Identity consistency

llms.txt present

On-site search

Clean text ratio

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?

Show off your score

Own this site?

Scan your own site