Menu

Agent readiness report

sca-corp.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 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.

  1. 1B2

    Correct schema types for the site type

    High impact · Medium effort

    Missing: type-specific markup (SoftwareApplication, Article, FAQPage, Service). For a saas site, SoftwareApplication or Article or FAQPage or Service is what lets an agent understand what you actually offer rather than that you exist.

  2. 2C4

    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.

  3. 3A4

    llms.txt present

    Medium impact · Low effort

    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.

  4. 4A3

    XML sitemap valid and referenced

    Medium impact · Low effort

    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.

  5. 5B4

    Meta and Open Graph

    Medium impact · Low effort

    Fix: 1 title(s) outside 15–70 characters; 1 description(s) outside 50–160 characters.

Every check, with the evidence

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

ADiscovery & access

  • A1Partial

    robots.txt exists and parses

    1/2

    Publish a robots.txt. A missing file leaves the site open by default, so nothing is blocked — but it also means crawlers get no sitemap reference and no explicit signal about AI agents.

    What we captured
    {
      "status": 404
    }
  • A2Pass

    Major AI crawlers allowed

    6/6
    What we captured
    {
      "of": 6,
      "allowed": 6,
      "blocked": []
    }
  • 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
    }
  • A5Pass

    Bot user-agent HTTP health

    3/3
    What we captured
    {
      "probes": [
        {
          "name": "GPTBot",
          "status": 200,
          "ttfbMs": 405
        },
        {
          "name": "ClaudeBot",
          "status": 200,
          "ttfbMs": 234
        },
        {
          "name": "PerplexityBot",
          "status": 200,
          "ttfbMs": 239
        }
      ],
      "medianTtfbMs": 239,
      "edgeBlockingDespiteRobots": false
    }
  • A6Fail

    No hard interstitial

    0/2

    Detected: Cloudflare challenge. 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": [
        "Cloudflare challenge"
      ]
    }
  • 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": 1,
      "pagesWithValidJsonLd": 1,
      "homepageHasValidJsonLd": true,
      "pagesWithInvalidJsonLd": 0
    }
  • B2Partial

    Correct schema types for the site type

    2/5

    Missing: type-specific markup (SoftwareApplication, Article, FAQPage, Service). For a saas site, SoftwareApplication or Article or FAQPage or Service is what lets an agent understand what you actually offer rather than that you exist.

    What we captured
    {
      "matched": [],
      "missing": [
        "type-specific markup (SoftwareApplication, Article, FAQPage, Service)"
      ],
      "siteType": "saas",
      "typesFound": [
        "BreadcrumbList",
        "ListItem",
        "Organization",
        "WebPage",
        "WebSite"
      ]
    }
  • 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://sca-corp.com: skipped heading level"
      ],
      "singleH1": 1,
      "allLandmarks": 1,
      "pagesCrawled": 1,
      "noSkippedLevels": 0
    }
  • B4Partial

    Meta and Open Graph

    1/3

    Fix: 1 title(s) outside 15–70 characters; 1 description(s) outside 50–160 characters.

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

    Clean text ratio

    2/3

    Visible text is 5.3% 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.053
      ],
      "averageRatio": 0.053
    }
  • B6Fail

    Alt text coverage

    0/2

    6 of 7 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": 1,
      "coverage": 0.14,
      "contentImages": 7
    }
  • B7Pass

    Canonical and duplication hygiene

    3/3
    What we captured
    {
      "hostVariants": [
        {
          "url": "https://www.sca-corp.com",
          "status": 301,
          "location": "https://icc-cds.com"
        },
        {
          "url": "http://sca-corp.com",
          "status": 301,
          "location": "https://icc-cds.com"
        }
      ],
      "pagesCrawled": 1,
      "selfConsistentCanonicals": 1
    }

CActionability

  • C1Pass

    Form usability

    6.11/6.11
    What we captured
    {
      "forms": 2,
      "inputs": 2,
      "realSubmit": true,
      "unlabelled": 0,
      "wrongTypes": 0
    }
  • C2Partial

    Navigable link graph

    1.22/4.89

    Fix: 7 clickable element(s) that are not anchors — an agent cannot follow a div; 17% of links use contextless text like "click here".

    What we captured
    {
      "anchors": 90,
      "genericLinks": 15,
      "genericRatio": 0.17,
      "hasBreadcrumb": true,
      "clickableNonAnchors": 7
    }
  • C3Partial

    Interactive element semantics

    2.44/4.89

    Fix: 7 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": 20,
      "positiveTabindex": 0,
      "clickableNonButtons": 7,
      "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": "saas"
    }
  • C6Pass

    On-site search

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

DTrust & freshness

  • D1Partial

    Transport security

    3/4

    Fix: no Strict-Transport-Security header.

    What we captured
    {
      "hsts": false,
      "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": "saas",
      "hasPrivacy": true,
      "hasReturns": false,
      "hasShipping": false
    }
  • D4Partial

    Freshness signals

    1/4

    Fix: sitemap has no lastmod values; only 0% of sitemap URLs modified in the last 90 days. Staleness is a ranking signal for models deciding what to cite.

    What we captured
    {
      "sitemapUrls": 0,
      "withLastmod": 0,
      "visibleDates": true,
      "modifiedLast90Days": 0
    }
  • 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": "Home | ICC CDS",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "General Code",
      "schemaName": "Home"
    }
  • 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": 1,
      "consistentTemplate": true
    }
59C
Discovery & access10/25
Understanding16/25
Actionability16.44/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.

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