Temso AI

<p>Temso captures every request your WordPress origin serves over HTTP and sends it to Temso in the background. No DNS changes, no extra infrastructure — install, paste two values, done.</p>
<ul>
<li>Captures all server-side requests — front-end, wp-admin, REST, AJAX, login, xmlrpc. Bot classification happens in Temso.</li>
<li>Non-blocking, batched delivery — adds no perceptible latency to your pages.</li>
<li>No cookies, no JavaScript, no client-side tracking.</li>
<li>Visitor IPs are sent over TLS and hashed in Temso before storage; raw IPs are never retained.</li>
<li>WordPress Multisite supported (activate and connect per site).</li>
</ul>
<p>Learn more at <a href="https://temso.ai/" rel="nofollow ugc">temso.ai</a>.</p>
<p>Requests served from full-page cache never reach PHP and therefore can’t be captured by any origin plugin — this is expected and matches the documented CDN-cache limitation.</p>
<h3>Privacy</h3>
<p>This plugin sends the following per HTTP request that WordPress serves (front-end, wp-admin, REST, AJAX, login, xmlrpc) to the Temso API endpoint you configure: timestamp, request URL, HTTP method, response status, user agent, referer, and the visitor IP address. The IP address is transmitted over TLS and hashed by Temso before storage — it is never stored in raw form, and the plugin sets no cookies and adds no client-side tracking.</p>


Stream front-end request logs from your WordPress origin to Temso so AI-crawler and bot traffic shows up in your dashboard.

Azey

<p>AI agents from ChatGPT, Claude, Perplexity, and others read your content to generate answers — but they parse through HTML, JavaScript, and navigation just to reach it. Serve Markdown gives them a direct path: clean Markdown with structured metadata. When a crawler requests it — via an <code>Accept: text/markdown</code> header or a <code>.md</code> URL — your site responds instantly. No noise, no guesswork.</p>
<h4>How It Works</h4>
<p>Serve Markdown adds three capabilities to your WordPress site:</p>
<p><strong>1. Content Negotiation</strong><br />
When an AI crawler sends <code>Accept: text/markdown</code>, your site returns Markdown instead of HTML — no URL changes needed.</p>
<p><strong>2. .md URL Suffix</strong><br />
Append <code>.md</code> to any post or page URL (e.g. <code>example.com/my-article.md</code>) to get the Markdown version directly.</p>
<p><strong>3. Markdown Auto-Discovery</strong><br />
Every page includes a <code><link rel="alternate" type="text/markdown"></code> tag in the HTML head so crawlers can find your Markdown automatically.</p>
<h4>What the Markdown Output Looks Like</h4>
<p>Every Markdown response includes YAML frontmatter with structured metadata followed by your post content. Here is a real example:</p>
<pre>
---
url: 'https://akumarjain.com/textexpander-year-in-review-2025/'
title: TextExpander Year in Review 2025
author:
  name: Ajay
  url: 'https://akumarjain.com/author/akumarjain/'
date: '2026-01-05T09:05:00+05:30'
modified: '2026-01-10T14:30:06+05:30'
type: post
categories:
  - 2025
  - Year in Review
tags:
  - '#ToolsIUse'
  - Productivity
  - Remote Work
image: 'https://akumarjain.com/wp-content/uploads/text-expander-year-in-review-2025.webp'
published: true
---

# TextExpander Year in Review 2025

In my daily work, I need to type the same words and phrases repeatedly...
</pre>
<h4>Features</h4>
<p><strong>Content Serving</strong></p>
<ul>
<li>Content negotiation via <code>Accept: text/markdown</code> header</li>
<li><code>.md</code> URL suffix on any post or page</li>
<li>Auto-discovery <code><link rel="alternate"></code> tag in page head</li>
<li>Each feature can be toggled independently</li>
<li>Choose which post types are exposed (posts, pages, custom post types)</li>
</ul>
<p><strong>Frontmatter and Metadata</strong></p>
<ul>
<li>YAML frontmatter with title, author, date, categories, tags, featured image, and more</li>
<li>Toggle individual metadata fields on or off</li>
<li>Add custom static key-value pairs (e.g., <code>license</code>, <code>language</code>)</li>
<li>Map WordPress custom fields (post meta) into the frontmatter</li>
</ul>
<p><strong>Access Control</strong></p>
<ul>
<li>Per-post opt-out via a sidebar checkbox in the editor</li>
<li>Exclude entire categories from Markdown serving</li>
<li>Exclude entire tags from Markdown serving</li>
<li>Only published posts are served — drafts and private posts are never exposed</li>
</ul>
<p><strong>Crawler Insights</strong></p>
<ul>
<li>Request log showing every Markdown request with timestamp, URL, bot name, and method</li>
<li>Automatic bot detection: ClaudeBot, GPTBot, ChatGPT, OAI-SearchBot, PerplexityBot, Googlebot, Bingbot, Cohere, Meta AI, Bytespider, Applebot, and more</li>
<li>Stats dashboard: total requests, requests today, unique bots</li>
<li>Filter log by individual bot</li>
<li>Configurable retention period with automatic pruning</li>
<li>One-click log clearing</li>
</ul>
<p><strong>Editor Integration</strong></p>
<ul>
<li>“Preview Markdown” button in the post editor sidebar</li>
<li>“View Markdown” link in the Posts and Pages list table</li>
<li>Meta box shows on all enabled post types</li>
</ul>
<h4>Performance</h4>
<p>Markdown conversion only runs when specifically requested — regular visitors see the same HTML pages they always have. The crawler log uses a lightweight custom table with three safeguards against unbounded growth: time-based retention, a row count cap, and a table size cap.</p>
<h4>Privacy</h4>
<p>The crawler log stores IP addresses and user-agent strings from Markdown requests. This data stays in your WordPress database and is never sent to external services. You can disable logging entirely, configure a retention period, or clear the log at any time from the settings page.</p>


Serve Markdown

Serve Markdown versions of your posts and pages to AI agents and crawlers. Content negotiation, .md URLs, auto-discovery, and crawler logging.

Temso AI vs Serve Markdown