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.

Paradoks Yazılım

<p>Paradoks Markdown for AI helps WordPress sites publish cleaner, lighter content to AI crawlers and retrieval systems without changing the public HTML experience for human visitors.</p>
<p>The plugin converts your rendered WordPress content to markdown, adds YAML frontmatter, caches the result, and serves it through multiple delivery channels that fit modern AI tooling.</p>
<h4>Core delivery features</h4>
<ul>
<li>Serve markdown when a client sends <code>Accept: text/markdown</code></li>
<li>Publish clean markdown URLs such as <code>/my-post.md</code></li>
<li>Generate <code>llms.txt</code> and optional <code>llms-full.txt</code></li>
<li>Add REST API <code>markdown</code> fields to enabled post types</li>
</ul>
<h4>Content and conversion features</h4>
<ul>
<li>YAML frontmatter with title, URL, dates, author, excerpt, taxonomies, image, and language</li>
<li>Optional Gutenberg-aware rendering for quotes, code blocks, galleries, and tables</li>
<li>Relative URL rewriting for links and images</li>
<li>Per-post controls for disabling markdown or overriding frontmatter</li>
<li>Skips very short posts (under 15 words) so empty stubs are not exposed as markdown</li>
<li>Lets you choose important pages for <code>llms.txt</code> automatically or with a custom page picker</li>
</ul>
<h4>WooCommerce support</h4>
<ul>
<li>Detects products automatically and emits a dedicated <code>woocommerce</code> frontmatter block</li>
<li>Includes price, regular and sale price with currency, SKU, stock status and quantity</li>
<li>Adds weight, dimensions, attributes, and gallery image URLs when available</li>
<li>Toggle product categories and product tags from the Content tab when products are enabled</li>
<li>Excludes WooCommerce cart, checkout, account, and shop pages from <code>llms.txt</code> discovery output</li>
</ul>
<h4>Performance and admin features</h4>
<ul>
<li>Post meta cache for generated markdown</li>
<li>Save-time invalidation and optional scheduled cache warming</li>
<li>Top-level admin menu with General, Content, Performance, and Advanced sections</li>
<li>Inline confirmation when settings are saved</li>
<li>Markdown preview tools in the editor and admin bar</li>
</ul>


Paradoks Markdown for AI

Serve markdown versions of WordPress posts and pages to AI agents through Accept headers, clean .md URLs, and discovery files such as llms.txt.

One-V LLM Serve vs Paradoks Markdown for AI