phalkmin

ParseLess serves your WordPress content as clean Markdown to AI crawlers (via User-Agent detection) and on manual <code>?format=md</code> requests. Same URL, same content, none of the theme chrome, navigation, widgets, or page-builder scaffolding that AI bots and CLI tools don’t need.
It also exposes <code>/llms.txt</code> for the emerging AI-indexing standard, so models know where to find your content.
<h4>Who is this for?</h4>
1. Developers using Claude Code, Cursor, Aider, or any CLI that feeds your own site content into an LLM.
If you’ve ever piped a blog post into Claude or ChatGPT for analysis, rewriting, or summarization, you’ve watched it burn through tokens parsing nav menus, footer markup, and CSS classes that have nothing to do with your content. A typical WordPress page measured live: ~19,800 tokens of HTML for ~975 tokens of actual content — a 20x reduction just by stripping the theme. Heavy page-builder sites (Elementor, Divi) routinely hit 100x or more.
That’s the difference between fitting a handful of pages in a context window and fitting dozens.
Just append <code>?format=md</code> to any post URL and pipe it straight into your tool of choice:
<pre><code>curl https://yoursite.com/my-post/?format=md | claude "summarize this"
</code></pre>
2. Site owners getting “high resource usage” warnings from their host because AI bots are hammering the site.
GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and a dozen others crawl WordPress sites constantly. Each request renders your full theme, runs widget queries, loads page-builder assets, and ships hundreds of KB of HTML per page — most of which the bot discards before extracting the actual text.
ParseLess intercepts these crawls and serves a tiny Markdown payload instead. You keep the AEO/SEO benefit of being indexed by AI search, without paying the server cost of rendering your full theme for every bot hit.
Typical impact on AI bot traffic (measured on real WordPress pages):
<ul>
<li>95%+ less bandwidth per crawled page (typically 15–30x smaller; e.g. a 79 KB page → 4 KB. Heavy page-builder sites see 100x+)</li>
<li>~60–80% fewer database queries per request</li>
<li>~60% lower peak PHP memory per request</li>
<li>~50–80% faster Time To First Byte (measured 54% on a content-heavy page, 67% on a short one)</li>
<li>On a site with 500 posts crawled monthly by major AI bots, that’s roughly gigabytes → tens of megabytes of monthly bandwidth and a fraction of the cumulative PHP execution time</li>
</ul>
Numbers vary by theme and content. Heavier setups (Elementor, Divi, Avada) see the biggest savings; lightweight themes see less dramatic but still meaningful gains. The conversion is cached as a transient, so repeated bot hits cost almost nothing.
<h4>How it works</h4>
<ul>
<li>AI crawlers are detected by User-Agent and served Markdown automatically — no configuration required.</li>
<li>Humans, search engines, and unknown bots receive your normal HTML output. ParseLess never affects what real visitors see.</li>
<li>The <code>?format=md</code> query parameter works on any post URL for manual preview or CLI piping.</li>
<li><code>/llms.txt</code> is published at your site root with a list of available content for AI indexers.</li>
<li>Conversion happens once per post and is cached. Subsequent requests serve a single transient read.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Automatic Markdown for known AI bots (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, CCBot, Google-Extended, Applebot-Extended, Bytespider, Meta-ExternalAgent, cohere-ai, and more)</li>
<li>Manual preview and CLI access via <code>?format=md</code> on any post URL</li>
<li><code>/llms.txt</code> endpoint for AI-indexing standards</li>
<li>Respects noindex flags from Yoast SEO, Rank Math, and Genesis</li>
<li>Skips private, draft, password-protected, and trashed posts</li>
<li>Works with all public post types (configurable)</li>
<li>Optional YAML frontmatter (title, URL, author, date, categories, tags, excerpt)</li>
<li>Transient-based caching with configurable TTL</li>
<li>Settings page at Tools → ParseLess for detection mode, bot list, cache TTL, post types, and llms.txt control</li>
<li>Per-post meta box with Markdown preview and copy-to-clipboard</li>
<li>Extensible via filters: <code>md4ai_bot_list</code>, <code>md4ai_supported_post_types</code>, <code>md4ai_markdown_output</code>, <code>md4ai_cache_ttl</code>, <code>md4ai_should_serve_markdown</code></li>
</ul>
<h3>Privacy and data collection</h3>
When logging is enabled (off by default), ParseLess records the following for 
each Markdown request:
<ul>
<li>Post ID, URL, and request timestamp</li>
<li>The full User-Agent header</li>
<li>A salted SHA-256 hash of the requester’s IP address (the raw IP is never stored)</li>
<li>Matched bot identifier, bytes served, and whether the response came from cache</li>
</ul>
IP hashes cannot be reversed from an email address, so the WordPress privacy 
exporter/eraser tools will report no personal data on demand.
Logs are pruned daily according to the configured retention window 
(7/30/90/365 days, default 30). Site owners can disable logging or click 
“Delete all logged requests” at any time from Tools → ParseLess.

