visiblyai

Search is changing. Google AI Overviews, ChatGPT Search, and Perplexity are now primary discovery surfaces — and they don’t rank pages the same way Google’s blue links do. Visibly AI helps you win both.
AI analyzes your content and tells you exactly how to improve each article for both traditional search rankings and AI citations.
Free features:
<ul>
<li>llms.txt auto-generator — Automatically creates and maintains an <code>llms.txt</code> file at your site root. AI crawlers use this to understand your content — think <code>robots.txt</code>, but for LLMs. Updates every time you publish or update a post.</li>
<li>Schema markup wizard — Guided setup for FAQ, HowTo, and Article structured data. These are the schema types that AI engines prefer when pulling citations.</li>
<li>Visibility score — A per-page score (green/amber/red) that tells you how AI-citable and search-optimized your content is: question/answer structure, heading hierarchy, meta description, concise definitions, and more.</li>
<li>Meta description editor — Native meta description field built right into the editor. Works alongside Yoast and Rank Math — Visibly AI detects them and stays out of the way.</li>
</ul>
Why Visibly AI?
WordPress powers 43% of the web. As AI Overviews, ChatGPT Search, and Perplexity become primary discovery surfaces, content needs to be optimized for both traditional search and AI answer engines. Visibly AI handles both without adding complexity.
Pro features (coming soon):
<ul>
<li>AI article optimizer — Connects to Claude AI to analyze your post and suggest specific improvements: better question/answer structure, stronger definitions, clearer headings.</li>
<li>Google Search Console integration — See exactly which queries you rank for, where AI Overviews are appearing, and which articles are closest to page one.</li>
<li>Content gap analysis — Find topics your competitors rank for that you’re missing.</li>
<li>One-click improvements — Accept AI suggestions directly in the editor.</li>
</ul>
<h3>External Services</h3>
This plugin optionally connects to the Visibly AI API to provide AI-powered content optimization suggestions (Pro feature only). The free version of this plugin does not make any external API calls.
Visibly AI API
<ul>
<li>What it does: Analyzes your post content and AEO signals, and returns specific copy-pasteable improvement suggestions powered by Claude AI (Anthropic).</li>
<li>What data is sent: When you click “Analyze with AI” in the editor, the plugin sends your post’s text content, a list of failing AEO signals, and your license key to the Visibly AI API.</li>
<li>When it is sent: Only when a Pro user manually clicks the “Analyze with AI” button. No data is sent automatically or passively.</li>
<li>License validation: When you save a Pro license key in the plugin settings, the key is sent to the Visibly AI API to confirm it is valid.</li>
<li>Service provider: Visibly AI (getvisiblyai.com)</li>
<li>Terms of Service: https://www.getvisiblyai.com/terms</li>
<li>Privacy Policy: https://www.getvisiblyai.com/privacy</li>
</ul>

Visibly AI — SEO & AEO Optimizer

AI-powered SEO and AEO for WordPress — rank in traditional search and get cited by AI answer engines.

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.

Visibly AI — SEO & AEO Optimizer vs ParseLess