onevteam

vslnk

<p><strong>One-V LLM Serve</strong> makes every public page on your WordPress site available as clean Markdown at the same URL with a <code>.md</code> extension — zero configuration required.</p>
<pre><code>https://example.com/about/      <span aria-hidden="true" class="wp-exclude-emoji">←</span> HTML page for humans
https://example.com/about.md    <span aria-hidden="true" class="wp-exclude-emoji">←</span> clean Markdown for AI
</code></pre>
<p>AI systems — ChatGPT, Perplexity, ClaudeBot, Google AI Overviews, and most RAG pipelines — parse Markdown far more efficiently than HTML. When these systems encounter an HTML page, they must strip navigation, headers, footers, sidebars, scripts, and tracking pixels before they can read the actual content. This noise introduces errors, increases token cost, and leads to lower-quality outputs.</p>
<p>The Markdown file contains a configurable YAML frontmatter block followed by the page title, headings in correct hierarchy, and the body text. Nothing else.</p>
<h4>Core features</h4>
<ul>
<li><strong>Zero-config Markdown endpoint</strong> for every public post, page, and custom post type</li>
<li><strong>YAML frontmatter</strong> with configurable fields (<code>title</code>, <code>date</code>, <code>modified</code>, <code>url</code>, <code>description</code>, <code>image</code>, <code>tags</code>, <code>categories</code>, <code>lang</code>, <code>type</code>)</li>
<li><strong><code>/llms.txt</code> discovery file</strong> at the site root following the <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a> convention</li>
<li><strong>Taxonomy archives</strong> as Markdown — <code>/category/news.md</code>, <code>/tag/foo.md</code>, custom taxonomies</li>
<li><strong><code>?format=markdown</code> query parameter</strong> as an alternative to the <code>.md</code> URL on any singular page</li>
<li><strong>Per-post exclude</strong> via a sidebar checkbox on the post editor</li>
<li><strong>Works with Classic Editor and Gutenberg</strong> via the <code>the_content</code> filter</li>
<li><strong>ACF integration</strong> — opt-in per-post: pick which text, textarea, WYSIWYG, URL, email, or link fields to append below the body</li>
<li><strong>Filterable AI analytics</strong> — per-hit events with full denormalised dimensions (UA bucket, referrer host, language, post type, response code), sticky filter bar that drives every chart and table live, six KPI tiles, a stacked-area time chart, three composition donuts (UA bucket / referrer source / language), four Top tables, a User-Agent classifier transparency table, and a Recent Activity stream. Referrers are tracked by <strong>hostname only</strong> — paths and query strings are stripped before storage so no PII is retained. Forward-compatible classification: when the bot or referrer catalogue is updated in a future release, historical rows are reclassified automatically — no Reset Analytics required.</li>
<li><strong>Browser-bucket sub-classification</strong> — anything that <em>looks</em> like a browser visit gets split into four kinds based on the <code>Sec-Fetch-Site</code>, <code>Sec-Fetch-User</code>, and <code>Sec-CH-UA</code> request headers a real browser sends: <strong>verified user</strong> (top-level navigation triggered by a click or address-bar Enter in a recognised browser), <strong>headed agent</strong> (real Chromium driven programmatically — Playwright, Puppeteer, Selenium), <strong>script agent</strong> (bare HTTP client imitating a browser UA — <code>requests</code>, <code>httpx</code>, LangChain, custom agents), <strong>spoofer</strong> (UA shape that no real browser would emit, like modern Chrome with a non-reduced UA). Visible as a stacked-bar breakdown on the User-Agents subpage so you can see at a glance how much of your “human” traffic is actually automation, and rendered inline as colour-coded slugs on every browser-bucket row in the Recent Activity table on the Analytics page. Detection is server-side fingerprinting of the request itself — no cookies, no JS, no IP.</li>
</ul>
<h4>Discoverability</h4>
<ul>
<li><strong><code>Link: rel="alternate"; type="text/markdown"</code></strong> HTTP header on every HTML page</li>
<li><strong><code><link rel="alternate"></code></strong> tag in <code><head></code> for HTML-based discovery</li>
<li><strong><code>Allow: /*.md$</code></strong> directive in <code>robots.txt</code></li>
<li><strong>CORS <code>Access-Control-Allow-Origin: *</code></strong> on <code>.md</code> and <code>/llms.txt</code> so browser-based AI clients can fetch them</li>
</ul>
<h4>Operations</h4>
<ul>
<li><strong>Transient caching</strong> with automatic invalidation on <code>save_post</code>, on ACF field value saves, on any ACF field group change, and on plugin settings save</li>
<li><strong>“Clear cache” button</strong> in the settings page</li>
<li><strong>Admin notice</strong> on fallback HTTP fetch failures</li>
<li><strong>“Settings” link</strong> next to the plugin row in Plugins screen</li>
<li><strong>“View .md” row action</strong> in the Posts and Pages list tables</li>
</ul>
<h4>Developer hooks</h4>
<ul>
<li><strong><code>ovls_markdown</code></strong> filter for the final Markdown output</li>
<li><strong><code>ovls_frontmatter</code></strong> filter for adding, removing, or modifying frontmatter fields</li>
<li><strong><code>ovls_content_queries</code></strong> filter for the HTML extraction XPath cascade</li>
</ul>
<h4>How it works</h4>
<p>Each request to <code>/about.md</code> is captured by a WordPress rewrite rule and routed through the plugin’s content generator. The generator runs the post through <code>apply_filters( 'the_content', ... )</code> — the same pipeline WordPress uses on the front end — so Classic Editor, Gutenberg, and shortcodes all work without separate code paths. The rendered HTML is converted to Markdown via <code>league/html-to-markdown</code>, then cached in a WordPress transient.</p>
<p>The cache is invalidated automatically on <code>save_post</code>, on ACF field/group changes, and whenever plugin settings are saved. A manual <strong>Clear cache</strong> button is also available on the settings page.</p>
<h4>Access methods</h4>
<p>There are three equivalent ways to request the Markdown version of a page:</p>
<ul>
<li><code>.md</code> extension — <code>https://example.com/about.md</code></li>
<li><code>?format=markdown</code> query — <code>https://example.com/about/?format=markdown</code></li>
<li><code>Link: rel="alternate"</code> header — returned by every HTML page</li>
</ul>
<p>The <code>.md</code> URL is the recommended canonical form.</p>
<h4>ACF integration</h4>
<p>When <a href="https://www.advancedcustomfields.com/" rel="nofollow ugc">Advanced Custom Fields</a> is active, ACF field rendering is opt-in at two levels:</p>
<ol>
<li><strong>Site defaults per post type</strong> — at <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> One-V LLM Serve <span aria-hidden="true" class="wp-exclude-emoji">→</span> ACF Defaults</strong>, tick fields that should be appended to every post of a given post type.</li>
<li><strong>Per-post override</strong> — the <strong>One-V LLM Serve</strong> metabox on each post editor lists every supported ACF field applicable to that post. Tick fields to replace the site defaults for that one post.</li>
</ol>
<p>Supported ACF types: <code>text</code>, <code>textarea</code>, <code>wysiwyg</code>, <code>url</code>, <code>email</code>, <code>link</code>. Each selected field is rendered under a <code>## Field Label</code> heading. Empty fields are skipped.</p>
<h3>Disclaimer</h3>
<p>This plugin is provided “as is”, without warranty of any kind, express or implied, in accordance with the GNU General Public License v2 or later. The authors and contributors are not liable for any direct, indirect, incidental, special, or consequential damages — including but not limited to data loss, lost profits, business interruption, search-ranking changes, or third-party claims — arising from the use of, or inability to use, this software, even if advised of the possibility of such damages.</p>
<p>By installing and activating the plugin you acknowledge that:</p>
<ul>
<li>You are responsible for testing the plugin in a staging environment before deploying to production.</li>
<li>You are responsible for the content this plugin exposes as Markdown — <code>.md</code> URLs and <code>/llms.txt</code> serve the same content as their HTML counterparts and are intended to be crawled and consumed by AI systems and third-party LLMs.</li>
<li>The plugin does not transmit data to any external service. All Markdown generation, caching, and file writes happen on your own server.</li>
</ul>
<p>Nothing in this disclaimer is intended to exclude or limit liability for matters that cannot lawfully be excluded under the consumer-protection laws of your jurisdiction. For the full legal terms see the GPLv2 license at <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">https://www.gnu.org/licenses/gpl-2.0.html</a>.</p>


One-V LLM Serve

Serve clean Markdown versions of every public page at the same URL with a .md extension for AI crawlers, LLMs, and GEO optimization.

Whizz People

<p><strong>Whizz MD</strong> automatically creates a <code>.md</code> version of every published post and page on your WordPress site, served dynamically without storing any files on disk.</p>
<p>AI-powered search engines and LLM crawlers (GPTBot, ClaudeBot, PerplexityBot, Googlebot) increasingly prefer clean, structured content. This plugin gives them exactly that — a Markdown file with rich YAML frontmatter containing all your SEO signals, served at a predictable URL like <code>/your-post-slug.md</code>.</p>
<h4>How It Works</h4>
<ol>
<li>Any published post or page automatically gets a <code>.md</code> endpoint</li>
<li>AI crawlers discover it via a <code><link rel="alternate"></code> tag in your page <code><head></code>, a dedicated <code>/md-sitemap.xml</code>, and crawlable anchor links in your page content</li>
<li>The Markdown is generated on the fly — no files written to disk, no database bloat</li>
<li>Full YAML frontmatter is included with all SEO metadata</li>
</ol>
<h4>What Gets Generated</h4>
<p><strong>YAML Frontmatter includes:</strong></p>
<ul>
<li><code>title</code> — SEO title (from Yoast, Rank Math, AIOSEO, or post title)</li>
<li><code>slug</code> — post slug</li>
<li><code>date</code> and <code>modified</code> — publication and last modified dates</li>
<li><code>author</code> — author display name</li>
<li><code>meta_description</code> — SEO meta description (from SEO plugin or auto-generated)</li>
<li><code>focus_keyword</code> — primary keyword (from Yoast/Rank Math)</li>
<li><code>canonical_url</code> — points back to your HTML page</li>
<li><code>og_title</code> and <code>og_description</code> — Open Graph fields</li>
<li><code>og_image</code> — featured image URL</li>
<li><code>schema_type</code> — auto-detected (Article, HowTo, FAQPage, WebPage)</li>
<li><code>categories</code> and <code>tags</code></li>
<li><code>reading_time</code> and <code>word_count</code></li>
<li><code>robots</code> — respects your SEO plugin’s noindex settings</li>
<li><code>lang</code> — site language (WPML/Polylang compatible)</li>
</ul>
<p><strong>Markdown Body includes:</strong></p>
<ul>
<li>H1–H6 headings with anchor ID preservation</li>
<li>Bold, italic, strikethrough, inline code</li>
<li>Fenced code blocks with language detection</li>
<li>Ordered and unordered lists (nested)</li>
<li>GitHub Flavored Markdown (GFM) tables</li>
<li>Blockquotes, images with alt text, links (relative <span aria-hidden="true" class="wp-exclude-emoji">→</span> absolute)</li>
<li>Gutenberg block HTML stripped cleanly</li>
</ul>
<h4>URL Patterns</h4>
<ul>
<li><code>/your-post-slug.md</code> — clean pretty permalink</li>
<li><code>/parent/child-page.md</code> — works with nested pages</li>
<li><code>/?p=123&format=md</code> — query string fallback</li>
</ul>
<h4>AI Crawler Discovery</h4>
<p>The plugin automatically:</p>
<ul>
<li>Adds <code><link rel="alternate" type="text/markdown"></code> to every page <code><head></code></li>
<li>Registers <code>/md-sitemap.xml</code> listing all <code>.md</code> URLs</li>
<li>Appends explicit <code>Allow: /*.md</code> rules to <code>robots.txt</code> for all major AI crawlers</li>
<li>Injects a crawlable <code><a></code> link on each page so robots can follow it naturally</li>
</ul>
<h4>SEO Plugin Compatibility</h4>
<ul>
<li>✅ Yoast SEO</li>
<li>✅ Rank Math</li>
<li>✅ All in One SEO (AIOSEO)</li>
<li>✅ WPML</li>
<li>✅ Polylang</li>
<li>✅ Gutenberg (Block Editor)</li>
<li>✅ Classic Editor</li>
</ul>
<h4>No Duplicate Content Risk</h4>
<p>The <code>.md</code> endpoint serves <code>Content-Type: text/markdown</code>, not <code>text/html</code>. An HTTP-level <code>Link: rel="canonical"</code> header points back to the original HTML page, and <code>X-Robots-Tag: noindex, follow</code> prevents Google from indexing the raw Markdown as a competing webpage — while still allowing AI crawlers to read it.</p>
<h4>Why This Matters</h4>
<p>LLMs and AI search engines crawl the web to build their knowledge. Clean, structured Markdown with rich YAML frontmatter is the ideal format for these systems to parse, index, and cite your content — giving you organic visibility in AI-powered search results, summaries, and citations.</p>


Whizz MD — Markdown Endpoints for AI Crawlers

Serve every WordPress post and page as a clean .md file with full SEO frontmatter — discoverable by AI crawlers and search engines on the fly.

One-V LLM Serve vs Whizz MD — Markdown Endpoints for AI Crawlers