Agentic Optimization – SEO for AI Agents

1. 01Upload the plugin folder to /wp-content/plugins/ .
2. 02Activate VideoWhisper Agentic Optimization in the WordPress admin.
3. 03Go to Settings > Agentic Optimization .
4. 04Enable the discovery outputs and APIs you want to expose.
5. 05Save settings to publish your selected endpoints.

Which SEO plugins can it read?

It reads WordPress search visibility and per-item/inherited robots settings from Yoast SEO, Rank Math, All in One SEO and SEOPress. Known noindex and unavailable supported-provider states are excluded while Respect noindex rules is enabled. Multiple providers are combined conservatively. Historical noindex flags are retained when no supported provider is active. Private, unpublished and password-protected content is always excluded, even if noindex protection is turned off.

The additive JSON seo context identifies its provider, resolution status and provider_settings scope. Titles, descriptions and canonical URLs use provider data where supported, otherwise editorial/permalink fallbacks. AIOSEO and SEOPress expose explicit fields rather than simulating all frontend templates. This is not a complete SEO suite or an exact simulation of arbitrary theme/frontend robots filters, redirects, headers or paginated URLs. It adds no competing SEO tags and never writes provider metadata. Review custom integrations separately.

Discovery caches reuse formatting only after checking current eligible items and SEO state. Metadata/settings edits invalidate caches, and stale in-flight builds cannot replace a newer generation. External caches that ignore no-cache headers must be purged separately. No indexing or ranking outcome is guaranteed.

What URLs does the plugin create?

When enabled, the plugin publishes:

• /llms.txt
• /llms-full.txt
• /.well-known/ai.txt
• /ai.txt
• /agent-sitemap.xml
• /robots.txt (enhanced virtual output when enabled)
• /wp-json/videowhisper-agentic-optimization/v1/search
• /wp-json/videowhisper-agentic-optimization/v1/content
• /wp-json/videowhisper-agentic-optimization/v1/markdown/<id>
• /wp-json/videowhisper-agentic-optimization/v1/comments/<post_id>
• /wp-json/videowhisper-agentic-optimization/v1/site-info
• /wp-json/videowhisper-agentic-optimization/v1/mcp

Does the free plugin allow writes?

No. The free plugin only exposes read-only access to public content.

Does this replace the REST or MCP endpoints?

No. WordPress Abilities are optional and additive. Existing REST, MCP, discovery, and OpenAPI-style integration surfaces remain available for clients that use them.

Does the plugin include the WordPress MCP Adapter?

No. If you want WordPress Abilities exposed to MCP clients through the official adapter, install and configure the WordPress MCP Adapter separately, then enable the Abilities settings in this plugin.

How can I test AI-agent routing?

Enable AI-agent routing on the Robots tab, then open any public post or page with ?vwao_agent=1 appended to the URL. The parameter name can be changed in settings.

Can agents access the normal human page?

Yes. Markdown responses include a human page URL with ?vwao_human=1 , which bypasses AI-agent redirects and returns the normal theme-rendered page.

What does the URL view parameter do?

When enabled, public single content URLs can render alternate views with ?vwao_view=markdown , ?vwao_view=json , ?vwao_view=html , or ?vwao_view=clean . Explicit view requests bypass AI-agent redirects.

Does it track visitors?

Analytics are disabled by default. When enabled, the plugin stores aggregate counters and recent event logs with hashed IP values only.

Where do I report security bugs found in this plugin?

Please report security bugs found in the source code of the undefined plugin through the Patchstack Vulnerability Disclosure Program . The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.