by
chancerylaneproject
0 (0 reviews)
Markdown for Agents and Statistics
Serve pre-generated Markdown files to AI agents via HTTP content negotiation.
Markdown for Agents and Statistics ranks #12,604 among WordPress.org plugins with 200+ active installations, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.7.3
Current Version v1.7.3
Updated 1 week ago
Last Update on 29 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Top 25% by installs
Downloads +13.9% this week
Actively maintained
Rank
#12,604
—
No change
Active Installs
200+
+100%
KW Avg Position
20
0.7 worse
Downloads
4K
+12 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 300
200+
300+
1,618
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 74 more installs to reach 300+
Rank Changes
Current
#12,604
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%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
0
Resolved
1
Unresolved
0%
Resolution Rate
Security History
Source: WPVulnerabilityNo known vulnerabilities on record for Markdown for Agents and Statistics. Checked 3 months ago.
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.7.3
- Last Updated
- Oct 29, 2026
- Requires WP
- 6.3+
- Tested Up To
- 7.1.4
- PHP Version
- 8.1 or higher
- Author
- chancerylaneproject
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 1
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners who want their content accessible to AI agents and language model tools. It solves the problem of serving content in a format LLMs can consume by pre-generating Markdown versions of posts and taxonomy pages and delivering them via HTTP content negotiation.
- HTTP content negotiation for Markdown
- Taxonomy archive support
- Automatic Markdown generation on save
- AJAX bulk generation with progress counter
- Per-post-type field configuration
- ACF support with dot notation
- llms.txt index generation
- Access statistics with admin page
Frequently Asked Questions
Common questions about Markdown for Agents and Statistics
Inside wp-content/uploads/{export_dir}/ (configurable in Settings). Post files live under {export_dir}/{post-type}/{slug}.md. Taxonomy archive files live under {export_dir}/taxonomy/{taxonomy}/{term-slug}.md. Negotiated page requests are served through WordPress. Direct uploads URLs are normally served by the web server and bypass the plugin headers and counters.
No. Markdown files are generated ahead of time (on post save or via manual/CLI bulk generation). Serving them is a simple file read, much faster than rendering a full WordPress page.
Bulk generation (the "Generate everything" and per-post-type/taxonomy buttons) runs in the background via WP-Cron, so WP-Cron needs to be working on the site. If you have set DISABLE_WP_CRON and use a system cron to call wp-cron.php instead, that cron must run as the same user as your web server, or the files it writes will fail permission checks. If WP-Cron is not working, a run sits at "running" with little or no progress instead of failing outright — there is no page load to trigger the next batch. Two things to check: whether DISABLE_WP_CRON is set with no system cron actually running behind it, and whether a firewall or HTTP auth on the site is blocking the loopback request WordPress makes to its own wp-cron.php.
There is no cancel button, but deactivating the plugin (Plugins screen, no CLI needed) stops a run immediately: it clears the job and unschedules its background events. Reactivating leaves already-generated files untouched, and you can start a new run from Settings. Note this is blunt — deactivating also stops the plugin serving Markdown to agents until you reactivate it.
First confirm the post is public, eligible, and has a current export. Missing files or excluded posts legitimately fall back to HTML. Otherwise inspect each CDN, firewall and page cache: it may answer before WordPress runs, return cached HTML or block the request. A UA-only request can receive warm cached HTML even
The advertised ?output_format=md alternate is the preferred route when every cache preserves that query parameter or explicitly bypasses it. It is not a firewall bypass, and caches configured to ignore query strings can still answer with the HTML entry. Direct upload URLs have separate static-cache behaviour.
Configure every cache layer, including any hosting-provider cache behind a CDN. Bypass requests containing a Markdown Accept header, the output_format query parameter, or a configured AI User-Agent where that layer supports the match.
Keep origin cache-control respected, and permit intended agents through security controls separately from cache rules. For LiteSpeed Cache, under Cache → Excludes, add the export directory (default /wp-content/uploads/wp-mfa-exports/) to Do Not Cache URIs, output_format to
User Agents, one per line. The Accept route additionally needs the README's rewrite rule. Regenerate UA exclusions whenever the configured list changes. The CDN and cache guide includes the worked configuration, other cache vendors, static-export caveats and both-order verification. Negotiated Markdown's private/no-store headers prevent storage only when the cache honours them; a forced TTL can defeat them.
If using cache-everything, choose an Edge TTL that respects origin cache-control. Put a Bypass cache rule for the Markdown query or configured UA after it: for conflicting cache settings the last matching rule wins. Generate the UA expression from this installation's saved options, not a stale copied list. Review bot/security policies and which layer manages robots.txt independently. A controlled free-plan test on 21 September 2026 rejected an Accept-header Cache Rule. Listed UA and query bypass worked; an unlisted client asking only through Accept still received warm cached HTML. This was a related Wagtail deployment, not verification of your WordPress host. Check current plan capabilities and use the guide's procedure against your actual stack.