pressific

Pressific Bio for LLMs.txt gives you complete control over what AI models and LLM crawlers see when they visit your site. You paste the content, the plugin serves it — no scraping, no auto-generation, no API keys.
Think of it as your site’s “bio” for AI: the short pitch and the long story, served at the standardised URLs (<code>/llms.txt</code> and <code>/llms-full.txt</code>) that AI crawlers look for.
What makes this plugin different
<ul>
<li>AI indexing status dashboard — at-a-glance view of your site visibility, what’s currently being served at /llms.txt and /llms-full.txt, and whether each major AI crawler (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, and more) is allowed or blocked by your robots.txt.</li>
<li>Smart import — if another plugin or a static file is already publishing llms.txt content, one click imports it into the editor so you do not start from scratch.</li>
<li>Conflicting plugin detection — active llms.txt plugins that would fight ours are surfaced with a one-click deactivate link.</li>
<li>robots.txt AI crawler helper — opt-in toggle that appends explicit Allow directives for the major AI user agents to the virtual robots.txt served by WordPress.</li>
<li>Dead simple editing — two textareas, one save button. No wizards, no walls of settings.</li>
<li>Privacy-first — the only HTTP requests the plugin makes are loopback requests to your own site (for status checks and import). Zero external calls, zero tracking, zero API keys.</li>
<li>Lightweight — no JavaScript frameworks, no bloat.</li>
<li>Works everywhere — compatible with every theme and every caching plugin.</li>
</ul>
What is llms.txt?
The llms.txt standard (see <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a>) provides a way for websites to offer AI-friendly content. Think of it like robots.txt, but instead of telling crawlers where they can go, it tells AI models what your site is actually about.
<ul>
<li><code>/llms.txt</code> — a short summary with links to key pages.</li>
<li><code>/llms-full.txt</code> — an extended version with full content for deeper understanding.</li>
</ul>
Who makes this, and why is it free?
Pressific is a WordPress management service for business websites — hosting, maintenance, monitoring, backups, and real human support, all bundled. We built Pressific Bio for LLMs.txt because we needed it on our own managed client sites and couldn’t find an existing plugin that was both simple and trustworthy.
Rather than keep it private, we published it here. If we ever monetize anything in this space, it will be a completely separate product with its own name. This plugin stays free, forever, with every feature included.
If you want managed WordPress, we’re at <a href="https://pressific.com" rel="nofollow ugc">pressific.com</a>. If you just want the plugin — that’s the whole offer. No upsell coming. Enjoy.

Pressific Bio for LLMs.txt

100% free. No "pro" version. No tracking. No account. Just a simple llms.txt plugin Pressific built for itself and published for everyone.

Ayuda WordPress

Fernando Tellado

