AISignal Markdown Converter
AISignal Markdown Converter
Description
AISignal Markdown Converter is a lightweight WordPress plugin that exposes eligible published content as Markdown while staying close to normal WordPress routing and output behavior.
Features include:
?format=markdownsupport for singular content and the homepage.mdURL handlingAccept: text/markdownnegotiation- REST endpoints for Markdown retrieval by post ID or slug path
- rendered HTML capture, extraction, normalization, and Markdown conversion
- ACF-aware fallback extraction for content stored outside the main editor
- compatible with many builder-based pages when important content is server-rendered
- alternate Markdown discovery through a head link and
Linkresponse header - optional YAML frontmatter for Markdown documents
- post type controls and exclusion controls for Markdown availability
- optional crawler insights with bot detection, request logging, request summary charts, retention, and filtering
Privacy Policy
Crawler insights stores request metadata for detected bot traffic to successful Markdown responses. It does not store IP addresses, cookies, request bodies, or raw user-agent strings.
Installation
- Upload the plugin folder to
/wp-content/plugins/. - Activate the plugin through the WordPress Plugins screen.
- Go to
Settings > AISignal Markdown Converter. - Choose which public post types should expose Markdown.
- Optionally enable YAML frontmatter and crawler insights.
Faq
You can access Markdown through ?format=markdown, .md URLs, Accept: text/markdown, and the provided REST endpoints.
Markdown is available only for published content in the post types you enable in plugin settings. You can also exclude specific items globally by post ID or individually through the editor metabox.
Yes. The plugin includes an ACF-aware fallback extractor for eligible published content, which helps recover meaningful Markdown when important content is stored in custom fields instead of the main editor. It is not a field-by-field ACF integration layer, but it is designed to improve Markdown output on ACF-heavy sites.
Often yes. The plugin is designed to work with standard WordPress rendering, including many builder-based pages, when the important content is present in rendered HTML or the_content. Highly dynamic or JavaScript-rendered sections may be incomplete, so representative builder pages should still be tested on each site.
Yes. Eligible singular requests and the homepage expose alternate Markdown discovery through:
<link rel="alternate" type="text/markdown" ...>Link: <...>; rel="alternate"; type="text/markdown"
No. Frontmatter is optional and disabled by default.
When enabled, frontmatter includes fields such as title, URL, post type, published and modified dates, schema type, language, word count, reading time, canonical URL, featured image, and public taxonomy names. It does not include author or publisher fields.
Crawler insights logs successful Markdown requests from detected bots when the feature is enabled. The admin screen includes request summary charts, retained request totals, bot filtering, timestamps, URLs, bot names, request methods, and retention controls.
Reviews
Works as promised. Great stats!
By Simon Dickson (s1m0nd) on May 6, 2026
It just works. Posts are instantly available with .md URLs. Easy to control which posts and post types get markdown. Copes well with ACF.
I'm finding the 'Crawler Insights' especially interesting. Not only does it confirm that the plugin is doing its job, it confirms just how much of your site traffic is coming from AI bots - something which my existing statistics solution isn't yet doing.
Solid Markdown bridge for AI
By Dmitry Mayorov (iamdmitrymayorov) on May 2, 2026
Clean, well-structured plugin that exposes WordPress content as Markdown via .md URLs, query params, and REST
Changelog
1.0.4
- Current release