Skip to content

AI-answer optimization

Hand agents the Markdown, not the layout

Serve a Markdown copy of each content page when a request asks for text/markdown, or at the same path plus .md. Keep the words identical to the HTML, send Vary: Accept so caches keep the two apart, and name the HTML page as canonical in the Link header. Agents get a clean read, and nothing competes with the original.

By The Marketinque TeamReviewed June 2026

Step 1.3.3.6 Serve a Markdown version of each content page to agents that ask for it in the SaaS launch checklist · phase 1, Ship-ready

The play

When an agent fetches a page for its user and asks for Markdown, answer with the same text as plain Markdown instead of the full HTML. It reads your words rather than your menus and scripts, and the copy stays tied to the HTML page as its canonical.

How to run it

  1. Render the Markdown from the same source as the HTML, so the two cannot drift.
  2. Answer Accept: text/markdown on the page URL, and the same path plus .md, with Content-Type text/markdown.
  3. Send Vary: Accept on both versions, so a cache never hands the Markdown to a browser.
  4. Add an HTTP Link header naming the HTML page as canonical. A Markdown file has no head to put the tag in.
  5. List the .md URLs in llms.txt, and keep the Markdown out of the sitemap.
  6. Test it: request a page with the header and confirm the type, the Vary header and the canonical.

Watch out for

  • Never add words to the Markdown that the HTML lacks. A version only machines see is cloaking, whatever the format.
  • This helps agents read you. It is not a ranking lever, and no search engine documents ranking on it.

Best for

Make this concrete for your product

Try the free idea finder now, or drop your email and we’ll run plays like this for your product end to end.

Tailor it to your product

Plays like this one

Sources

  1. llms.txt — a proposed standard
  2. MDN: HTTP content negotiation

Compiled by The Marketinque Team to our editorial standards.