Mescio for Agents vs Conversion Agent Discovery

Conversion Agent Discovery helps WordPress sites expose public, read-only discovery surfaces for AI agents without pretending to support capabilities that are not implemented. It is designed to improve measurable agent accessibility for public, read-only discovery checks without calling external scanners automatically. Features include: Markdown negotiation for public content with Accept: text/markdown. Content Signals in robots.txt. Generated llms.txt and /.well-known/llms.txt. Editable AI Instructions page for official brand facts and LLM guidance, starting empty with English templates by default. Runtime Front-end Placement for exact, design-safe AI Instructions link placement across matching public header, footer, or page content components. [conversion_ai_instructions_link] shortcode for manual placement. Generated /.well-known/api-catalog. Generated /.well-known/agent-skills/index.json and virtual SKILL.md files. Local Agent Skills discovery schema generated by the site. Read-only WebMCP tool registration with runtime diagnostics for compatible browsers. Production-oriented Agentic Browsing readiness guidance for PageSpeed and Lighthouse checks. Optional origin isolation headers and optional Origin-Trial header for browser WebMCP runtime support. Opt-in declarative WebMCP form annotations for exact rendered form opening tags. Public read-only REST endpoints for site search, recent content, single content reads, site context, and contact handoff. Agentic Browsing diagnostics that separate plugin-controlled discovery surfaces from theme accessibility and layout stability checks. Admin settings page with a global public switch. Conversion Agent Discovery does not publish fake OAuth, MCP Server Card, A2A, or commerce metadata. The AI Instructions feature was inspired by Chris Long’s public LinkedIn post and Nectiv case study showing that AI Instructions pages can be cited by ChatGPT in branded queries. It also credits the earlier Seer Interactive AI Information page by Wil Reynolds and Alisa Scharf that Chris Long identified as an important example. References: Chris Long’s LinkedIn post: https://www.linkedin.com/posts/chris-long-marketing_holy-moly-seos-ai-instruction-pages-influence-share-7466096236799053824-_rpb/ Nectiv case study: https://nectivdigital.com/blog/aeo-experiment-chatgpt-cited-an-ai-instructions-page-in-48-hours Nectiv AI Instructions example: https://nectivdigital.com/ai-instructions Seer Interactive AI Information example: https://www.seerinteractive.com/ai-information Omniscient Digital AI Info example: https://beomniscient.com/ai-info/ llms.txt proposal by Jeremy Howard: https://llmstxt.org/ Important: this plugin does not guarantee LLM citations, search rankings, AI Overview visibility, or model behavior. It provides controlled public discovery surfaces for experimentation. External Services This plugin does not send requests to external services automatically and does not transmit visitor or site data to third parties. The generated Agent Skills discovery document uses a local schema URL served by the WordPress site at /.well-known/agent-skills/discovery-0.2.schema.json; it does not depend on an external schema service. The plugin contains optional external links that administrators or users may open manually: https://conversion.ag/ is linked for Conversion attribution and plugin author information. The plugin does not send visitor or site data to Conversion; the link is opened only when a user clicks it manually. Conversion’s privacy policy is available at https://www.conversion.com.br/politica-de-privacidade/. https://github.com/agencia-conversion/conversion-agent-discovery is linked as the public development repository and release source. The plugin does not send visitor or site data to GitHub; the link is opened only when a user clicks it manually. GitHub’s terms are available at https://docs.github.com/en/site-policy/github-terms/github-terms-of-service and GitHub’s privacy statement is available at https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement. https://wordpress.org/plugins/wp-graphql/ is linked from the admin screen when WPGraphQL is not detected, so administrators can optionally install it. The plugin does not send visitor or site data to WordPress.org; the link is opened only when an administrator clicks it manually. WordPress.org’s privacy policy is available at https://wordpress.org/about/privacy/ and terms are available at https://wordpress.org/about/terms-of-service/. https://pagespeed.web.dev/ is linked from the Agentic Browsing admin screen so administrators can manually test their public site in PageSpeed Insights. The plugin does not send visitor or site data to Google automatically; the link is opened only when an administrator clicks it manually. Google’s privacy policy is available at https://policies.google.com/privacy and terms are available at https://policies.google.com/terms. The developer-only tools/run-agentic-lighthouse.sh script is not run by WordPress and is never executed automatically. If a developer runs it manually, it uses npx to download and run Lighthouse from the npm registry and audits only the URL supplied by the developer. The optional WebMCP Origin Trial token field is empty by default. If an administrator adds a public Chrome origin trial token, the plugin sends it as an Origin-Trial response header on public pages together with the opt-in WebMCP origin isolation headers. The plugin does not request or generate tokens and does not make a server-side request to Google or Chrome services. Conversion’s privacy policy is available at https://www.conversion.com.br/politica-de-privacidade/. Privacy Conversion Agent Discovery does not track users and does not send site data to external services automatically. Outbound links in the admin screen and readme are plain manual links. Development Development happens at https://github.com/agencia-conversion/conversion-agent-discovery. The distributed plugin contains readable PHP, JavaScript, CSS, and SVG source files; no build step is required to run the plugin. Local Agentic Browsing validation can be run by developers with: tools/setup-agentic-fixture.sh tools/run-agentic-lighthouse.sh http://localhost:8089/ node tools/assert-agentic-lighthouse.mjs .context/lighthouse-agentic.json CAD_REQUIRE_WEBMCP=1 node tools/assert-agentic-lighthouse.mjs .context/lighthouse-agentic.json when running a Chrome runtime that exposes real WebMCP APIs. Public 0.4.0 launch materials are available in the repository: docs/launch-0.4.0.md docs/local-agentic-browsing-activation.md docs/demo-checklist-0.4.0.md docs/changelog-0.4.0.md

