Title: Adding the “Accept: text/markdown” header
Last modified: May 27, 2026

---

# Adding the “Accept: text/markdown” header

 *  [shurup](https://wordpress.org/support/users/shurup/)
 * (@shurup)
 * [4 days ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/)
 * Hi! First of all, thanks a lot for your wonderful plugin, it does it job perfectly!
 * I wanted to suggest adding the “Accept: text/markdown” header to all website 
   content that features a markdown version. According to the [Accept markdown](https://acceptmarkdown.com/),
   this header is required to make the content more AI-ready. Currently, when this
   test is invoked against the content served with the plugin (I’m using [this article](https://palark.com/blog/autoscalable-gitlab-runners-on-aws-ec2/)
   as an example), it fails immediately due to the absence of this header.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fadding-the-accept-text-markdown-header%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [Michael Sablone](https://wordpress.org/support/users/michaelsablone/)
 * (@michaelsablone)
 * [3 days, 13 hours ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/#post-18921206)
 * Will definitely consider this in the next release!
 *  Plugin Author [Michael Sablone](https://wordpress.org/support/users/michaelsablone/)
 * (@michaelsablone)
 * [3 days, 12 hours ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/#post-18921216)
 * Thanks for the suggestion. I agree the `Accept: text/markdown` pattern is becoming
   more common for AI-oriented content negotiation, and I did spend some time evaluating
   it.
 * At the moment, I’m intentionally not implementing that behavior because I think
   the operational risk outweighs the upside for a WordPress plugin intended to 
   run across a wide variety of hosting and caching environments.
 * The plugin currently uses explicit `.md` routes instead, which are much safer
   and more predictable from a caching and infrastructure perspective.
 * Serving Markdown conditionally from the same URL based on the `Accept` header
   introduces a number of edge cases:
    - CDN/cache variation requirements (`Vary: Accept`)
    - Reverse proxy compatibility
    - Cache poisoning or stale cache scenarios
    - Hosts that ignore or mishandle content negotiation
    - The possibility of Markdown accidentally being cached and served to normal
      browsers
 * On highly cached WordPress sites, especially with Cloudflare, Varnish, Nginx 
   microcache, or aggressive edge caching, this could realistically result in broken
   page output if misconfigured.
 * Because of that, I’m currently treating `.md` URLs plus the existing `<link rel
   ="alternate" type="text/markdown">` output as the safer and more deterministic
   implementation.
 * I may revisit this later as an optional advanced setting, but I don’t currently
   feel comfortable enabling negotiated Markdown responses by default.
 *  Thread Starter [shurup](https://wordpress.org/support/users/shurup/)
 * (@shurup)
 * [3 days, 5 hours ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/#post-18921490)
 * Sounds totally fair; thanks a lot for this detailed answer!
 *  Plugin Author [Michael Sablone](https://wordpress.org/support/users/michaelsablone/)
 * (@michaelsablone)
 * [2 days, 22 hours ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/#post-18922023)
 * More thinking: while i’m hesitant to enable `Accept: text/markdown` content negotiation
   by default, I agree there are valid advanced use cases, so I’m considering exposing
   it behind a developer filter. That would let site owners explicitly opt in once
   they’ve confirmed their cache layer respects `Vary: Accept`. Do you have the 
   ability to add in your own custom hooks?

Viewing 4 replies - 1 through 4 (of 4 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fadding-the-accept-text-markdown-header%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/llm-markdown/assets/icon-256x256.png?rev=3470711)
 * [LLM Markdown – Expose Content as .md](https://wordpress.org/plugins/llm-markdown/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/llm-markdown/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/llm-markdown/)
 * [Active Topics](https://wordpress.org/support/plugin/llm-markdown/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/llm-markdown/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/llm-markdown/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Michael Sablone](https://wordpress.org/support/users/michaelsablone/)
 * Last activity: [2 days, 22 hours ago](https://wordpress.org/support/topic/adding-the-accept-text-markdown-header/#post-18922023)
 * Status: not resolved