Menu

Agent readiness report

igear.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 e-commerce 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 (Product, Offer). For a ecommerce site, Product or Offer is what lets an agent understand what you actually offer rather than that you exist.

  2. 2C1

    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.

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

    Policies discoverable

    Medium impact · Low effort

    Fix: no privacy policy linked; shipping and returns pages not both linked.

  5. 5A4

    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.

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": 5,
      "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": 19,
      "referencedInRobots": true
    }
  • 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": 3,
      "llmsFullTxt": false,
      "describedLinks": 0
    }
  • A5Pass

    Bot user-agent HTTP health

    3/3
    What we captured
    {
      "probes": [
        {
          "name": "GPTBot",
          "status": 200,
          "ttfbMs": 1039
        },
        {
          "name": "ClaudeBot",
          "status": 200,
          "ttfbMs": 243
        },
        {
          "name": "PerplexityBot",
          "status": 200,
          "ttfbMs": 399
        }
      ],
      "medianTtfbMs": 399,
      "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": 12890,
      "renderedTextLength": 8228
    }

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 (Product, Offer). For a ecommerce site, Product or Offer is what lets an agent understand what you actually offer rather than that you exist.

    What we captured
    {
      "matched": [],
      "missing": [
        "type-specific markup (Product, Offer)"
      ],
      "siteType": "ecommerce",
      "typesFound": [
        "EntryPoint",
        "LocalBusiness",
        "PostalAddress",
        "SearchAction",
        "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://igear.com: 12 h1 elements"
      ],
      "singleH1": 0,
      "allLandmarks": 1,
      "pagesCrawled": 1,
      "noSkippedLevels": 1
    }
  • B4Partial

    Meta and Open Graph

    2/3

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

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

    Clean text ratio

    1/3

    Visible text is 3.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.034
      ],
      "averageRatio": 0.034
    }
  • B6Partial

    Alt text coverage

    1/2

    10 of 47 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": 37,
      "coverage": 0.79,
      "contentImages": 47
    }
  • B7Pass

    Canonical and duplication hygiene

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

CActionability

  • C1Partial

    Form usability

    3/5

    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
    }
  • C2Fail

    Navigable link graph

    0/4

    Fix: 5 clickable element(s) that are not anchors — an agent cannot follow a div; 15% of links use contextless text like "click here"; no breadcrumbs or clear URL hierarchy.

    What we captured
    {
      "anchors": 86,
      "genericLinks": 13,
      "genericRatio": 0.15,
      "hasBreadcrumb": false,
      "clickableNonAnchors": 5
    }
  • C3Partial

    Interactive element semantics

    2/4

    Fix: 5 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": 10,
      "positiveTabindex": 0,
      "clickableNonButtons": 5,
      "keyboardTrapsTested": false
    }
  • C4Fail

    Machine endpoints and agent manifests

    0/5

    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": []
    }
  • C5Fail

    Commerce actionability

    0/4

    Fix: no product page reachable within the crawl depth; no Offer schema carrying price and availability; cart or checkout path did not return 200 without login; no guest or express checkout signal detected. Agentic commerce depends on an agent being able to read a price and reach a checkout without an account.

    What we captured
    {
      "offerSchema": false,
      "cartReachable": false,
      "expressCheckout": false,
      "productPageFound": false
    }
  • 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: 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
    }
  • D3Fail

    Policies discoverable

    0/4

    Fix: no privacy policy linked; shipping and returns pages not both linked.

    What we captured
    {
      "hasTerms": true,
      "siteType": "ecommerce",
      "hasPrivacy": false,
      "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": 19,
      "withLastmod": 0,
      "visibleDates": false,
      "modifiedLast90Days": 0
    }
  • D5Pass

    Identity consistency

    3/3
    What we captured
    {
      "title": "IGear | Helping Industrial Organizations Run Better Operations",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "IGear",
      "schemaName": "IGear, LLC"
    }
  • 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": 400,
      "present": false
    }
  • D7Pass

    Multi-page stability

    4/4
    What we captured
    {
      "nonOk": [],
      "slowPages": 0,
      "pagesCrawled": 1,
      "consistentTemplate": true
    }
59C
Discovery & access22/25
Understanding17/25
Actionability7/25
Trust & freshness13/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 igear.com with another site →