# AI readiness of craighill.co
> Measured on the home page. Overall grade: Good.
Score 70/100, grade Good. Measured 2026-09-10T19:05:25.038+00:00, engine axrush-engine@6.0.0.
## Checks
### Content — 80/100
#### Content Negotiation — 0/100
- **FAIL** Homepage does not serve Markdown via content negotiation
Got text/html (HTTP 200) for "Accept: text/markdown"
Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
https://axrush.com/guides/content-negotiation#not-supported
- **WARN** No fallback found on the homepage
If you cannot enable content negotiation, advertise a Markdown version with so agents can discover it.
https://axrush.com/guides/content-negotiation#no-alternate
#### Structured Data — 90/100
- **PASS** 2 JSON-LD block(s) found
- **PASS** @context references schema.org
- **WARN** No @graph array (single-entity only)
Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
https://axrush.com/guides/structured-data#no-graph
- **PASS** Key types found: Organization, WebSite
- **WARN** No BreadcrumbList found
Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
https://axrush.com/guides/structured-data#no-breadcrumb
- **WARN** No author declared in structured data
An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
https://axrush.com/guides/structured-data#no-author
- **PASS** 3 sameAs link(s) tie your entity to external identifiers
, https://www.instagram.com/craighillcompany/, https://www.youtube.com/@craighillcompany
- **WARN** No dateModified or datePublished in structured data
Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.
https://axrush.com/guides/structured-data#no-dates
#### HTML Rendering — 95/100
- **PASS** Server-rendered content detected (647 words, 4210 chars of visible text)
- **WARN** Markup-heavy page (text is 2.9% of structural markup)
Recommended minimum: 5%. The content thresholds are met, so this does not move the score.
The visible text clears the content thresholds, so agents can read this page. Trimming wrapper markup would still make it cheaper to consume.
https://axrush.com/guides/html-rendering#low-ratio
- **PASS** Semantic landmarks present (main, section, header, footer, nav)
- **WARN** 3
headings found (recommend exactly 1)
Use a single
per page to clearly mark the primary topic. Demote secondary headings to
+.
https://axrush.com/guides/html-rendering#multiple-h1
- **PASS** 60/61 tags have alt attributes
#### SEO Basics — 82/100
- **WARN** is too short (9 chars): "Craighill"
Lengthen the title to 20-70 characters with a clear topic indicator.
https://axrush.com/guides/seo-basics#short-title
- **WARN** Meta description is short (34 chars)
Expand the description to 70-160 characters with the page's main value proposition.
https://axrush.com/guides/seo-basics#short-description
- **PASS** Canonical URL: https://craighill.co/
- **PASS** <html lang="en">
- **PASS** UTF-8 charset declared
- **PASS** Viewport meta present: "width=device-width,initial-scale=1"
#### Agent Operability — 90/100
- **PASS** 85/86 interactive elements have an accessible name
- **PASS** 3/3 form controls are labelled
- **WARN** 1/1 iframes have no title
An untitled frame is an opaque region. A title tells an agent whether it is worth entering.
https://axrush.com/guides/agent-operability#iframe-no-title
- **WARN** 58/61 images, frames or videos have no declared dimensions
Undeclared dimensions shift the layout as media loads. An agent working from a screenshot clicks where the button was a moment ago. Set width and height, or aspect-ratio.
https://axrush.com/guides/agent-operability#unsized-media
- **PASS** Method note: this reads markup, not a rendered accessibility tree
Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.
### Access — 97/100
#### TLS / HTTPS — 87/100
- **PASS** Site is served over HTTPS
- **PASS** HTTP requests redirect to HTTPS
- **WARN** HSTS max-age is short (7889238s = ~91 days)
Use at least max-age=15768000 (~6 months); preload list submission requires max-age=31536000 (1 year).
https://axrush.com/guides/tls-https#hsts-short
- **WARN** HSTS does not include subdomains
Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.
https://axrush.com/guides/tls-https#hsts-no-subdomains
- **WARN** HSTS lacks the preload directive
Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
https://axrush.com/guides/tls-https#hsts-no-preload
#### Agent Access — 100/100
- **PASS** All 10 core AI crawler user-agents receive the same page as a regular client
#### HTTP Hygiene — 100/100
- **PASS** Missing pages return 404
- **PASS** Homepage answers without a redirect
- **PASS** HEAD requests are supported
- **PASS** Content-Type: text/html with charset
#### Crawl Efficiency — 80/100
- **PASS** Response compressed with Brotli (br)
- **PASS** Cache validator present (ETag)
- **WARN** Conditional request returned 200 instead of 304 Not Modified
Re-requested with If-None-Match
The server advertises a cache validator but does not honor If-None-Match / If-Modified-Since. Configure it to return 304 when the validator matches, so crawlers avoid re-downloading unchanged pages.
https://axrush.com/guides/crawl-efficiency#no-304
- **WARN** Homepage is on the large side (604.2 KB decompressed)
Consider trimming inlined payloads to reduce crawl cost.
https://axrush.com/guides/crawl-efficiency#large-page
- **WARN** Roughly 1,053 tokens of content in 154,483 tokens of response (99% markup)
Estimated at four characters per token.
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 191ms
#### AI Directives — 100/100
- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page
### Discovery — 78/100
#### LLMs.txt — 100/100
- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/markdown)
- **PASS** H1 heading: "Agent Instructions — Craighill"
- **WARN** No blockquote description found ("> ...")
Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
https://axrush.com/guides/llms-txt#missing-blockquote
- **PASS** 5 section heading(s) found
- **PASS** 5 link(s) found
- **PASS** /llms-full.txt also available (bonus)
- **WARN** No rel="describedby" link to llms.txt
llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
https://axrush.com/guides/llms-txt#no-describedby
- **WARN** 2 duplicate link(s) in llms.txt
Each URL should appear once. Duplicates spend an agent’s budget re-reading what it already has.
https://axrush.com/guides/llms-txt#duplicate-links
- **PASS** 3 sampled link(s) resolve
- **WARN** 1 sampled link(s) redirect
https://www.shopify.com → https://www.shopify.com/es-es
Point llms.txt at the final URL. Each redirect is a round trip the agent pays for on every visit.
https://axrush.com/guides/llms-txt#redirecting-links
- **WARN** No per-page Markdown mirror found
Tried /index.md and /index.html.md.
llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.
#### Robots.txt — 60/100
- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
https://axrush.com/guides/robots-txt#no-core-crawlers
- **PASS** Sitemap directive present
- **WARN** No Content-Signal directive found (optional)
Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
https://axrush.com/guides/robots-txt#low-coverage
#### Sitemap — 100/100
- **PASS** Sitemap located: https://craighill.co/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** Sitemap-index references 5 child sitemap(s)
- **PASS** 3/3 sample child sitemap(s) reachable
- **PASS** Sample yielded 118 URL(s) across 3 child(ren)
- **PASS** Newest <lastmod> is recent (0 day(s) ago)
#### Meta Tags — 52/100
- **WARN** No AI meta tags (ai:*) found
Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** No rel="alternate" link to llms.txt in HTML
Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** No rel="alternate" link to the Agent Card in HTML
Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** No rel="me" identity links found
Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
https://axrush.com/guides/meta-tags#no-rel-me
- **PASS** OpenGraph required tags present (og:title, og:description, og:url, og:type)
- **PASS** Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
- **WARN** Twitter Card recommended tags missing: twitter:image
Add twitter:image for richer previews.
https://axrush.com/guides/meta-tags#twitter-recommended-missing
#### HTTP Headers — 85/100
- **PASS** 5/7 security headers present
- **WARN** Link header present but does not reference AI discovery files
Add AI discovery entries to your Link header: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
https://axrush.com/guides/http-headers#no-ai-discovery
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
https://axrush.com/guides/http-headers#discovery-relations
### Protocols — 7/100
#### Agent Card (A2A) — 0/100
- **FAIL** /.well-known/agent-card.json not found
Site is agent-facing (an API surface (navigation into an API or developer area)). Also tried the pre-0.3 path /.well-known/agent.json. IANA-registered well-known URI.
This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
https://axrush.com/guides/agent-card#not-found
#### OpenAPI Spec — 0/100
- **FAIL** API surface present but no machine-readable description found
Evidence of an API: navigation into an API or developer area. Checked /.well-known/api-catalog, Link and <link> rel="service-desc", and /.well-known/openapi.json, /openapi.json, /openapi.yaml, /.well-known/openapi.yaml, /api/openapi.json, /v1/openapi.json, /swagger.json, /api-docs, /asyncapi.json, /arazzo.json
The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
https://axrush.com/guides/api-discovery#not-found
#### MCP (Model Context Protocol) — N/A
- **PASS** No MCP server — MCP discovery does not apply to this site
A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.
#### AI Catalog — 0/100 (reports, does not score)
- **WARN** No agent resource catalog found
Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
https://axrush.com/guides/ai-catalog#not-found
#### Agent Skills — 0/100
- **WARN** No Agent Skills published
Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
https://axrush.com/guides/agent-skills#not-found
#### Commerce Discovery — 75/100 (reports, does not score)
- **PASS** UCP profile published at /.well-known/ucp
Vendor convention, not IANA-registered. Google-led, adopted by Shopify, Etsy, Walmart and Stripe. Not IANA-registered.
- **PASS** UCP version 2026-08-25
- **PASS** 1 commerce service(s) declared: dev.ucp.shopping
- **PASS** 2 declared schema URL(s) resolve
- **WARN** UCP profile declares no payment handlers
Without a payment handler an agent can read your catalog but cannot complete a purchase. Declare the handlers you accept.
https://axrush.com/guides/commerce-discovery#no-payment-handlers
- **WARN** UCP profile declares no signing keys
Publish the public keys an agent uses to verify your responses. Money is moving; identity should not rest on DNS alone.
https://axrush.com/guides/commerce-discovery#no-keys
#### Auth Discovery — 70/100
- **PASS** Protected-resource metadata published (RFC 9728)
IANA-registered well-known URI.
- **PASS** 1 authorization server(s) named
- **FAIL** Authorization server https://shopify.com publishes no discovery metadata
Checked /.well-known/oauth-authorization-server and /.well-known/openid-configuration
The chain stops here: an agent knows which server to ask but not which endpoints it has. Publish RFC 8414 or OpenID discovery metadata.
https://axrush.com/guides/auth-discovery#no-server-metadata
#### WebMCP — 100/100 (reports, does not score)
- **WARN** 4 form(s) on the page, none declared as agent tools
WebMCP is a W3C Community Group draft in a Chrome origin trial. It is not a standard and adoption is minimal, so this is a forward-looking note, not a defect.
A declared form is called by an agent rather than driven pixel by pixel. Add toolname and tooldescription to the forms worth automating — search, filter, subscribe — and toolparamdescription to each field.
https://axrush.com/guides/webmcp#no-annotations
### Policy — 18/100
#### Security.txt — 0/100
- **FAIL** /.well-known/security.txt not found
HTTP 404
Create a /.well-known/security.txt file per RFC 9116. At minimum, include Contact: and Expires: fields. See https://securitytxt.org/ for a generator.
https://axrush.com/guides/security-txt#not-found
#### RSL License — 0/100
- **FAIL** No RSL license discovery found
Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
https://axrush.com/guides/rsl#not-found
#### Usage Policy — 40/100
- **WARN** No machine-readable usage policy declared
Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
https://axrush.com/guides/usage-policy#no-policy
---
Markdown representation of https://axrush.com/report/craighill.co