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.

llmaffiliate01

<p><strong>LLMAffiliate AI Traffic Monetizer</strong> is a WordPress plugin that detects Large Language Model (LLM) traffic and dynamically serves enhanced content while ensuring compliance with search engine parity requirements.</p>
<p>It mirrors the behavior of an interception layer (e.g., Cloudflare Worker) directly inside WordPress, enabling controlled content delivery for AI crawlers and agents.</p>
<h4>CORE FEATURES</h4>
<ul>
<li>Detects major LLM user agents including ChatGPT, Claude, Gemini, Copilot, Perplexity, Pi, LLaMA, Grok, Cohere, Mistral, Anthropic, and OpenAI.</li>
<li>Ensures Googlebot and search engine crawlers always receive original content (configurable parity enforcement).</li>
<li>Serves enhanced HTML responses via a remote content service.</li>
<li>Automatically falls back to native WordPress rendering if the external service fails.</li>
<li>Adds cache-control, licensing, and optional Text and Data Mining headers.</li>
<li>Supports secure QA overrides using HMAC-signed query parameters.</li>
</ul>
<h4>HOW IT WORKS</h4>
<p>The plugin intercepts incoming HTTP requests and:</p>
<ol>
<li>Identifies whether the request originates from an LLM or standard browser.</li>
<li>If LLM traffic is detected:
<ul>
<li>Fetches enhanced content from a configured external service.</li>
<li>Applies headers and response transformations.</li>
</ul>
</li>
<li>If the service fails:
<ul>
<li>Falls back to WordPress rendering safely.</li>
</ul>
</li>
<li>Ensures search engines always receive unmodified content.</li>
</ol>
<h4>USE CASES</h4>
<ul>
<li>AI traffic handling and request analysis</li>
<li>Controlled content delivery for LLM vs. human visitors</li>
<li>Response parity handling (search engines receive origin content)</li>
<li>Experimentation with LLM-specific rendering in compliant deployments</li>
</ul>
<h4>OPERATIONAL LOGGING & PRIVACY</h4>
<p>An in-plugin setting (<strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> LLMAffiliate AI Traffic <span aria-hidden="true" class="wp-exclude-emoji">→</span> Advanced Detection Settings</strong>) allows you to disable request and suspicious-event logging. When disabled, no logs are stored. When enabled (default), the plugin may store operational or security logs. These may include:<br />
* IP address<br />
* User agent<br />
* Requested URL<br />
* Referer<br />
* Selected HTTP headers<br />
* Detection and decision metadata<br />
* Suspicious-event or request logs</p>
<p>This logging is used for debugging, security analysis, and request classification. Data is stored within your WordPress database. Configure and retain logs in accordance with your privacy policy and applicable regulations.</p>
<h4>AI TERMS PAGE</h4>
<p>The plugin can serve a public <code>/ai-terms</code> page (or equivalent) that displays your site’s AI usage and content terms. It functions as a site-published policy page that visitors—including AI systems and human readers—can view. Site owners are responsible for the contents and legal suitability of the terms. The plugin includes a default template; you may customize it to match your needs.</p>
<h4>GOOGLE SEARCH CONSOLE (OPTIONAL)</h4>
<p>The <strong>LLMAffiliate</strong> service can provide a <strong>Google Search Console HTML tag verification token</strong> on <a href="https://llmaffiliate.com/" rel="nofollow ugc">llmaffiliate.com</a> for connected sites (see your dashboard or integration docs). If you choose to use it, open <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> LLMAffiliate AI Traffic</strong> in WordPress and paste the token into the prominent <strong>Use LLMAffiliate’s Search Console verification</strong> field, then save. The token is <strong>stored only in your site’s database</strong> and outputs the standard <code><meta name="google-site-verification" …></code> tag on your <strong>public</strong> frontend. You can clear the field at any time to remove the tag.</p>
<p><strong>Why this helps:</strong> With your consent, LLMAffiliate can verify the site in Search Console tied to that token, which helps the service <strong>monitor indexing coverage and page performance</strong> for your integration and support you more effectively. This is <strong>fully optional</strong>; if you leave the field empty, nothing is added to your HTML.</p>
<p>No extra HTTP request is made to Google from the plugin for this feature—the meta tag is for Google’s crawler when it visits your site.</p>
<h3>External services</h3>
<p>This plugin connects to the <strong>LLM Affiliate</strong> cloud service to detect visiting AI crawlers (ChatGPT, Perplexity, Claude, Gemini, Copilot, etc.) and return an LLM-optimized, monetizable version of the requested article. Without this external service the plugin still performs local LLM detection, search-engine parity, and renders the <code>/ai-terms</code> page, but the enhanced-content feature is not available.</p>
<p>This service is provided by <strong>LLM Affiliate</strong> (llmaffiliate.com).</p>
<p>Service endpoints used:</p>
<ol>
<li>
<p><strong>Site Onboarding</strong> — <code>POST https://api.llmaffiliate.com/api/v1/enhanced-content/onboarding/</code></p>
<ul>
<li><strong>Purpose:</strong> Registers your WordPress site with the LLM Affiliate backend so the site can receive enhanced content. Think of it as a one-time (idempotent) handshake.</li>
<li><strong>When it is sent:</strong> Only when you click <strong>Generate Token</strong> in the plugin admin screen (Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> LLMAffiliate AI Traffic). It is also re-sent if you regenerate/rotate the token. It is <strong>not</strong> sent on every page load.</li>
<li><strong>Data sent (JSON body):</strong>
<ul>
<li><code>token</code> – the authentication token generated by the plugin</li>
<li><code>site_id</code> – an internal site identifier (e.g., <code>site_xxxxxxxx</code>) generated by the plugin</li>
<li><code>host</code> – your site’s public URL (WordPress <code>home_url()</code>)</li>
</ul>
</li>
<li><strong>No post content, no user data, no visitor IP, and no visitor PII is transmitted by this endpoint.</strong></li>
</ul>
</li>
<li>
<p><strong>Enhanced Content Render</strong> — <code>GET https://api.llmaffiliate.com/api/v1/enhanced-content/render</code></p>
<ul>
<li><strong>Purpose:</strong> Fetches the LLM-optimized HTML version of a single article URL to serve back to the detected AI crawler.</li>
<li><strong>When it is sent:</strong> Only when the plugin’s LLM detector classifies an incoming request as an AI/LLM user-agent (ChatGPT, Perplexity, Claude, Gemini, Copilot, LLaMA, Grok, Cohere, Mistral, DeepSeek, Pi, and similar). It is <strong>not</strong> sent for human visitors, for search-engine crawlers (Googlebot, Bingbot), or for admin/REST/static-asset requests.</li>
<li><strong>Data sent (query string + pass-through headers):</strong>
<ul>
<li><code>url</code> – the public URL of the article being requested (query string + path)</li>
<li><code>llm_profile</code> – the detected LLM profile name (e.g., <code>chatgpt</code>, <code>claude</code>, <code>gemini</code>)</li>
<li><code>User-Agent</code> header – forwarded from the visiting LLM client</li>
<li><code>Accept-Language</code> header – forwarded from the visiting LLM client</li>
<li><code>X-LLM-Profile</code> header – the plugin’s detected profile</li>
<li><code>X-LLM-Confidence</code> header – a numeric confidence score (0–1) from the local detector</li>
</ul>
</li>
<li><strong>No cookies, session IDs, logged-in-user identifiers, or page body content are sent.</strong> Only the public URL and the minimum context needed to produce and attribute enhanced content is transmitted.</li>
</ul>
</li>
<li>
<p><strong>User sitemaps (for the plugin sitemap endpoint only)</strong> — <code>GET https://api.llmaffiliate.com/api/v1/enhanced-content/public/user-sitemaps?host=<hostname></code></p>
<ul>
<li><strong>Purpose:</strong> Returns JSON listing LLM-optimized sitemap URLs for the given site hostname so this plugin can serve <code>/sitemap.xml</code> (or the configured sitemap path) as a simple URL index for search engines.</li>
<li><strong>When it is sent:</strong> Only on GET requests that match the plugin’s dedicated sitemap path (not on normal page views). The <code>host</code> query parameter is your site’s hostname from WordPress <code>home_url()</code> (no path, no user input from forms).</li>
<li><strong>Data sent:</strong> <code>host</code> only, in the query string. Non-200 responses result in an empty <code><urlset></code> (no URLs listed).</li>
</ul>
</li>
</ol>
<p>All requests are made over HTTPS. If the service is unavailable or returns a non-200 response, the plugin adds an <code>X-LLMAFFTM-Interceptor: fallback</code> header and allows WordPress to render the normal (origin) page — humans and LLMs always receive <em>something</em>.</p>
<p>Use of the LLM Affiliate service is governed by the provider’s terms. Please review them before generating a token:</p>
<ul>
<li><strong>Terms of Service:</strong> https://llmaffiliate.com/terms</li>
<li><strong>Privacy Policy:</strong> https://llmaffiliate.com/privacy</li>
<li><strong>Service provider homepage:</strong> https://llmaffiliate.com/</li>
</ul>


LLMAffiliate AI Traffic Monetizer

Detect LLM user agents, enforce Google parity, and serve enhanced content through a configurable content service.

Whizz MD — Markdown Endpoints for AI Crawlers vs LLMAffiliate AI Traffic Monetizer