Menu

Agent readiness report

surelocktechnology.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. 1B1

    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.

  2. 2B2

    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.

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

    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.

Every check, with the evidence

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

ADiscovery & access

  • A1Fail

    robots.txt exists and parses

    0/2

    robots.txt exists but contains no parseable directives. Check for HTML being served in its place.

    What we captured
    {
      "bytes": 635965,
      "status": 200,
      "directives": 0
    }
  • A2Pass

    Major AI crawlers allowed

    6/6
    What we captured
    {
      "of": 6,
      "allowed": 6,
      "blocked": []
    }
  • 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
    }
  • 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": 174
        },
        {
          "name": "ClaudeBot",
          "status": 200,
          "ttfbMs": 190
        },
        {
          "name": "PerplexityBot",
          "status": 200,
          "ttfbMs": 117
        }
      ],
      "medianTtfbMs": 174,
      "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": 8687,
      "renderedTextLength": 6854
    }

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": 6,
      "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": []
    }
  • B3Pass

    Semantic HTML structure

    4/4
    What we captured
    {
      "problems": [],
      "singleH1": 6,
      "allLandmarks": 6,
      "pagesCrawled": 6,
      "noSkippedLevels": 6
    }
  • B4Partial

    Meta and Open Graph

    2/3

    Fix: duplicate titles across pages.

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

    Clean text ratio

    3/3
    What we captured
    {
      "perPage": [
        0.119,
        0.119,
        0.119,
        0.119,
        0.119,
        0.119
      ],
      "averageRatio": 0.119
    }
  • B6Pass

    Alt text coverage

    2/2
    What we captured
    {
      "withAlt": 120,
      "coverage": 0.95,
      "contentImages": 126
    }
  • B7Partial

    Canonical and duplication hygiene

    1/3

    Fix: 5 page(s) missing or with a mismatched rel=canonical. Duplicate hosts split whatever authority the page has earned.

    What we captured
    {
      "hostVariants": [
        {
          "url": "https://www.surelocktechnology.com",
          "status": 301,
          "location": "https://surelocktechnology.com"
        },
        {
          "url": "http://surelocktechnology.com",
          "status": 301,
          "location": "https://surelocktechnology.com/"
        }
      ],
      "pagesCrawled": 6,
      "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": 79,
      "genericLinks": 1,
      "genericRatio": 0.01,
      "hasBreadcrumb": false,
      "clickableNonAnchors": 0
    }
  • C3Pass

    Interactive element semantics

    4/4
    What we captured
    {
      "realButtons": 9,
      "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

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

    Policies discoverable

    2/4

    Fix: shipping and returns pages not both linked.

    What we captured
    {
      "hasTerms": false,
      "siteType": "ecommerce",
      "hasPrivacy": true,
      "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
    }
  • 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 Support Services in Atlanta",
      "hasFavicon": true,
      "hasOgImage": true,
      "ogSiteName": "SureLock Technology",
      "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": 6,
      "consistentTemplate": true
    }
53D
Discovery & access17/25
Understanding12/25
Actionability10/25
Trust & freshness14/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 surelocktechnology.com with another site →