`. If we want every fetch to include a pointer to `llms.txt`, it's not enough to have a link in our ``. I now insert a `LLMDiscoveryNote.astro` component immediately after the opening `

` on every page. It's pretty simple: ```astro ``` The *"For AI agents and crawlers"* isn't just for agents and crawlers. It'll be read aloud by screen readers so the text is clear about who it's for. *If anyone knows of a reliable way to hide stuff from screen readers but not from crawlers/agents please yell.* We should do the same for our markdown versions. Let's add this to the top of them all: ```md > For the complete site index, see [llms.txt](https://danny.is/llms.txt) ``` ### 3. Serve markdown to UAs asking for it Since user agents can send an [`Accept` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation) with their requests and we already have markdown versions of our content, we should probably serve markdown to anyone requesting plain ol' `/writing/` URLs with an `Accept: text/markdown` header. We can do this for both notes and articles with a little addition to our vercel config: ```jsonc { "src": "^/writing/([^/]+)/?$", "has": [{ "type": "header", "key": "accept", "value": ".*text/markdown.*" }], "dest": "/writing/$1.md", "headers": { "content-type": "text/markdown; charset=utf-8" } } ``` Browsers never send `Accept: text/markdown` so they're unaffected by this, but we need to make sure "negotiable URLs" like this carry `Vary: Accept` so CDNs don't accidentally serve markdown when they shouldn't. While we're here, we can also respond to `Accept: text/markdown` requests to the root of `danny.is` with the contents of our `llms.txt` rather than our homepage HTML. ### 4. Advertise the index Even More Since llms.txt is so important, let's also add a `Link` header to every response and a `` tag to every HTML document: ``` Link: ; rel="describedby" ``` ```html ``` ### 5. Make it easier to discover markdown versions Our `llms.txt` currently includes a big old list of markdown links to all our content, but the URLs point at the *HTML* versions. It makes much more sense to use the `.md` URLs in this context. So now the links in `llms.txt` point to markdown versions if they exist. While we're here, we should make sure content pages include a ``. ### 6. Turn meta-refresh redirects into propa HTTP redirects I use redirects in two places on this site: 1. Those hard-coded in `redirects.ts` which forward URLs like https://danny.is/meeting to external services. 2. Articles with a `redirectURL` frontmatter property which forward to content hosted elsewhere. I use [Astro redirects](https://docs.astro.build/en/guides/routing/#configured-redirects) for the former and meta-refresh for the latter, though since this is a statically generated site they all end up as HTML meta-refresh pages in the generated `/dist`. We can improve on this by having our `astro build` *also* generate a host-agnostic `dist/redirects.json` containing **all** of these, in this kinda form: ```json { "version": 1, "redirects": [{ "source": "/meeting", "destination": "https://cal.com/dannysmith", "status": 302 }] } ``` Then as part of our Vercel-specific deployment action we can use this to generate an appropriate [Build Output API](https://vercel.com/docs/build-output-api) config which returns proper `302` redirects for these routes. The meta-refresh pages stay in the static build for the sake of portability, as does `dist/redirects.json` which is the *source of truth* about how server-side redirects should work. ## So where did we end up? These little tweaks ended up making quite a difference to our audit metrics. ```bash → bunx afdocs check https://danny.is --verbose ... 16 passed, 3 warnings, 3 failed, 1 skipped (23 total) ``` The remaining warnings & failures are all false positives as far as I'm concerned. The `isitagentready` audit jumped from a score of ~20 to 43 overall, with all the things I care about now showing "green" ([check it out](https://isitagentready.com/danny.is)). ![isitagentready.com showing danny.is at a score of 43, with the content and discovery checks I care about passing](../../assets/articles/2026-06-19-isagentready.png) Most of the "failures" here have to do with API, Auth, MCP & Skill Discovery. Not only are these extremely new/immature standards, they're also not very relevant to content-first websites like this one. ## Wrapping up None of this was difficult to do, but it did require a few minutes actually thinking about how agents consume content on a site like this. I think my biggest takeaway here is that it doesn't really matter whether `/llms.txt` is adopted as a standard by harness-makers, in the same way it doesn't really matter about RSS vs Atom feeds. But it **does** matter that I – as a website owner – do my best to signpost users appropriately so they know where to find stuff.