Umay AI Markdown

No. For normal visitors the plugin only checks the Accept header and adds two small hints (a <link> tag and a Link header). Markdown is generated only when an agent asks for it, and then cached.

No. It makes no external requests, sends no analytics and loads no remote assets. All conversion happens on your server with the bundled league/html-to-markdown library.

Markdown responses are never stored by page caches: the plugin defines DONOTCACHEPAGE, tells LiteSpeed Cache not to cache the response and sends no-store headers, so browsers never receive Markdown from a cache. The .md URLs and /llms.txt always work, because they are separate addresses. Content negotiation on the same URL (the Accept header) also requires the cache to tell agents and browsers apart. HTML responses carry Vary: Accept, which caches such as Varnish, nginx and browsers honor. A full-page cache that ignores Vary may hand its cached HTML to an agent that asked for Markdown; the agent still gets correct content, and it can use the advertised .md URL. To negotiate on the same URL behind such a cache, configure it to bypass (or vary on) requests whose Accept header contains text/markdown, for example with a Cloudflare Cache Rule.

If a physical llms.txt file exists in your site root (Yoast SEO's llms.txt feature writes one), the web server serves that file and this plugin's version is not used. To use this plugin's version, turn off the llms.txt feature of the SEO plugin and delete the file. To keep the SEO plugin's file, you can disable ours with add_filter( 'umay_mdn_llms_txt', '__return_false' );.

No duplicate content is created. Negotiated Markdown is served on the page's own URL and carries a Link: rel="canonical" header. The .md URLs additionally send X-Robots-Tag: noindex and point to the HTML page as canonical.

No. Password-protected posts are never served as Markdown, not even to visitors who entered the password, and private, draft, scheduled and trashed content is never served to visitors. Negotiated Markdown is only generated for visitors who are not logged in; logged-in users can preview .md URLs of content they are allowed to see, and those responses are never cached. Responses for visitors carrying cookies (other than common analytics and CDN cookies) are never cached either, so content a membership plugin unlocks by cookie stays with that visitor. llms.txt summaries come only from manual excerpts, so text of restricted posts is not quoted there; posts hidden by your own access rules can be left out with the umay_mdn_llms_include filter.

Yes. Markdown is produced at the very end of WordPress's request handling: plugins that redirect (login walls), set an error status such as 503 (maintenance) or switch to their own template (coming-soon pages) apply first, and the agent receives what a visitor would see.

Add a filter, for example in a small plugin or your theme's functions.php: add_filter( 'umay_mdn_content_signal', function () { return 'search=yes, ai-input=yes, ai-train=no'; } ); The value is sent as a Content-Signal header with every Markdown response and added under User-agent: * in the robots.txt that WordPress generates. A physical robots.txt file is not changed.

Automatically: the affected URLs (post, home page, archives, author and term pages, llms.txt) when a post changes; everything after a theme switch, a menu or term edit, a plugin/theme/core update, or deactivation. To clear it manually run do_action( 'umay_mdn_flush' );, for example with WP-CLI: wp eval 'do_action( "umay_mdn_flush" );'.