No. The plugin only activates when a request includes the Accept: text\/markdown<\/code> header, which only AI agents send. Regular visitors, browsers, and search engines are completely unaffected.<\/p><\/dd>\nDoes this work with page builders like WPBakery or Elementor?<\/h3><\/dt>\nYes. The plugin strips all shortcodes and HTML before serving Markdown, so page builder code is cleaned automatically.<\/p><\/dd>\n
Does this work with caching plugins?<\/h3><\/dt>\nYes. Markdown responses are excluded from page caching via DONOTCACHEPAGE, nocache_headers(), and plugin-specific hooks for LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Fastest Cache, and SG Optimizer. Regular visitor and SEO bot caching is completely unaffected.<\/p><\/dd>\n
Will this slow down my site?<\/h3><\/dt>\nNo. The plugin checks a single HTTP header on each request. If the header is not present, the plugin does nothing at all.<\/p><\/dd>\n
Does this work with WooCommerce?<\/h3><\/dt>\nWooCommerce 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.<\/p><\/dd>\n
What is the difference between Lite and Pro?<\/h3><\/dt>\nLite works out of the box with no configuration \u2014 Markdown content negotiation, llms.txt, RFC 8288 Link headers, and Content Signals are included automatically.<\/p>\n\n
Pro adds: bot management dashboard, llms-full.txt, MCP\/A2A agent cards, JSON-LD schema markup (Article, WebPage, WebSite), Advanced Schema builder (LocalBusiness, Organization, Service, Person, FAQPage), Author Override, AI Agent Analytics, and Markdown Cache.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.13<\/h4>\n\n\n- Fixed: Markdown content now uses do_shortcode() instead of strip_shortcodes() \u2014 page builder content (WPBakery, Elementor, etc.) is properly rendered before text extraction<\/li>\n
- Fixed: Remaining unregistered shortcode markup cleaned via regex after rendering<\/li>\n
- Fixed: Added Surrogate-Control, Edge-Control and CDN-Cache-Control: no-store headers to Markdown responses \u2014 resolves cache bypass issues on GWS and similar CDN\/proxy layers<\/li>\n<\/ul>\n\n
1.0.12<\/h4>\n\n\n- Fixed: renamed X-Agurel-Ecosystem header to X-Agurel-Product for consistency across the Agurel plugin ecosystem<\/li>\n
- Added Agurel AI Agent Monitor link to admin panel<\/li>\n<\/ul>\n\n
1.0.11<\/h4>\n\n\n- Removed llms-full.txt \u2014 now a Pro-only feature<\/li>\n
- Removed JSON-LD schema markup (Article, WebPage, WebSite) \u2014 now a Pro-only feature<\/li>\n
- Removed author, date, and category metadata from Markdown output \u2014 now a Pro-only feature<\/li>\n
- Added cache bypass support for WP Rocket, W3 Total Cache, WP Fastest Cache, SG Optimizer, and LiteSpeed Cache \u2014 Markdown responses are now reliably excluded from all major cache plugins<\/li>\n<\/ul>\n\n
1.0.10<\/h4>\n\n\n- Added X-Agurel-Ecosystem header for Agurel plugin ecosystem detection<\/li>\n<\/ul>\n\n
1.0.9<\/h4>\n\n\n- Added Bytespider (ByteDance\/TikTok AI training crawler) to supported bots list<\/li>\n
- Added TikTokSpider (ByteDance\/TikTok AI training crawler) to supported bots list<\/li>\n
- Added Googlebot-Extended (Google AI Overviews) to supported bots list<\/li>\n<\/ul>\n\n
1.0.8<\/h4>\n\n\n- Corrected bot name: \"YandexBot\" (a classic search crawler, not AI-specific) was mistakenly listed as an AI bot in 1.0.7. Replaced with YandexAdditionalBot, the crawler Yandex actually uses to power YandexGPT live answers.<\/li>\n
- Added \"aeo\" tag<\/li>\n<\/ul>\n\n
1.0.7<\/h4>\n\n\n- Added YandexBot to supported AI bots list<\/li>\n
- Updated tags: replaced markdown with aivisibility<\/li>\n
- Tested up to WordPress 7.1<\/li>\n
- Added Kreosus support link<\/li>\n
- Removed isitagentready.com test button from admin panel<\/li>\n<\/ul>\n\n
1.0.6<\/h4>\n\n\n- 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.<\/li>\n
- 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.<\/li>\n
- 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.<\/li>\n
- Updated the plugin description to accurately reflect the new lightweight caching (previously said \"zero database writes\")<\/li>\n
- Added a FAQ entry clarifying that WooCommerce is not officially supported or tested<\/li>\n
- Updated the Supported AI Bots list and clarified that Lite works with any bot automatically, since it doesn't filter by bot identity<\/li>\n<\/ul>\n\n
1.0.5<\/h4>\n\n\n- Added AI Search Signals: automatic JSON-LD schema (Article, WebPage, WebSite)<\/li>\n
- Added author attribution for blog posts in schema markup<\/li>\n
- Added author, date and category metadata in Markdown output for blog posts<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Add author, date and category metadata for blog posts in Markdown output<\/li>\n
- Fixed duplicate Description header in plugin file<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Added dynamic llms.txt generator with page summaries<\/li>\n
- Added dynamic llms-full.txt with full page content<\/li>\n
- Fixed .htaccess rewrite rule positioning<\/li>\n
- Added Content Signals via meta tag for SEO plugin compatibility<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Plugin renamed to Agurel AI Agent Ready<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release: Markdown negotiation, RFC 8288 Link headers, Content Signals<\/li>\n<\/ul>","raw_excerpt":"Make your WordPress site AI agent-ready. Serves Markdown to AI bots, RFC 8288 Link headers, Content Signals, and dynamic llms.txt generation.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/306462","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=306462"}],"author":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ahmtgurel"}],"wp:attachment":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=306462"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=306462"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=306462"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=306462"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=306462"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=306462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}