by
Fabio Balossi
0 (0 reviews)
System Markdown Alternate
Exposes a clean Markdown version of your posts (readable by LLMs, agents and technical tools) by appending .md to the permalink.
System Markdown Alternate ranks #72,019 among WordPress.org plugins with 0+ active installations, and was last updated Sep 14, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v0.53.1
Current Version v0.53.1
Updated 1 month ago
Last Update on 14 Sep, 2026
Refreshed 1 week ago
Last Refreshed on
Downloads -20.1% this week
Rank
#72,019
—
No change
Active Installs
0+
-100%
KW Avg Position
34
1 worse
Downloads
1.8K
+6 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
44,451
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#72,019
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.53.1
- Last Updated
- Sep 14, 2026
- Requires WP
- 6.1+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Fabio Balossi
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about System Markdown Alternate
By default no post type is enabled. Open Settings → Markdown Alternate and tick at least one post type under Supported post types.
Anything the endpoint would not be able to serve honestly: content types not enabled in the settings page; drafts, pending and private content, and password-protected posts; media attachments (always excluded); posts with a non-standard post format — aside, status, quote, link, gallery, image, video, audio, chat. These are short snippets, usually untitled, with no editorial body worth serving as a document. Use the sysmda_markdown_excluded_post_formats filter to change that; posts rendered by an unsupported page builder — Elementor, Divi, WPBakery, Oxygen, Beaver Builder or Breakdance. Their content is stored outside post_content, or stored in it as the builder's own layout shortcodes, so the Markdown would come out either empty or full of layout wrappers converted as prose. A 404 is the honest answer; use the sysmda_markdown_unsupported_builders filter if you would rather have the empty document. Bricks pages are supported and get a real .md, rendered through Bricks' own API — see the next question; WooCommerce's cart, checkout and my-account pages. They are ordinary published pages, but their body without a shopping session is WooCommerce's own placeholder text, not anything written for a reader. The shop page is unaffected — that one is real content. Use the sysmda_markdown_excluded_woocommerce_pages filter to change that. That last rule is decided per post, from the builder's own render mode. Activating a builder does not affect posts you did not build with it, and a post you switched back to the WordPress editor keeps its Markdown version even though the builder data is still stored. Nothing is read from the post content, so an article quoting [et_pb_section] in a code sample is not mistaken for a Divi page.
The .md is built by calling Bricks' own \Bricks\Frontend::render_data() on the page's stored element tree — the plugin never re-implements Bricks' elements. The existing md-exclude CSS class already works on any Bricks element (set it in the element's CSS Classes field); a new Excluded builder elements list under Settings → Markdown Alternate → Markdown output additionally strips Bricks chrome by default — forms, nav menus, share bars, tables of contents, breadcrumbs — the same way excluded CSS classes are stripped, and it only adds to that list, never replaces it. A page switched to Render with WordPress is served from post_content as usual, whether or not Bricks data is still stored on it. Markdown is also never served for URL variants of a post — its feed, its oEmbed view, its trackback endpoint, paged comments and the sub-pages of a post split with <!--nextpage--> — even with Accept: text/markdown. Only the canonical permalink and its .md URL return Markdown.
Each .md response is a UTF-8 document with a YAML front-matter block (title, URL, Markdown URL, published/modified dates, and — when available — author, featured image, categories, tags and a description), followed by the # Title heading and the post body converted to clean Markdown. The exact keys, their order and the escaping rules are documented as a stable contract, with conformance tests, in the Markdown output format reference.
Yes. Open Settings → Markdown Alternate → Markdown output and tick the ones you want under Custom taxonomies: the front matter then carries a taxonomies: block with their terms, sorted alphabetically. Categories and tags already have their own keys and are not repeated. Nothing is selected by default and nothing is ever added implicitly — a taxonomy registered by a plugin you install later shows up in the list unticked, so it cannot start publishing itself. Taxonomies used for editorial classification only, with no public term archive ("publicly queryable" off), are labelled as internal in the list: they are still selectable, but only on purpose. Developers can curate the list further with the sysmda_front_matter_taxonomy_slugs filter.
Add one of the CSS classes no-md, md-exclude or exclude-from-markdown to a block; the element (and its children) is removed from the Markdown output. You can customize the list with the sysmda_markdown_excluded_classes filter.
The .md responses are sent with X-Robots-Tag: noindex, follow and a Link: rel="canonical" header pointing back to the HTML version, so search engines are told to prefer the original page.
Use the [sysmda_md_url] shortcode. If you run GenerateBlocks 2.x, the {{sysmda_md_url}} Dynamic Tag is available automatically — use it in element fields such as a Button URL. When the post has no .md, the tag resolves to an empty value so GenerateBlocks can hide the element instead of leaving a broken link.
Use [sysmda_md_actions]. It renders a GitHub-style split button: the main action copies the complete Markdown document, while the dropdown offers Copy as Markdown, View as Markdown in a new tab and Download Markdown. Use [sysmda_md_actions id="123"] for a specific post. The component renders only where the shortcode is placed. Its small stylesheet and dependency-free script are loaded only on pages that actually render it, including placements in templates, widgets and secondary loops. The menu opens aligned to the button and drops below it, moving to the opposite side or above only when the screen edge leaves no room. Like the other shortcodes, it outputs nothing when the target post has no Markdown version.
Use the [sysmda_md_download] shortcode. It prints a link that saves the file: [sysmda_md_download] [sysmda_md_download text="Save the Markdown"] [sysmda_md_download id="123"] The link carries the HTML download attribute, which is what tells the browser to save the file instead of displaying it. The file name comes from the post slug. Nothing changes on the server side: the .md URL itself behaves exactly as it always has, so opening it directly still shows whatever your browser normally does with a Markdown file. The shortcode outputs a plain link with a single sysmda-md-download class, and the plugin loads no CSS and no JavaScript on your site for it. Any styling is your theme's job. Like [sysmda_md_url], it outputs nothing when the post has no Markdown version, so it can never produce a link to a 404.