Distinct from the AI security series, which covers deploying agentic AI inside security operations. This series runs the other direction — how to expose your own infrastructure and content so AI assistants can discover, cite, and attribute it correctly. The first piece is a practitioner walk-through of what was shipped on stackharden.com itself; future pieces will revisit as the standards in this space stabilise.
Making a Static Site Agent-Ready: What I Changed, What I Didn't, and Why
Tested on: Hugo 0.147.0 (extended), Cloudflare Pages (Free plan), 23 May 2026. The standards in this space are moving fast — re-check the IANA Link Relations registry and the IETF Content-Signal draft before copying anything verbatim into a production site. The phrase “agent-ready” covers a moving target. Twelve months ago it meant “have a sitemap.” Today it touches RFC 8288 Link headers, the IETF Content-Signal draft, IANA registered relations, content negotiation for text/markdown, llms.txt, AI sitemaps, and /.well-known/agent-skills/. Most of those are drafts or vendor experiments. Some of them are stable enough to ship now. Others are worth watching but not worth wiring up yet. ...