Mescio for Agents makes your WordPress site AI-ready by silently serving posts, pages and WooCommerce products as clean, structured Markdown to any AI agent or LLM pipeline that requests it — using the standard HTTP Accept: text/markdown content negotiation header. Human visitors using a browser are completely unaffected. Mescio for Agents only activates when an AI agent or crawler explicitly asks for Markdown. Why Markdown? Feeding raw HTML to an AI is expensive and noisy. A heading like ## About Us costs ~3 tokens in Markdown vs 12–15 tokens as HTML — before accounting for wrappers, navigation bars and script tags that carry zero semantic value. This blog post you are reading takes 16,180 tokens in HTML and 3,150 tokens in Markdown. That is an 80% reduction. Markdown has become the lingua franca for AI systems. Mescio for Agents lets your site speak it natively, at zero cost to your human visitors. How it works When an HTTP client sends a request with Accept: text/markdown, Mescio for Agents intercepts the WordPress request lifecycle before any template is rendered, converts the post content to clean Markdown, and returns it with the correct Content-Type: text/markdown header. curl https://yoursite.com/your-post/ \ -H "Accept: text/markdown" Features Zero configuration — works out of the box on any singular post, page or custom post type /llms.txt endpoint — auto-generated index of all your content in the llmstxt.org standard format, so AI agents can discover what’s on your site /llms-full.txt endpoint — full site content in a single Markdown file, ready for RAG pipelines WooCommerce support — product pages include price, SKU, stock status, rating, attributes and gallery; products are grouped by category in llms.txt YAML front matter — every document includes structured metadata (title, description, URL, date, categories, tags, featured image) Multilingual — detects language via WPML, Polylang, TranslatePress or WordPress locale; emits Content-Language and Link: rel=alternate headers REST API endpoint — /wp-json/mescio-for-agents/v1/markdown?id= or ?url= Page builder cleanup — aggressively strips Elementor, Divi, WPBakery and Beaver Builder layout noise Token count header — X-Markdown-Tokens tells AI pipelines how large the document is before processing Content Signals — emits Content-Signal: ai-train=yes, search=yes, ai-input=yes Correct HTTP caching — Vary: Accept ensures CDNs cache HTML and Markdown versions separately Response headers Content-Type: text/markdown; charset=utf-8 Content-Language: it (or detected language) Vary: Accept X-Markdown-Tokens: 725 Content-Signal: ai-train=yes, search=yes, ai-input=yes Link: ; rel="alternate"; hreflang="en" (when translations available) Multilingual plugin support WPML — reads language and available translations automatically Polylang — reads language and links to translated post IDs TranslatePress — reads trp_language post meta Manual — configure primary language and additional languages in Settings → Mescio for Agents REST API GET /wp-json/mescio-for-agents/v1/markdown?id=42 GET /wp-json/mescio-for-agents/v1/markdown?url=https://yoursite.com/my-page/ Developer hooks Filter: mescio_enabled_post_types — add or remove post types dynamically. Filter: mescio_pre_convert_content — modify the HTML before conversion to Markdown. Filter: mescio_post_convert_content — modify the Markdown after conversion. Privacy This plugin does not collect, store or transmit any personal data. It does not set cookies. It does not make external HTTP requests.