Agentic Optimization helps WordPress sites expose public content to AI agents in a safer, WordPress-native way.
If SEO helped search engines discover, index, and understand websites, Agentic Optimization does something similar for AI agents, assistants, and LLM-powered tools. It gives public WordPress content clearer discovery files, cleaner read-only endpoints, and structured access paths that are easier for agentic systems to use responsibly.
Instead of trying to make AI tools scrape full themes, shortcodes, and plugin output blindly, this plugin helps site owners publish a more intentional agent-facing layer for public content.
Features in the free plugin:
- Root-level
llms.txt - Optional root-level
llms-full.txt - Root-level
agent-sitemap.xml - Optional WordPress
robots.txtenhancement with discovery hints - Public REST search, content, markdown, comments, categories, tags, and site info endpoints
- Read-only MCP endpoint with search, content, comments, taxonomy, and site info tools
- Hard request caps and transient-based rate limiting
- Privacy-friendly analytics with aggregate counts and hashed IP logs only
- Admin-managed site description and site details for llms.txt context
- SEO-aware content exclusion hooks for common noindex patterns
- Extension points for future add-ons and custom integrations
- Formatter and admin hooks for add-ons that extend post type coverage or editorial agent overrides
The plugin is intentionally conservative:
- Read-only only
- Public content only
- No drafts, private content, or pending comments
- Comments exposure disabled by default
- MCP disabled by default
- Analytics disabled by default
External Services
This plugin generates agent-optimized discovery files and sitemaps using standard XML formats.
Sitemaps.org XML Schema
The agent-sitemap.xml output uses the standard sitemap XML namespace (http://www.sitemaps.org/schemas/sitemap/0.9) and a custom extension URN namespace (urn:videowhisper:agentic:1.0). These are identifier strings embedded in locally generated XML documents only. No data is transmitted to external services when the sitemap file is generated or served.
- sitemaps.org protocol reference: https://www.sitemaps.org/protocol.html
