Agent readiness report

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

1C1
Form usability
High impact · Medium effort
Fix: 6 of 6 inputs have no associated label; 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.
2B2
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.
3C4
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.
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.
5A3
XML sitemap valid and referenced
Medium impact · Low effort
Fix: sitemap parsed to zero URLs; not referenced from robots.txt. A sitemap referenced from robots.txt is how a crawler discovers pages that are not linked from the homepage.

Every check, with the evidence

No finding without evidence: each result shows what we actually captured during the crawl.

ADiscovery & access

A1Fail
robots.txt exists and parses
0/2
robots.txt exists but contains no parseable directives. Check for HTML being served in its place.
What we captured
```
{
  "bytes": 2111533,
  "status": 200,
  "directives": 0
}
```
A2Pass
Major AI crawlers allowed
6/6
What we captured
```
{
  "of": 6,
  "allowed": 6,
  "blocked": []
}
```
A3Partial
XML sitemap valid and referenced
1/3
Fix: sitemap parsed to zero URLs; 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": true,
  "urlCount": 0,
  "referencedInRobots": false
}
```
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": 0,
  "llmsFullTxt": true,
  "describedLinks": 0
}
```
A5Partial
Bot user-agent HTTP health
1/3
Your robots.txt welcomes these agents, but GPTBot received 403, ClaudeBot received 403, PerplexityBot received 403 — the block is happening at your CDN or WAF, before robots.txt is ever read. Cloudflare in particular blocks AI crawlers by default on every plan. One setting change, and it is invisible until someone tests it.
What we captured
```
{
  "probes": [
    {
      "name": "GPTBot",
      "status": 403,
      "ttfbMs": 801
    },
    {
      "name": "ClaudeBot",
      "status": 403,
      "ttfbMs": 479
    },
    {
      "name": "PerplexityBot",
      "status": 403,
      "ttfbMs": 411
    }
  ],
  "medianTtfbMs": 479,
  "edgeBlockingDespiteRobots": true
}
```
A6Pass
No hard interstitial
2/2
What we captured
```
{
  "markers": []
}
```
A7Not applicable
Server-rendered content parity
0/5
No headless render was captured, so parity could not be measured. Re-run with rendering enabled.
What we captured
```
{
  "rendered": false
}
```

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": [
    "ContactPoint",
    "ImageObject",
    "Organization",
    "PostalAddress"
  ]
}
```

B3Partial

Semantic HTML structure

3/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://invensys.com: 2 h1 elements",
    "https://invensys.com/ww/en/product-country-selector/?pageType=all-products: 2 h1 elements",
    "https://invensys.com/ww/en/about-us/: 2 h1 elements",
    "https://invensys.com/ww/en/about-us/newsroom/: 2 h1 elements",
    "https://invensys.com/ww/en/about-us/university/: 2 h1 elements",
    "https://invensys.com/ww/en/about-us/open-source/: 2 h1 elements"
  ],
  "singleH1": 0,
  "allLandmarks": 6,
  "pagesCrawled": 6,
  "noSkippedLevels": 6
}

B4Partial
Meta and Open Graph
1/3
Fix: duplicate titles across pages; 6 description(s) outside 50–160 characters.
What we captured
```
{
  "goodTitles": 6,
  "pagesCrawled": 6,
  "uniqueTitles": false,
  "goodDescriptions": 0,
  "completeOpenGraph": 6
}
```
B5Partial
Clean text ratio
1/3
Visible text is 1.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.011,
    0.011,
    0.011,
    0.011,
    0.011,
    0.011
  ],
  "averageRatio": 0.011
}
```
B6Partial
Alt text coverage
1/2
72 of 150 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": 78,
  "coverage": 0.52,
  "contentImages": 150
}
```

B7Partial

Canonical and duplication hygiene

1/3

Fix: 6 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.invensys.com",
      "status": 301,
      "location": "https://www.se.com/ww/en/brands/invensys/invensys.jsp"
    },
    {
      "url": "http://invensys.com",
      "status": 301,
      "location": "https://invensys.com/"
    }
  ],
  "pagesCrawled": 6,
  "selfConsistentCanonicals": 0
}

CActionability

C1Partial
Form usability
1.22/6.11
Fix: 6 of 6 inputs have no associated label; 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": 6,
  "inputs": 6,
  "realSubmit": false,
  "unlabelled": 6,
  "wrongTypes": 0
}
```

C2Partial

Navigable link graph

3.67/4.89

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

What we captured

{
  "anchors": 74,
  "genericLinks": 22,
  "genericRatio": 0.3,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}

C3Pass

Interactive element semantics

4.89/4.89

What we captured

{
  "realButtons": 33,
  "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": 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": 8,
  "contactDiscoverable": true,
  "hasOrganizationSchema": true
}

D3Partial

Policies discoverable

2/4

Fix: no terms page linked.

What we captured

{
  "hasTerms": false,
  "siteType": "other",
  "hasPrivacy": true,
  "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
}
```

D5Pass

Identity consistency

3/3

What we captured

{
  "title": "Schneider Electric Global | Your Energy Technology Partner",
  "hasFavicon": true,
  "hasOgImage": true,
  "ogSiteName": "Schneider Electric",
  "schemaName": "Schneider Electric"
}

D6Partial
security.txt
1/2
security.txt is present but invalid: no Contact field; no Expires field. An expired Expires field makes the whole file non-conformant, so this fails even though the file was correct when it was written.
What we captured
```
{
  "valid": false,
  "hasContact": false
}
```

D7Partial

Multi-page stability

3/4

Fix: 1 page(s) exceeded 4s TTFB.

What we captured

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

55C

Discovery & access11/25

Understanding14/25

Actionability12.78/25

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

invensys.com

What to fix first

Form usability

Correct schema types for the site type

Machine endpoints and agent manifests

llms.txt present

XML sitemap valid and referenced

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