Menu

Agent readiness report

computerhelper.org

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

    JSON-LD present and valid

    High impact · Medium effort

    Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.

  3. 3B2

    Correct schema types for the site type

    High impact · Medium effort

    Missing: Organization or WebSite sitewide; 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.

  4. 4C1

    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.

  5. 5C4

    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.

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": 10,
      "status": 200,
      "sitemaps": 0
    }
  • 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"
      ]
    }
  • 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

    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": 246
        },
        {
          "name": "ClaudeBot",
          "status": 403,
          "ttfbMs": 79
        },
        {
          "name": "PerplexityBot",
          "status": 403,
          "ttfbMs": 75
        }
      ],
      "medianTtfbMs": 79,
      "edgeBlockingDespiteRobots": false
    }
  • 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

  • B1Fail

    JSON-LD present and valid

    0/5

    Add JSON-LD to the homepage. Organization or WebSite is the baseline, and it is what tells a machine who you are rather than making it infer that from prose.

    What we captured
    {
      "pagesCrawled": 1,
      "pagesWithValidJsonLd": 0,
      "homepageHasValidJsonLd": false,
      "pagesWithInvalidJsonLd": 0
    }
  • B2Fail

    Correct schema types for the site type

    0/5

    Missing: Organization or WebSite sitewide; 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": [
        "Organization or WebSite sitewide",
        "type-specific markup (Product, Offer)"
      ],
      "siteType": "ecommerce",
      "typesFound": []
    }
  • B3Fail

    Semantic HTML structure

    0/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://computerhelper.org: 16 h1 elements",
        "https://computerhelper.org: skipped heading level",
        "https://computerhelper.org: missing main"
      ],
      "singleH1": 0,
      "allLandmarks": 0,
      "pagesCrawled": 1,
      "noSkippedLevels": 0
    }
  • B4Partial

    Meta and Open Graph

    1/3

    Fix: 1 description(s) outside 50–160 characters; 1 page(s) missing og:title, og:description or og:image.

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

    Clean text ratio

    2/3

    Visible text is 9.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.091
      ],
      "averageRatio": 0.091
    }
  • B6Fail

    Alt text coverage

    0/2

    11 of 11 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": 0,
      "coverage": 0,
      "contentImages": 11
    }
  • B7Partial

    Canonical and duplication hygiene

    2/3

    Fix: www/non-www or http/https variants do not resolve to one canonical host. Duplicate hosts split whatever authority the page has earned.

    What we captured
    {
      "hostVariants": [
        {
          "url": "https://www.computerhelper.org",
          "error": "fetch failed",
          "status": 0
        },
        {
          "url": "http://computerhelper.org",
          "status": 301,
          "location": "https://computerhelperga.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
    }
  • C2Partial

    Navigable link graph

    3/4

    Fix: no breadcrumbs or clear URL hierarchy.

    What we captured
    {
      "anchors": 32,
      "genericLinks": 0,
      "genericRatio": 0,
      "hasBreadcrumb": false,
      "clickableNonAnchors": 0
    }
  • C3Pass

    Interactive element semantics

    4/4
    What we captured
    {
      "realButtons": 0,
      "positiveTabindex": 0,
      "clickableNonButtons": 0,
      "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
    }
  • C6Fail

    On-site search

    0/3

    No on-site search found. If you have search, expose it as a GET form with a query parameter so an agent can jump straight to results.

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

DTrust & freshness

  • D1Partial

    Transport security

    3/4

    Fix: no Strict-Transport-Security header.

    What we captured
    {
      "hsts": false,
      "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": false,
      "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": 0,
      "withLastmod": 0,
      "visibleDates": false,
      "modifiedLast90Days": 0
    }
  • D5Fail

    Identity consistency

    0/3

    Fix: site name differs across title, og:site_name and schema name; no og:image. An unexplained name mismatch reads as a signal the site may not be what it claims.

    What we captured
    {
      "title": "computerhelperga.com |",
      "hasFavicon": true,
      "hasOgImage": false,
      "ogSiteName": "",
      "schemaName": ""
    }
  • 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
    }
  • D7Pass

    Multi-page stability

    4/4
    What we captured
    {
      "nonOk": [],
      "slowPages": 0,
      "pagesCrawled": 1,
      "consistentTemplate": true
    }
35F
Discovery & access10/25
Understanding5/25
Actionability10/25
Trust & freshness10/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 computerhelper.org with another site →