adxtech.com

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.

{
  "present": true,
  "anyLinks": 0,
  "llmsFullTxt": true,
  "describedLinks": 0
}

Your robots.txt welcomes these agents, but GPTBot received 403, ClaudeBot received 403, PerplexityBot received 403 — the block is happening at your CDN or WAF, before robots.txt is ever read. Cloudflare in particular blocks AI crawlers by default on every plan. One setting change, and it is invisible until someone tests it.

{
  "probes": [
    {
      "name": "GPTBot",
      "status": 403,
      "ttfbMs": 117
    },
    {
      "name": "ClaudeBot",
      "status": 403,
      "ttfbMs": 114
    },
    {
      "name": "PerplexityBot",
      "status": 403,
      "ttfbMs": 54
    }
  ],
  "medianTtfbMs": 114,
  "edgeBlockingDespiteRobots": true
}

An agent fetching your HTML sees almost nothing — 15 characters against 217 after rendering. Everything downstream of this is affected: schema an agent never receives may as well not exist. This is the single highest-value fix on the report, and the most involved.

{
  "ratio": 0.069,
  "rawTextLength": 15,
  "renderedTextLength": 217
}

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.

{
  "pagesCrawled": 1,
  "pagesWithValidJsonLd": 0,
  "homepageHasValidJsonLd": false,
  "pagesWithInvalidJsonLd": 0
}

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

{
  "matched": [],
  "missing": [
    "Organization or WebSite sitewide",
    "type-specific markup (Article, FAQPage, Service, SoftwareApplication)"
  ],
  "siteType": "other",
  "typesFound": []
}

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.

{
  "problems": [
    "https://adxtech.com: 0 h1 elements",
    "https://adxtech.com: missing main, nav, footer"
  ],
  "singleH1": 0,
  "allLandmarks": 0,
  "pagesCrawled": 1,
  "noSkippedLevels": 1
}

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

{
  "goodTitles": 0,
  "pagesCrawled": 1,
  "uniqueTitles": true,
  "goodDescriptions": 0,
  "completeOpenGraph": 0
}

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

{
  "hostVariants": [
    {
      "url": "https://www.adxtech.com",
      "status": 200
    },
    {
      "url": "http://adxtech.com",
      "status": 200
    }
  ],
  "pagesCrawled": 1,
  "selfConsistentCanonicals": 0
}

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.

{
  "formsFound": 0
}

Fix: too few real anchor elements found; no breadcrumbs or clear URL hierarchy.

{
  "anchors": 0,
  "genericLinks": 0,
  "genericRatio": 0,
  "hasBreadcrumb": false,
  "clickableNonAnchors": 0
}

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.

{
  "found": []
}

Not a commerce site; these points are redistributed across C1–C4.

{
  "siteType": "other"
}

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.

{
  "searchForm": false,
  "searchAction": false
}

Fix: no Strict-Transport-Security header.

{
  "hsts": false,
  "tlsValid": true,
  "mixedContentReferences": 0
}

Fix: no contact page or mailto link found; no Organization schema. sameAs links to a company profile are how a model corroborates that you are who the page says you are.

{
  "sameAsCount": 0,
  "contactDiscoverable": false,
  "hasOrganizationSchema": false
}

Fix: no privacy policy linked; no terms page linked.

{
  "hasTerms": false,
  "siteType": "other",
  "hasPrivacy": false,
  "hasReturns": false,
  "hasShipping": false
}

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.

{
  "sitemapUrls": 1,
  "withLastmod": 0,
  "visibleDates": false,
  "modifiedLast90Days": 0
}

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

{
  "title": "",
  "hasFavicon": false,
  "hasOgImage": false,
  "ogSiteName": "",
  "schemaName": ""
}

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.

{
  "valid": false,
  "hasContact": false
}

Fix: 1 page(s) did not return 200: https://adxtech.com/lander (403).

{
  "nonOk": [
    {
      "url": "https://adxtech.com/lander",
      "status": 403
    }
  ],
  "slowPages": 0,
  "pagesCrawled": 2,
  "consistentTemplate": true
}