ParseLess

Serve your posts as Markdown to AI crawlers and CLI tools — typically 95%+ less bandwidth, ~60–80% fewer DB queries, no theme bloat.

Ayuda WordPress

Fernando Tellado

AI Content Signals lets you declare, in a machine-readable way, how AI systems may use your content: for search indexing, real-time AI answers (RAG), or model training. It started with Cloudflare’s Content Signals in robots.txt and now expresses the same preferences across several surfaces, so more crawlers and tools can read them:
<ul>
<li>robots.txt — Cloudflare Content Signals (search / ai-input / ai-train)</li>
<li>HTTP header — <code>X-Robots-Tag: noai, noimageai</code></li>
<li>HTML meta — robots <code>noai, noimageai</code></li>
<li>/.well-known/tdmrep.json — W3C Text and Data Mining Reservation Protocol</li>
<li>EU Directive 2019/790 rights reservation</li>
</ul>
Everything is opt-in and does not change your robots.txt output unless you enable it.
The signals you control
You set three preferences, and AI Content Signals expresses each one in the right format on every surface you enable:
<ul>
<li>search — allow or deny search indexing and traditional search results (links and short snippets)</li>
<li>ai-input — allow or deny using your content for real-time AI answers (RAG, grounding, AI Overviews)</li>
<li>ai-train — allow or deny using your content to train or fine-tune AI models</li>
</ul>
These three come from Cloudflare’s Content Signals vocabulary, written to your robots.txt. When you deny AI training, the same opt-out is also emitted on any other surface you enable: <code>noai, noimageai</code> in an HTML meta tag and an <code>X-Robots-Tag</code> header, plus a <code>tdm-reservation</code> in your TDMRep manifest. Declaring the same preference in several places means a crawler that ignores one signal may still honor another.
Key Features
<ul>
<li>Easy-to-use settings page in WordPress admin</li>
<li>Set global defaults for all crawlers</li>
<li>Configure specific settings for individual AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.)</li>
<li>Add custom bot User-Agents</li>
<li>Supports both physical and virtual robots.txt files</li>
<li>Option to create physical robots.txt with basic WordPress rules</li>
<li>Preview generated Content Signals before applying</li>
<li>Export and import settings as JSON for easy migration between sites</li>
<li>Optional legal text with EU Directive reference</li>
<li>Developer-friendly: filter hook to extend the predefined bots list</li>
<li>Works with existing robots.txt from SEO plugins</li>
<li>Automatic sitemap detection and inclusion</li>
<li>Optional extra output surfaces: HTML robots meta tag (noai, noimageai), X-Robots-Tag header, and a W3C TDMRep file at /.well-known/tdmrep.json</li>
</ul>
Supported Bots
The plugin includes predefined settings for 28 major AI crawlers:
<ul>
<li>OpenAI GPTBot, OAI-SearchBot, and ChatGPT-User</li>
<li>Anthropic ClaudeBot, Claude-Web, and anthropic-ai</li>
<li>Perplexity Bot and Perplexity-User</li>
<li>Google Extended (Gemini) and GoogleOther</li>
<li>Amazon Bot</li>
<li>Apple Extended</li>
<li>Meta/Facebook Bot and meta-externalagent</li>
<li>DuckDuckGo DuckAssistBot</li>
<li>Allen Institute AI2Bot</li>
<li>Mistral AI</li>
<li>ByteDance Bytespider</li>
<li>DeepSeek AI</li>
<li>xAI Grok</li>
<li>Huawei Pangu</li>
<li>Common Crawl, Cohere AI, Diffbot, You.com Bot, and more</li>
</ul>
Important Notice
Content Signals is a declarative standard – it expresses your preferences but does not technically enforce them. AI companies are not legally required to respect these signals, though the plugin includes legal text referencing EU copyright directives.
The IETF AI Preferences (AIPREF) Working Group is currently developing a formal standard based on similar concepts. This plugin implements the current Cloudflare Content Signals specification and will be updated as standards evolve.
This plugin works best when combined with other protection measures like traditional robots.txt rules and server-level bot management.
<h3>Support</h3>
Need private support or custom development?
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:ai-content-signals@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.
Need help or have suggestions?
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/ai-content-signals/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
Love the plugin? Please leave us a <a href="https://wordpress.org/support/plugin/ai-content-signals/reviews/#new-post" rel="ugc">5-star review</a> and help spread the word!
<h3>About AyudaWP.com</h3>
We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

AI Content Signals

Control how AI uses your content — search, AI answers or training — via robots.txt Content Signals, HTTP headers, meta tags and TDMRep.

ParseLess vs AI Content Signals