Agentic Markdown Bridge
Agentic Markdown Bridge gives public WordPress content a clean machine-readable Markdown representation while leaving the normal HTML experience unchanged. Its primary purpose is a per-page representation layer for WordPress content: posts, pages, and public custom post types can expose their own Ma
Agentic Markdown Bridge gives public WordPress content a clean machine-readable Markdown representation while leaving the normal HTML experience unchanged.
Its primary purpose is a per-page representation layer for WordPress content: posts, pages, and public custom post types can expose their own Markdown endpoint for AI agents, retrieval systems, developer tools, and other machine clients. llms.txt support is optional and complements that per-page layer rather than defining it.
With pretty permalinks:
https://example.com/about/
can expose:
https://example.com/about/index.md
The HTML page can advertise the representation with:
<link rel="alternate" type="text/markdown" href="https://example.com/about/index.md">
The plugin also includes optional llms.txt management, per-content controls, caching, diagnostics, multilingual-aware URLs and response language metadata, local request counters, content negotiation, and developer/CLI tools.
The plugin does not automatically send content or analytics to Bipixels or any third party and does not require an account, API key, SaaS service, or remote code. Optional AI-assisted llms.txt buttons are user-initiated outbound links to third-party AI websites.
Representation layer, not just llms.txt
The core feature is a machine-readable representation layer for individual WordPress URLs. Each eligible piece of content can have its own Markdown endpoint, discovery metadata, HTTP validation headers, content-negotiation behavior, exclusions, title rules, and per-content overrides. Optional llms.txt management acts as a site-level resource map on top of that representation layer.
Core Markdown features
- Dynamic /index.md representations with no duplicate physical Markdown files.
- Posts, pages, and selectable public custom post types.
- Per-post/page Markdown enable, disable, or inherit control.
- Smart title behavior: Auto, Always include, or Never include the WordPress title.
- Per-post title override.
- Global and per-content control to ignore visual content before the first H1; enabled by default for cleaner machine-readable documents.