Agurel AI Agent Ready Lite
| 开发者 | ahmtgurel |
|---|---|
| 更新时间 | 2026年7月26日 18:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Accept: text/markdown header, MP Agent Lite returns a clean Markdown version of your content. Regular visitors and search engines see nothing different.
Features
- Serves clean Markdown content to AI agents
- Adds RFC 8288 compliant Link headers for agent discovery
- Automatically adds Content Signals to robots.txt (ai-train=no, search=yes, ai-input=yes)
- Zero performance impact. No background processes, no cron jobs.
- No conflicts with any theme or page builder (including WPBakery and Elementor)
- Compatible with all caching plugins
- Clean uninstall. Leaves no trace.
- Dynamic llms.txt: auto-generated site index with summaries for AI agents
- Dynamic llms-full.txt: full page content for AI agents, updates automatically when new content is added
- Automatically includes author, date, and categories in Markdown output for blog posts
- AI Search Signals: automatic JSON-LD schema markup (Article, WebPage, WebSite) for better AI search visibility
- Author attribution in schema: automatically adds author name for blog posts (non-admin authors)
Accept: text/markdown header receives Markdown content, so the plugin works automatically with new AI bots as they appear, without needing an update. This list is provided for reference only.
Pro Version
The Pro version includes a dashboard to manage which bots can access your content, with granular control over assistant, search, and training bots. Also includes configurable Content Signals settings.
Get Agurel AI Agent Ready PRO
安装:
- Upload the plugin files to the
/wp-content/plugins/agurel-ai-agent-ready-litedirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the 'Plugins' screen in WordPress.
- That's it. No configuration needed.
常见问题:
Does the plugin add structured data (schema.org)?
Yes. Article schema is added for blog posts, WebPage for pages, and WebSite for the homepage. If you use an SEO plugin (Yoast, Rank Math, AIOSEO), both schemas coexist without conflict.
Does llms.txt update automatically?
Yes. Both llms.txt and llms-full.txt are generated dynamically. New pages and posts are included automatically without any action needed.
Will llms.txt conflict with my SEO plugin?
Some SEO plugins generate their own llms.txt. The plugin detects this and warns you. Disable your SEO plugin's llms.txt generation before enabling this feature.
Does Lite serve Markdown to Training bots?
Yes. In Lite, all bots including Training bots (GPTBot, anthropic-ai, CCBot, etc.) receive Markdown content. If you want to control which bots can access your content individually, upgrade to Pro.
Can I control which bots access my site?
Bot management is available in the Pro version. Pro includes a dashboard where you can enable or disable each bot individually, including Training bots.
Is MCP Server Card supported?
MCP Server Card (/.well-known/mcp.json) and A2A Agent Card (/.well-known/agent.json) are Pro features. They allow AI agents to automatically discover your site's capabilities.
Does this affect regular visitors?
No. The plugin only activates when a request includes the Accept: text/markdown header, which only AI agents send. Regular visitors, browsers, and search engines are completely unaffected.
Does this work with page builders like WPBakery or Elementor?
Yes. The plugin strips all shortcodes and HTML before serving Markdown, so page builder code is cleaned automatically.
Does this work with caching plugins?
Yes. Markdown responses include a Cache-Control: no-store header to prevent caching conflicts. On LiteSpeed servers specifically, the plugin also writes a rewrite rule to your .htaccess file that bypasses LiteSpeed's own page cache for Markdown, llms.txt, and llms-full.txt requests, since LiteSpeed's cache lookup is URL-based and doesn't take the Accept header into account on its own. This rule is ignored on non-LiteSpeed servers.
Will this slow down my site?
No. The plugin checks a single HTTP header on each request. If the header is not present, the plugin does nothing at all.
Does this work with WooCommerce?
WooCommerce is not officially supported or tested at this time. The plugin's Markdown negotiation may technically respond on product pages since it works with any WordPress content, but product-specific data (price, stock, variations, etc.) is not specially handled, and llms.txt/llms-full.txt only include standard posts and pages. If you run a WooCommerce store, treat this as untested. Proper WooCommerce support may be added in a future update.
What is the difference between Lite and Pro?
Lite works out of the box with no configuration. Content Signals are added automatically with recommended defaults. Pro adds a dashboard where you can control which AI bots can access your content and customize your Content Signals preferences.
更新日志:
- Fixed: llms.txt and llms-full.txt were returning a 404 Not Found status even though correct content was being served in the body, which could cause external scanners/validators to report these files as "missing". Both now explicitly return 200 OK.
- Performance: llms.txt and llms-full.txt now cache their generated output instead of rebuilding it from the database on every request. The cache clears automatically whenever a post or page is published, updated, or removed.
- On LiteSpeed servers, added a rewrite rule that bypasses LiteSpeed's own page cache for Markdown, llms.txt, and llms-full.txt requests, since LiteSpeed's cache lookup is URL-based and doesn't take the Accept header into account. Ignored on non-LiteSpeed servers.
- Updated the plugin description to accurately reflect the new lightweight caching (previously said "zero database writes")
- Added a FAQ entry clarifying that WooCommerce is not officially supported or tested
- Updated the Supported AI Bots list and clarified that Lite works with any bot automatically, since it doesn't filter by bot identity
- Added AI Search Signals: automatic JSON-LD schema (Article, WebPage, WebSite)
- Added author attribution for blog posts in schema markup
- Added author, date and category metadata in Markdown output for blog posts
- Add author, date and category metadata for blog posts in Markdown output
- Fixed duplicate Description header in plugin file
- Added dynamic llms.txt generator with page summaries
- Added dynamic llms-full.txt with full page content
- Fixed .htaccess rewrite rule positioning
- Added Content Signals via meta tag for SEO plugin compatibility
- Plugin renamed to Agurel AI Agent Ready
- Initial release: Markdown negotiation, RFC 8288 Link headers, Content Signals