Skip to content
Content Formats and Agent APIs

Request Markdown Content for AI Agents

2 min read

citelayer® serves supported public content as Markdown when a client explicitly asks for that format. Ordinary visits continue to receive the normal page.

Three request methods

  • Add ?format=markdown to the published page URL.
  • Use a supported .md route for the content path.
  • Send the HTTP header Accept: text/markdown.
curl -i -H "Accept: text/markdown" https://example.com/article/

Enable and scope the output

Open the Markdown settings, enable the feature and select the supported public post types and archives. Per-post exclusions can hold content back. Review the scope settings when a request returns HTML.

Check an actual page

  1. Choose a published page that belongs to the configured scope.
  2. Request its Markdown and inspect Content-Type and body.
  3. Confirm headings, links and important product facts survived conversion.
  4. Change the content and verify the response updates; check cache ownership if it does not.

Interpret the result carefully

Markdown can reduce markup noise, but the saving depends on the source page. There is no universal token-reduction percentage. A clean response does not prove a model will request it or cite it. Bot identity alone does not switch every request into Markdown.

Next step

Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.

Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.