Agent readiness report
abd.net
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.
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.
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.
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.
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.
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.
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/2What we captured
{ "groups": 139, "status": 200, "sitemaps": 3 } - A2Pass
Major AI crawlers allowed
6/6What we captured
{ "of": 6, "allowed": 6, "blocked": [] } - A3Pass
XML sitemap valid and referenced
3/3What we captured
{ "exists": true, "urlCount": 38, "referencedInRobots": true } - A4Partial
llms.txt present
1/4llms.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": 34, "llmsFullTxt": false, "describedLinks": 0 } - A5Pass
Bot user-agent HTTP health
3/3What we captured
{ "probes": [ { "name": "GPTBot", "status": 200, "ttfbMs": 823 }, { "name": "ClaudeBot", "status": 200, "ttfbMs": 716 }, { "name": "PerplexityBot", "status": 200, "ttfbMs": 743 } ], "medianTtfbMs": 743, "edgeBlockingDespiteRobots": false } - A6Fail
No hard interstitial
0/2Detected: CAPTCHA, Cookie wall. 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": [ "CAPTCHA", "Cookie wall" ] } - A7Pass
Server-rendered content parity
5/5What we captured
{ "ratio": 1, "rawTextLength": 16324, "renderedTextLength": 10447 }
BUnderstanding
- B1Pass
JSON-LD present and valid
5/5What we captured
{ "pagesCrawled": 1, "pagesWithValidJsonLd": 1, "homepageHasValidJsonLd": true, "pagesWithInvalidJsonLd": 0 } - B2Partial
Correct schema types for the site type
2/5Missing: 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", "EntryPoint", "GeoCoordinates", "ImageObject", "ListItem", "LocalBusiness", "OpeningHoursSpecification", "Organization", "PostalAddress", "PropertyValueSpecification", "ReadAction", "SearchAction", "WebPage", "WebSite" ] } - B3Pass
Semantic HTML structure
4/4What we captured
{ "problems": [], "singleH1": 1, "allLandmarks": 1, "pagesCrawled": 1, "noSkippedLevels": 1 } - B4Pass
Meta and Open Graph
3/3What we captured
{ "goodTitles": 1, "pagesCrawled": 1, "uniqueTitles": true, "goodDescriptions": 1, "completeOpenGraph": 1 } - B5Partial
Clean text ratio
2/3Visible text is 6.8% 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.068 ], "averageRatio": 0.068 } - B6Partial
Alt text coverage
1/217 of 72 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": 55, "coverage": 0.76, "contentImages": 72 } - B7Pass
Canonical and duplication hygiene
3/3What we captured
{ "hostVariants": [ { "url": "https://www.abd.net", "status": 200 }, { "url": "http://abd.net", "status": 301, "location": "https://abd.net/" } ], "pagesCrawled": 1, "selfConsistentCanonicals": 1 }
CActionability
- C1Partial
Form usability
3.67/6.11No 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
1.22/4.89Fix: 1 clickable element(s) that are not anchors — an agent cannot follow a div; 15% of links use contextless text like "click here".
What we captured
{ "anchors": 124, "genericLinks": 19, "genericRatio": 0.15, "hasBreadcrumb": true, "clickableNonAnchors": 1 } - C3Partial
Interactive element semantics
2.44/4.89Fix: 1 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": 25, "positiveTabindex": 0, "clickableNonButtons": 1, "keyboardTrapsTested": false } - C4Fail
Machine endpoints and agent manifests
0/6.11No 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/4Not a commerce site; these points are redistributed across C1–C4.
What we captured
{ "siteType": "other" } - C6Partial
On-site search
2/3Search 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
- D1Partial
Transport security
3/4Fix: no Strict-Transport-Security header.
What we captured
{ "hsts": false, "tlsValid": true, "mixedContentReferences": 0 } - D2Pass
Verifiable identity
4/4What we captured
{ "sameAsCount": 3, "contactDiscoverable": true, "hasOrganizationSchema": true } - D3Pass
Policies discoverable
4/4What we captured
{ "hasTerms": true, "siteType": "other", "hasPrivacy": true, "hasReturns": false, "hasShipping": false } - D4Pass
Freshness signals
4/4What we captured
{ "sitemapUrls": 38, "withLastmod": 38, "visibleDates": true, "modifiedLast90Days": 15 } - D5Partial
Identity consistency
1/3Fix: 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": "Ultra-Staff EDGE | Staffing and Recruiting Software", "hasFavicon": true, "hasOgImage": true, "ogSiteName": "Automated Business Designs", "schemaName": "Ultra-Staff EDGE | Staffing and Recruiting Software" } - D6Fail
security.txt
0/2Publish /.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 } - D7Partial
Multi-page stability
2/4Fix: 1 page(s) did not return 200: https://abd.net/%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E:%20%20Illegal%20string%20offset%20'url'%20in%20%3Cb%3E/home/forge/www.abd.net/public/wp-content/uploads/cache/ce0fbbccc1ac865263cb50096a69636d6767a9eb.php%3C/b%3E%20on%20line%20%3Cb%3E312%3C/b%3E%3Cbr%20/%3E (404).
What we captured
{ "nonOk": [ { "url": "https://abd.net/%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E:%20%20Illegal%20string%20offset%20'url'%20in%20%3Cb%3E/home/forge/www.abd.net/public/wp-content/uploads/cache/ce0fbbccc1ac865263cb50096a69636d6767a9eb.php%3C/b%3E%20on%20line%20%3Cb%3E312%3C/b%3E%3Cbr%20/%3E", "status": 404 } ], "slowPages": 0, "pagesCrawled": 2, "consistentTemplate": true }
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.