VigIA (Spanish for “lookout” or “watchman”, incorporating “IA” – Spanish for “AI”) is a complete AI visibility toolkit for WordPress. Monitor 55+ AI crawlers, control access to your content, and optimize how AI systems discover and understand your site.
<h4>What does VigIA do?</h4>
<ul>
<li>Scores your AI visibility with a 100-point analyzer covering 20 checks across 5 categories</li>
<li>Tracks AI crawlers visiting your site (GPTBot, ClaudeBot, PerplexityBot, and 55+ others)</li>
<li>Provides detailed analytics with advanced filters, server-side pagination, and exportable reports with metadata banner</li>
<li>Blocks unwanted crawlers via PHP (403 response)</li>
<li>Manages robots.txt rules for AI crawlers with compliance monitoring</li>
<li>Sends email alerts about crawler activity (daily, weekly, or monthly)</li>
<li>Generates llms.txt files to help AI systems understand your site</li>
<li>Serves markdown endpoints for posts, pages, taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products with schema-like data</li>
<li>Generates JSON-LD structured data with Site Identity and AI Discovery signals</li>
<li>Exposes abilities for AI agents and automation tools (WordPress 6.9+)</li>
</ul>
<h4>Key Features</h4>
AI Visibility Analyzer 
* 100-point scoring system with letter grades (A+ to F) 
* 20 individual checks across 5 categories 
* Access & AI Discovery (37 pts): robots.txt, AI bot directives, Content Signals, llms.txt, sitemap, RSS feed 
* Structured Data & Semantic Context (25 pts): JSON-LD schemas, Open Graph, Twitter Cards, meta description, canonical URL 
* Content Structure & Readability (20 pts): heading hierarchy, semantic HTML5, image alt text, content/HTML ratio 
* AI Interaction & Distribution (8 pts): markdown delivery, AI share buttons 
* Access Performance (10 pts): TTFB measurement 
* Smart recommendations with direct links to VigIA features and plugin suggestions 
* Analyze any page on your site with URL autocomplete selector 
* Results cached for 24 hours with manual re-analyze option
Analytics Dashboard 
* Total visits, unique crawlers, and pages crawled statistics 
* Timeline chart with daily breakdown 
* Category distribution (AI Training, AI Search, AI Assistant, Data Scraper) 
* Top crawlers and most crawled pages tables with paginated navigation 
* <a href="https://wordpress.org/plugins/ai-share-summarize/" rel="ugc">AI Share & Summarize</a> integration: see share button clicks per page 
* Recent activity log with content type and HTTP status columns (color coded by status family) 
* Advanced filters: multi-select crawler picker, content type, HTTP status code, and configurable date range 
* Server-side pagination with four-button pager (first, previous, next, last) — operates over the full database, not just the latest 500 rows 
* Period comparison functionality 
* CSV export with a metadata banner (site name, site URL, export type, date range, export timestamp, applied filters) 
* “Export filtered CSV” button that downloads exactly what the active filters return, with <code>vigia-filtered-YYYY-MM-DD.csv</code> filename 
* Content type detection distinguishes Home, Post, Page, Product, custom CPTs, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File, Admin / login attempts (<code>/wp-admin</code>, <code>/wp-login.php</code>), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other
Crawler Blocking 
* Block crawlers via PHP with 403 Forbidden response 
* Quick block dropdown in analytics dashboard 
* Manage blocks from Extras page 
* Works on any server (Apache, Nginx, LiteSpeed, etc.)
Robots.txt Management 
* Add Disallow rules for AI crawlers 
* Visual preview of your robots.txt 
* Compliance monitoring: see which crawlers ignore your rules 
* One-click blocking for non-compliant crawlers 
* Works with both physical and virtual robots.txt
Email Alerts 
* Daily, weekly, or monthly reports 
* Three detail levels: Minimal, Normal, Complete 
* Non-compliant crawler warnings 
* Activity comparison with previous period
Markdown for Agents 
* Serve posts, pages and any public post type as optimized markdown for AI agents 
* Serve taxonomy archive pages (categories, tags, WooCommerce product categories, custom taxonomies) as markdown — disabled by default, opt in per taxonomy 
* Dedicated .md URL endpoints (e.g., <code>/your-post.md</code>, <code>/category/news.md</code>, <code>/product-category/electronics.md</code>) 
* Accept: text/markdown content negotiation on posts and taxonomy archive pages 
* Discoverability via Link HTTP headers and <code><link rel="alternate" type="text/markdown"></code> HTML tags 
* YAML frontmatter for posts: title, date, modified, author, image, categories, tags, post type, lang 
* YAML frontmatter for taxonomy terms: title, description, url, type, taxonomy, parent, count, image (term meta), lang 
* WooCommerce product frontmatter adds schema-like fields: sku, product_type, price, regular_price, sale_price, currency, availability, stock_quantity, rating, rating_count, review_count 
* Taxonomy term body includes the term description (rendered through <code>the_content</code>), the list of direct child terms in hierarchical taxonomies, and an excerpt of the latest posts/products assigned to the term 
* Product listings inside <code>product_cat</code> archives include an inline summary with formatted price, “was X” on sale items, star rating and out-of-stock flag 
* Respects blocking rules (blocked crawlers get 403) and LLMs.txt exclusion filters 
* Per-term noindex detection from Yoast SEO, Rank Math, All in One SEO and SEOPress 
* Analytics integration: tracks markdown requests per crawler 
* X-Markdown-Tokens response header 
* Filters: <code>vigia_markdown_post_eligible</code>, <code>vigia_markdown_term_eligible</code>, <code>vigia_markdown_term_posts_limit</code> 
* Follows the Cloudflare Markdown for Agents standard
LLMs.txt Generator 
* Select content by post type with one click 
* Filter by taxonomies (categories, tags, custom) 
* Manual include/exclude with AJAX search 
* Exclude by URL patterns (wildcards supported) 
* SEO plugin integration (auto-exclude noindex content) 
* Auto-regeneration (daily, weekly, monthly) 
* Robots.txt integration (add llms.txt and llms-full.txt references) 
* Generate llms.txt and llms-full.txt files 
* Full content or excerpt mode 
* Compatible with Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer
JSON-LD Structured Data 
* Generate WebSite and Organization/Person schema for site identity 
* AI Discovery: ReadAction pointers to llms.txt, llms-full.txt, and Markdown for Agents endpoints 
* Social profiles and sameAs links for brand identity across the web 
* SearchAction for Google sitelinks search box 
* Media library integration for logo selection 
* SEO plugin conflict detection (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework) 
* Choose output page (front page or any published page) 
* Live JSON-LD preview with real-time updates 
* Smart integration with LLMs.txt and Markdown for Agents features
<h4>Supported AI Crawlers</h4>
VigIA monitors 55+ AI crawlers including:
<ul>
<li>OpenAI: GPTBot, OAI-SearchBot, ChatGPT-User</li>
<li>Anthropic: ClaudeBot, Claude-Web, Claude-SearchBot</li>
<li>Google: Google-Extended, GoogleOther, Gemini-Deep-Research</li>
<li>Perplexity: PerplexityBot, Perplexity-User</li>
<li>Meta: Meta-ExternalAgent, FacebookBot</li>
<li>Microsoft: BingBot</li>
<li>ByteDance: Bytespider</li>
<li>Amazon: Amazonbot</li>
<li>Apple: Applebot-Extended</li>
<li>And many more…</li>
</ul>
<h4>Privacy Focused</h4>
VigIA stores visitor data locally in your WordPress database. No data is sent to external servers.
<h3>Abilities API</h3>
VigIA is one of the first WordPress plugins to implement the <a href="https://developer.wordpress.org/apis/abilities-api/" rel="nofollow ugc">Abilities API</a> introduced in WordPress 6.9. This API allows AI agents, automation tools, and external systems to discover and interact with VigIA’s functionality in a standardized, secure way.
<h4>What are Abilities?</h4>
Abilities are self-contained units of functionality that VigIA exposes through WordPress’s central registry. Each ability has defined inputs, outputs, and permissions, making it easy for automation tools to understand and use them.
<h4>Available Abilities</h4>
VigIA registers the following abilities:
Analytics
<ul>
<li><code>vigia/get-crawler-stats</code> – Get statistics about AI crawler visits (total visits, unique crawlers, pages crawled)</li>
<li><code>vigia/get-top-crawlers</code> – Get a ranked list of most active AI crawlers</li>
<li><code>vigia/get-top-pages</code> – Get the most crawled pages on your site</li>
</ul>
Blocking
<ul>
<li><code>vigia/get-blocked-items</code> – List all blocked crawlers and IP addresses</li>
<li><code>vigia/block-crawler</code> – Block a crawler by User-Agent pattern</li>
<li><code>vigia/unblock-crawler</code> – Remove an existing block</li>
</ul>
Robots.txt
<ul>
<li><code>vigia/get-robots-rules</code> – Get current AI crawler rules in robots.txt</li>
<li><code>vigia/add-robots-disallow</code> – Add a Disallow directive for a crawler</li>
<li><code>vigia/remove-robots-rule</code> – Remove a robots.txt rule</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Automated monitoring: AI agents can query crawler statistics and alert you to anomalies</li>
<li>Reactive blocking: Automation tools can block crawlers that repeatedly ignore robots.txt</li>
<li>External dashboards: Aggregate data from multiple WordPress sites with VigIA installed</li>
<li>WP-CLI integration: Future command-line access through the Abilities API</li>
<li>n8n / Make workflows: Build custom automation flows using VigIA’s abilities</li>
</ul>
<h4>Requirements</h4>
The Abilities API ships with WordPress 6.9 and later. On older WordPress versions, VigIA works normally but abilities and MCP are not available.
<h3>MCP Server (Model Context Protocol)</h3>
VigIA exposes its 9 abilities as native MCP tools to any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Codex CLI, Antigravity, Continue, Cline, Zed and similar) using the official <a href="https://github.com/WordPress/mcp-adapter" rel="nofollow ugc">WordPress MCP Adapter</a>. The adapter ships bundled with the plugin, so the MCP endpoint is active right after installation — no Composer step or terminal access required.
<h4>Requirements</h4>
<ul>
<li>WordPress 6.9 or later (provides the Abilities API)</li>
</ul>
<h4>Quick connect (recommended)</h4>
Open VigIA > Extras > MCP and click “Generate password and connection commands”. The plugin creates a dedicated Application Password named <code>VigIA MCP</code> and renders ready-to-paste commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) for any other MCP client.
The plain password is shown only once. If you lose it, revoke the entry from the same panel and generate a new one.
<h4>Endpoint</h4>
<pre><code>https://your-site.example/wp-json/vigia/v1/mcp
</code></pre>
The endpoint uses HTTP Basic auth with the WordPress Application Password. The user must have the <code>manage_options</code> capability.
<h4>Connecting Claude Code</h4>
Quick Connect builds the full command for you. The shape is:
<pre><code>claude mcp add --transport http vigia https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD"
</code></pre>
Claude Code merges the new entry into its config file automatically — no risk of breaking other servers.
<h4>Connecting Cursor</h4>
Save the JSON block from Quick Connect as <code>~/.cursor/mcp.json</code>. You can also reach this file from inside Cursor at Settings → Cursor Settings → MCP.
If the file already exists with other content, see “Merging into an existing config file” below.
<h4>Connecting Claude Desktop</h4>
Save the JSON block from Quick Connect as <code>claude_desktop_config.json</code> in your user Library (this is not the system Library at the root of the disk):
<ul>
<li>macOS: <code>~/Library/Application Support/Claude/claude_desktop_config.json</code></li>
<li>Windows: <code>%APPDATA%\Claude\claude_desktop_config.json</code></li>
<li>Linux: <code>~/.config/Claude/claude_desktop_config.json</code></li>
</ul>
On macOS, the easiest way to reach the folder is to open Finder, press ⌘ Shift G, paste <code>~/Library/Application Support/Claude/</code> and hit Enter. On Windows, press Win+R and run <code>%APPDATA%\Claude</code>.
Important: Claude Desktop only speaks stdio to local processes, so the snippet does not connect directly to VigIA over HTTP. Instead it launches a small bridge package (<code>mcp-remote</code>) via <code>npx</code> that proxies the connection. This means you need <a href="https://nodejs.org/" rel="nofollow ugc">Node.js</a> installed on the machine. The first run downloads <code>mcp-remote</code> automatically; subsequent runs use the npm cache.
If you do not want to install Node.js, connect from Claude Code or Cursor instead — both speak HTTP MCP natively and do not need a bridge.
Restart Claude Desktop after saving the file. If the app boots with default preferences, the JSON is malformed — review the file or restore your backup. If Claude Desktop says the entry is “not a valid MCP server configuration”, <code>npx</code> is not in its PATH; check that Node.js is installed and accessible to GUI apps.
If the file already exists with other content, see “Merging into an existing config file” below.
<h4>Merging into an existing config file</h4>
If your <code>claude_desktop_config.json</code> or <code>~/.cursor/mcp.json</code> already exists, do not paste the full Quick Connect block on top of it. Pasting on top discards everything else (preferences, other MCP servers) and the app will start with defaults.
Always make a backup of the file first. Then open it with any text editor that preserves JSON.
There are two scenarios.
Scenario 1 — the file has content but no mcpServers block yet.
This is common when you have used Claude Desktop before but never configured MCP servers. The file might look like this:
<pre><code>{
 "preferences": {
 "menuBarEnabled": false,
 "...": "..."
 }
}
</code></pre>
Add <code>mcpServers</code> as a sibling property of <code>preferences</code>, separated by a comma. The result should be:
<pre><code>{
 "preferences": {
 "menuBarEnabled": false,
 "...": "..."
 },
 "mcpServers": {
 "vigia": {
 "command": "npx",
 "args": [
 "-y",
 "mcp-remote",
 "https://your-site.example/wp-json/vigia/v1/mcp",
 "--header",
 "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD"
 ]
 }
 }
}
</code></pre>
The order of <code>preferences</code> and <code>mcpServers</code> is not important, but the comma between them is required. Forgetting the comma makes the JSON invalid and Claude Desktop will start with default preferences.
Scenario 2 — the file already has mcpServers with other servers.
Add the <code>vigia</code> entry inside the existing <code>mcpServers</code> object, separated from other entries by a comma:
<pre><code>"mcpServers": {
 "other-server": {
 "...": "..."
 },
 "vigia": {
 "command": "npx",
 "args": [
 "-y",
 "mcp-remote",
 "https://your-site.example/wp-json/vigia/v1/mcp",
 "--header",
 "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD"
 ]
 }
}
</code></pre>
For Cursor the entry is different — Cursor speaks HTTP MCP natively, so its block uses <code>type</code>, <code>url</code> and <code>headers</code> directly inside the server entry instead of the bridge command. The Quick Connect panel renders the right format for each client.
<h4>Other MCP clients (Codex CLI, Continue, Cline, Antigravity, Zed, custom)</h4>
Most MCP clients accept HTTP transport with a custom Authorization header. The Quick Connect panel exposes the two raw values you need — the server URL and the Authorization header — so you can drop them into whatever configuration format your client expects.
Browser-only assistants without an MCP client (AI Studio, ChatGPT web) cannot connect. They need a desktop or CLI client that speaks MCP over HTTP.
<h4>Read-only mode</h4>
If you only want your AI to consult VigIA (not change anything), enable “Read-only mode” in the MCP tab. While on, write actions (block, unblock, robots changes) return a permission denied error. Read actions (statistics, top crawlers, blocked items, robots rules) keep working.
The toggle stores a <code>vigia_mcp_read_only</code> option that hooks into the <code>vigia_can_write_via_abilities</code> filter. Developers can still force read-only from a mu-plugin:
<pre><code>add_filter( 'vigia_can_write_via_abilities', '__return_false' );
</code></pre>
The mu-plugin filter at the default priority takes precedence over the toggle.
<h4>After connecting</h4>
Restart your MCP client after adding the server so it picks up the new tools. Then try a few prompts to confirm everything is wired up:
<ul>
<li>“Show me VigIA crawler stats for the last 7 days.”</li>
<li>“List the top 5 most crawled pages on this site.”</li>
<li>“Add a robots.txt Disallow rule for TestBot and then list the current AI crawler rules.”</li>
</ul>
The third example exercises a read + write + read round-trip, which is the most complete sanity check.
<h3>Support</h3>
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/vigia/" 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 5-star review and help spread the word!
<h3>About AyudaWP</h3>
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

VigIA – AI Visibility, Analytics & Control

Gran plugin mejor soporte

Monitor 55+ AI crawlers, control access via robots.txt, and boost your AI visibility with llms.txt, JSON-LD, Markdown for Agents & Visibility Score.

Pressific Bio for LLMs.txt vs VigIA – AI Visibility, Analytics & Control