Agent readiness report

fftechnologies.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 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.
2B1
JSON-LD present and valid
High impact · Medium effort
Only 2 of 6 crawled pages carry structured data. Add it at the template level rather than page by page.
3C4
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.
4B7
Canonical and duplication hygiene
Medium impact · Low effort
Fix: 1 page(s) missing or with a mismatched rel=canonical. Duplicate hosts split whatever authority the page has earned.
5D2
Verifiable identity
Medium impact · Low effort
Fix: no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.

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": 64,
  "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": 61
}
```

A5Pass

Bot user-agent HTTP health

3/3

What we captured

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 200,
      "ttfbMs": 636
    },
    {
      "name": "ClaudeBot",
      "status": 200,
      "ttfbMs": 161
    },
    {
      "name": "PerplexityBot",
      "status": 200,
      "ttfbMs": 87
    }
  ],
  "medianTtfbMs": 161,
  "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": 4774,
  "renderedTextLength": 3894
}

BUnderstanding

B1Partial
JSON-LD present and valid
3/5
Only 2 of 6 crawled pages carry structured data. Add it at the template level rather than page by page.
What we captured
```
{
  "pagesCrawled": 6,
  "pagesWithValidJsonLd": 2,
  "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": [
    "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://fftechnologies.com: 4 h1 elements",
    "https://fftechnologies.com: missing footer",
    "https://fftechnologies.com/products: missing footer",
    "https://fftechnologies.com/about: 0 h1 elements",
    "https://fftechnologies.com/about: missing footer",
    "https://fftechnologies.com/contact: 0 h1 elements",
    "https://fftechnologies.com/contact: missing footer",
    "https://fftechnologies.com/home: 4 h1 elements",
    "https://fftechnologies.com/home: missing footer",
    "https://fftechnologies.com/appian: skipped heading level"
  ],
  "singleH1": 2,
  "allLandmarks": 0,
  "pagesCrawled": 6,
  "noSkippedLevels": 5
}

B4Partial

Meta and Open Graph

2/3

Fix: duplicate titles across pages.

What we captured

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

B5Partial
Clean text ratio
1/3
Visible text is 4.1% 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.041,
    0.031,
    0.051,
    0.036,
    0.041,
    0.05
  ],
  "averageRatio": 0.041
}
```
B6Fail
Alt text coverage
0/2
48 of 48 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": 0,
  "coverage": 0,
  "contentImages": 48
}
```

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.fftechnologies.com",
      "status": 200
    },
    {
      "url": "http://fftechnologies.com",
      "status": 301,
      "location": "https://www.fftechnologies.com/"
    }
  ],
  "pagesCrawled": 6,
  "selfConsistentCanonicals": 5
}

CActionability

C1Pass

Form usability

6.11/6.11

What we captured

{
  "forms": 3,
  "inputs": 13,
  "realSubmit": true,
  "unlabelled": 0,
  "wrongTypes": 0
}

C2Fail
Navigable link graph
0/4.89
Fix: 1 clickable element(s) that are not anchors — an agent cannot follow a div; 7% of links use contextless text like "click here"; no breadcrumbs or clear URL hierarchy.
What we captured
```
{
  "anchors": 189,
  "genericLinks": 13,
  "genericRatio": 0.07,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 1
}
```
C3Partial
Interactive element semantics
2.44/4.89
Fix: 1 element(s) act as buttons without being buttons. A div with a click handler is invisible to anything driving the page programmatically.
What we captured
```
{
  "realButtons": 7,
  "positiveTabindex": 0,
  "clickableNonButtons": 1,
  "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": "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

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

D3Partial

Policies discoverable

2/4

Fix: no terms page linked.

What we captured

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

D4Partial
Freshness signals
1/4
Fix: 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": 64,
  "withLastmod": 64,
  "visibleDates": false,
  "modifiedLast90Days": 0
}
```

D5Pass

Identity consistency

3/3

What we captured

{
  "title": "Records/Documents/Governance | Forefront Technologies",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "",
  "schemaName": "Forefront 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
}

60C

Discovery & access24/25

Understanding9/25

Actionability12.22/25

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

fftechnologies.com

What to fix first

Correct schema types for the site type

JSON-LD present and valid

Machine endpoints and agent manifests

Canonical and duplication hygiene

Verifiable identity

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