Menu

Agent readiness report

syscombusiness.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. 1A2

    Major AI crawlers allowed

    High impact · Low effort

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended. If that is deliberate, nothing to do. If it is inherited from a template or a platform default, add explicit Allow directives — these agents are how a growing share of buyers now reach you.

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

  4. 4A4

    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.

  5. 5A5

    Bot user-agent HTTP health

    Medium impact · Low effort

    GPTBot received 403, ClaudeBot received 403, PerplexityBot received 403. Allow these agents through at the edge as well as in robots.txt.

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": 11,
      "status": 200,
      "sitemaps": 1
    }
  • A2Partial

    Major AI crawlers allowed

    3/6

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended. If that is deliberate, nothing to do. If it is inherited from a template or a platform default, add explicit Allow directives — these agents are how a growing share of buyers now reach you.

    What we captured
    {
      "of": 6,
      "allowed": 3,
      "blocked": [
        "GPTBot",
        "ClaudeBot",
        "Google-Extended"
      ]
    }
  • A3Pass

    XML sitemap valid and referenced

    3/3
    What we captured
    {
      "exists": true,
      "urlCount": 172,
      "referencedInRobots": true
    }
  • 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
    }
  • A5Partial

    Bot user-agent HTTP health

    1/3

    GPTBot received 403, ClaudeBot received 403, PerplexityBot received 403. Allow these agents through at the edge as well as in robots.txt.

    What we captured
    {
      "probes": [
        {
          "name": "GPTBot",
          "status": 403,
          "ttfbMs": 27
        },
        {
          "name": "ClaudeBot",
          "status": 403,
          "ttfbMs": 20
        },
        {
          "name": "PerplexityBot",
          "status": 403,
          "ttfbMs": 7
        }
      ],
      "medianTtfbMs": 20,
      "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": 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": [
        "BreadcrumbList",
        "ListItem",
        "Organization",
        "SearchAction",
        "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://syscombusiness.com: missing main, nav, footer",
        "https://syscombusiness.com/pricing/: missing main, nav, footer",
        "https://syscombusiness.com/about-us/: missing main, nav, footer",
        "https://syscombusiness.com/industries/: missing main, nav, footer",
        "https://syscombusiness.com/our-clients/: skipped heading level",
        "https://syscombusiness.com/our-clients/: missing main, nav, footer",
        "https://syscombusiness.com/it-services/: missing main, nav, footer"
      ],
      "singleH1": 6,
      "allLandmarks": 0,
      "pagesCrawled": 6,
      "noSkippedLevels": 5
    }
  • B4Pass

    Meta and Open Graph

    3/3
    What we captured
    {
      "goodTitles": 6,
      "pagesCrawled": 6,
      "uniqueTitles": true,
      "goodDescriptions": 6,
      "completeOpenGraph": 6
    }
  • B5Pass

    Clean text ratio

    3/3
    What we captured
    {
      "perPage": [
        0.216,
        0.273,
        0.152,
        0.21,
        0.196,
        0.202
      ],
      "averageRatio": 0.208
    }
  • B6Pass

    Alt text coverage

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

    Canonical and duplication hygiene

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

CActionability

  • C1Pass

    Form usability

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

    Navigable link graph

    3.67/4.89

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

    What we captured
    {
      "anchors": 137,
      "genericLinks": 9,
      "genericRatio": 0.07,
      "hasBreadcrumb": false,
      "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
    }
  • D2Partial

    Verifiable identity

    2/4

    Fix: Organization schema has no sameAs links. 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": true
    }
  • 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

    3/4

    Fix: no visible dates on content. Staleness is a ranking signal for models deciding what to cite.

    What we captured
    {
      "sitemapUrls": 172,
      "withLastmod": 172,
      "visibleDates": false,
      "modifiedLast90Days": 69
    }
  • 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": "Managed IT Services in Michigan and Pennsylvania | Syscom",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "Syscom Business Technologies",
      "schemaName": "Syscom Business 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
    }
61C
Discovery & access9/25
Understanding19/25
Actionability16.67/25
Trust & freshness16/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 syscombusiness.com with another site →