Use the Accept Header to Serve Markdown Instead of HTML to LLMs
1–10 of 64 posts
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#2- https://x.com/bunjavascript/status/1971934734940098971
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#3There was a lot of conversation about this on X over the last couple days and the `Accept` request header including "text/markdown, text/plain" has emerged as kind of a new standard for AI agents requesting content such that they don't burn unnecessary inference compute processing HTML attributes and CSS. - https://x.com/bunjavascript/status/1971934734940098971 - https://x.com/thdxr/status/1972421466953273392 - https…
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#4There was a lot of conversation about this on X over the last couple days and the `Accept` request header including "text/markdown, text/plain" has emerged as kind of a new standard for AI agents requesting content such that they don't burn unnecessary inference compute processing HTML attributes and CSS. - https://x.com/bunjavascript/status/1971934734940098971 - https://x.com/thdxr/status/1972421466953273392 - https…
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#5Humans get HTML, bots get markdown. Two tiny tweaks I’d make...
Send Vary: Accept so caches don’t mix Markdown and HTML.
Expose it with a Link: …; rel="alternate"; type="text/markdown" so it’s easy to discover.
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#6Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#7I think there is a problem of incentive here. When we made our websites Search Engine Optimized, the incentive was for google to understand our content, and bring traffic our way. When you make your content optimized for LLM, it only improves their product, and you get nothing in return.
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#8I think there is a problem of incentive here. When we made our websites Search Engine Optimized, the incentive was for google to understand our content, and bring traffic our way. When you make your content optimized for LLM, it only improves their product, and you get nothing in return.
This isn't true. ChatGPT and Gemini link to sites in a similar way to how search engines have always done it. You can see the traffic show up in ahrefs or semrush.
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#9Earlier quoted context omitted.
This isn't true. ChatGPT and Gemini link to sites in a similar way to how search engines have always done it. You can see the traffic show up in ahrefs or semrush.
I had a call with a new user for a SaaS product that I sell recently. During the call he mentioned that he found it by typing what he was looking for into Gemini, and it recommended my app. I don't do anything special for llms, and the public-facing part of the website has been neglected for longer than I like to admit, so I was delighted. I had never considered that AI could send new users to me rather than pull the…
Re: Use the Accept Header to Serve Markdown Instead of HTML to LLMs
#10I think there is a problem of incentive here. When we made our websites Search Engine Optimized, the incentive was for google to understand our content, and bring traffic our way. When you make your content optimized for LLM, it only improves their product, and you get nothing in return.
This isn't true. ChatGPT and Gemini link to sites in a similar way to how search engines have always done it. You can see the traffic show up in ahrefs or semrush.