Serve WordPress Posts as Markdown for LLMs and AI Search
An AI assistant, a documentation chatbot or a retrieval pipeline wants a site’s content as text. Pointing it at the public page means it downloads the theme, the navigation, the cookie banner and the footer along with the article, then has to guess which part is the article. The core REST API is closer, but content.rendered is still HTML full of block markup, classes and inline styles, which costs tokens and carries nothing an LLM can use. The llms.txt convention makes the expectation explicit: link to a Markdown version of each page. A route can produce that version from the post itself.
Why this needs a package
Section titled “Why this needs a package”Converting HTML to Markdown correctly is more than stripping tags: headings become # lines, links keep their target, lists keep their nesting, <pre><code> becomes a fenced block, and everything Markdown has no equivalent for has to be dropped without losing its text. league/html-to-markdown does exactly that conversion, on top of PHP’s own DOM parser.
The route
Section titled “The route”<?php
declare(strict_types=1);
use League\HTMLToMarkdown\HtmlConverter;use Loopress\Api\Attribute\Permission;
#[Permission(public: true)]class PostMarkdown{ public function get(WP_REST_Request $request): WP_Error|null { $post = get_post((int) $request->get_param('post_id'));
if ( $post === null || $post->post_status !== 'publish' || !is_post_type_viewable($post->post_type) || post_password_required($post) ) { return new WP_Error('not_found', 'No published post with that id.', ['status' => 404]); }
$html = apply_filters('the_content', $post->post_content);
$converter = new HtmlConverter([ 'strip_tags' => true, 'header_style' => 'atx', ]);
// Raw Markdown, not JSON: set the header, send the body, stop. header('Content-Type: text/markdown; charset=utf-8'); echo '# ' . get_the_title($post) . "\n\n" . $converter->convert($html) . "\n"; exit; }}{ "require": { "league/html-to-markdown": "^5.1" }}lps composer pushlps api pushapply_filters('the_content', ...) renders the post exactly as the theme would, blocks, shortcodes and embeds included, so the Markdown matches what a visitor actually reads, not the raw block comments stored in the database. strip_tags drops the markup Markdown can’t express (a <figure> wrapper, a <div>) but keeps its text, and header_style: atx writes ## Heading instead of the underlined style, which is what most LLM tooling expects.
Now call it
Section titled “Now call it”curl https://your-site.com/wp-json/loopress-api/v1/markdown/489# Shipping notes
## Why
Read the [docs](https://loopress.dev), *then* ship.
- Git- CI
```lps api push```That’s a real Gutenberg post (heading, paragraph, list and code blocks), converted. A draft, a private post, a password-protected one or an id that does not exist answers 404 with {"code":"not_found","message":"No published post with that id."} instead, as JSON.
Permission
Section titled “Permission”The route is public on purpose: an AI crawler or an assistant fetching a page has no WordPress account. It only ever returns what’s already public, published posts of a publicly viewable post type, without a password, the same text the site shows any visitor. The post_status, is_post_type_viewable() and post_password_required() checks are what make that true, don’t remove them to “also support drafts”: a draft served here would be readable by anyone who guesses its id. For drafts, see signed draft previews.
A missing package is scoped to this route
Section titled “A missing package is scoped to this route”Without league/html-to-markdown installed, HtmlConverter is an undefined class, a PHP Error thrown inside get(). Loopress catches it, logs a Loopress api/: line and answers that request with a 500, the other routes keep working. Install the package through Composer dependency management before pushing this route.
What this opens up
Section titled “What this opens up”The llms.txt convention expects two things: a /llms.txt file at the site root listing the pages worth reading, and a Markdown version of each page, usually at the page’s own URL with .md appended. This recipe covers the second half, at /wp-json/loopress-api/v1/markdown/<id>, which you link from llms.txt rather than serving at the .md URL. A plain /llms.txt at the root and .md URLs next to each permalink need a rewrite rule, which a Custom API Route does not provide. If you want the index, add a second route, api/llms.php, that lists published posts with their title and Markdown URL, and link it from your llms.txt. The recipe stays on one route because the conversion is the part that needs a package.
With one Markdown URL per post, that index is a second small route listing them. The same conversion feeds a RAG pipeline’s ingestion step, a newsletter tool that wants Markdown, or a migration away from WordPress entirely. It’s the reverse of rendering Markdown with CommonMark, which turns Markdown written elsewhere into HTML for WordPress.
Related docs
Section titled “Related docs”Custom API Routes and Composer dependency management ship with Loopress Full, a free WordPress plugin and CLI for managing custom code and dependencies as version-controlled files instead of pasting into wp-admin.
Getting Started walks through connecting it to your site in under a minute. Writing Route Files covers the complete file reference.