Menu

Agent readiness report

ecisolutions.com

What an AI agent can and cannot do on this site, measured by an unauthenticated crawl and scored against the published rubric.

Scanned · 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.

  1. 1B1

    JSON-LD present and valid

    High impact · Medium effort

    1 page(s) contain JSON-LD that fails to parse — malformed structured data scores zero, exactly as if it were absent. Validate the output of whatever template generates it.

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

  3. 3C1

    Form usability

    High impact · Medium effort

    No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.

  4. 4C4

    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.

  5. 5D5

    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.

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": 8
    }
  • 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": 2522,
      "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": 64
    }
  • A5Pass

    Bot user-agent HTTP health

    3/3
    What we captured
    {
      "probes": [
        {
          "name": "GPTBot",
          "status": 200,
          "ttfbMs": 801
        },
        {
          "name": "ClaudeBot",
          "status": 200,
          "ttfbMs": 159
        },
        {
          "name": "PerplexityBot",
          "status": 200,
          "ttfbMs": 139
        }
      ],
      "medianTtfbMs": 159,
      "edgeBlockingDespiteRobots": false
    }
  • A6Partial

    No hard interstitial

    1/2

    Detected: Cookie wall. An agent cannot dismiss a consent dialog or solve a challenge — whatever sits behind it is unreachable. Cookieless analytics removes the need for a banner entirely.

    What we captured
    {
      "markers": [
        "Cookie wall"
      ]
    }
  • A7Pass

    Server-rendered content parity

    5/5
    What we captured
    {
      "ratio": 1,
      "rawTextLength": 23541,
      "renderedTextLength": 4539
    }

BUnderstanding

  • B1Partial

    JSON-LD present and valid

    2/5

    1 page(s) contain JSON-LD that fails to parse — malformed structured data scores zero, exactly as if it were absent. Validate the output of whatever template generates it.

    What we captured
    {
      "pagesCrawled": 5,
      "pagesWithValidJsonLd": 4,
      "homepageHasValidJsonLd": false,
      "pagesWithInvalidJsonLd": 1
    }
  • 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": [
        "BreadcrumbList",
        "ContactPoint",
        "Corporation",
        "ImageObject",
        "ListItem",
        "Organization",
        "PostalAddress",
        "SearchAction",
        "WebPage",
        "WebSite"
      ]
    }
  • 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://ecisolutions.com: missing main",
        "https://ecisolutions.com/company/blog/: skipped heading level",
        "https://ecisolutions.com/company/blog/: missing main",
        "https://ecisolutions.com/company/news/: missing main",
        "https://ecisolutions.com/company/eci-everyday-hero/: missing main",
        "https://ecisolutions.com/connect/: skipped heading level",
        "https://ecisolutions.com/connect/: missing main"
      ],
      "singleH1": 5,
      "allLandmarks": 0,
      "pagesCrawled": 5,
      "noSkippedLevels": 3
    }
  • B4Partial

    Meta and Open Graph

    2/3

    Fix: 2 description(s) outside 50–160 characters.

    What we captured
    {
      "goodTitles": 5,
      "pagesCrawled": 5,
      "uniqueTitles": true,
      "goodDescriptions": 3,
      "completeOpenGraph": 5
    }
  • B5Partial

    Clean text ratio

    2/3

    Visible text is 5.4% 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.058,
        0.055,
        0.057,
        0.049,
        0.051
      ],
      "averageRatio": 0.054
    }
  • B6Pass

    Alt text coverage

    2/2
    What we captured
    {
      "withAlt": 84,
      "coverage": 1,
      "contentImages": 84
    }
  • B7Pass

    Canonical and duplication hygiene

    3/3
    What we captured
    {
      "hostVariants": [
        {
          "url": "https://www.ecisolutions.com",
          "status": 200
        },
        {
          "url": "http://ecisolutions.com",
          "status": 301,
          "location": "https://ecisolutions.com/"
        }
      ],
      "pagesCrawled": 5,
      "selfConsistentCanonicals": 5
    }

CActionability

  • C1Partial

    Form usability

    3.67/6.11

    No forms were found on the crawled pages, so form usability could not be assessed. If you add a contact or signup form, give every input a real label and a correct input type.

    What we captured
    {
      "formsFound": 0
    }
  • C2Pass

    Navigable link graph

    4.89/4.89
    What we captured
    {
      "anchors": 349,
      "genericLinks": 3,
      "genericRatio": 0.01,
      "hasBreadcrumb": true,
      "clickableNonAnchors": 0
    }
  • C3Pass

    Interactive element semantics

    4.89/4.89
    What we captured
    {
      "realButtons": 1,
      "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"
    }
  • C6Partial

    On-site search

    2/3

    Search exists but posts rather than using a GET query parameter, so an agent cannot construct a results URL directly. Switching to GET is usually a one-line change, and advertising it via WebSite SearchAction schema makes it discoverable.

    What we captured
    {
      "usesGet": false,
      "searchForm": false,
      "searchAction": true
    }

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": 4,
      "contactDiscoverable": true,
      "hasOrganizationSchema": true
    }
  • D3Pass

    Policies discoverable

    4/4
    What we captured
    {
      "hasTerms": true,
      "siteType": "other",
      "hasPrivacy": true,
      "hasReturns": false,
      "hasShipping": false
    }
  • D4Pass

    Freshness signals

    4/4
    What we captured
    {
      "sitemapUrls": 2522,
      "withLastmod": 2522,
      "visibleDates": true,
      "modifiedLast90Days": 993
    }
  • 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": "AI Powered Industry Specific ERP and Business Management Software",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "ECI Software Solutions",
      "schemaName": "ECI Solutions"
    }
  • D6Partial

    security.txt

    1/2

    security.txt is present but invalid: 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": true
    }
  • D7Pass

    Multi-page stability

    4/4
    What we captured
    {
      "nonOk": [],
      "slowPages": 0,
      "pagesCrawled": 5,
      "consistentTemplate": true
    }
74B
Discovery & access23/25
Understanding14/25
Actionability15.45/25
Trust & freshness22/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.

Show off your score

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

Agent Readiness Score 74/100, grade B

<a href="https://agentfriendlyrank.com/site/ecisolutions.com">
  <img src="https://agentfriendlyrank.com/badge/ecisolutions.com.svg"
    alt="Agent Readiness Score 74/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.

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