Conversion Agent Discovery vs Markdown for Agents and Statistics

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

Markdown for Agents and Statistics converts your WordPress content to Markdown and serves it to AI agents and language model tools that request it via HTTP content negotiation (Accept: text/markdown). The Chancery Lane Project is a charity that helps organisations reduce emissions using the power of legal documents and processes. We’ve published this plugin as we believe that making content more legible for AI Agents makes a meaningful difference to their energy usage – not only by reducing the amount of tokens required (by up to 90% over HTML) to consume the content, but also minimising the server resources required to render, process and display pages at source. How it works: Posts and taxonomy archive pages are converted to Markdown and saved as static files on disk inside wp-content/uploads/. When a visitor (or AI agent) requests a page with Accept: text/markdown in the HTTP headers, WordPress serves the pre-generated .md file directly — no page render required. A tag is added to each page’s so agents can discover Markdown versions automatically. Features: Content negotiation (Accept: text/markdown, ?output_format=md, or known AI User-Agents) Taxonomy archive support — category, tag, and custom taxonomy term pages served as Markdown post listings Automatic Markdown generation on post save; taxonomy archives auto-update when any post in the term changes Background bulk generation — runs as a WP-Cron job with live progress, so it survives closing the tab and never times out a page request Per-post-type field configuration — choose which meta/ACF fields go in frontmatter or body ACF support with dot notation for nested group fields (e.g. group.subfield) Content fields option — use ACF fields as the body content instead of post_content Manifest generation with content hashes and change tracking per post type Incremental export — only re-export changed documents (--incremental) Delta file (changes.json) for RAG system sync Access statistics — logs AI agent requests with a dedicated stats admin page Access grouping by class of agent Optional frontmatter fields — hierarchy (parent/ancestors/children IDs), author display name, root-relative featured image paths Topics section — appends a ## Topics section with linked taxonomy terms to the Markdown body Export preview — preview generated Markdown inline in the post editor without writing to disk OKF directory indexes — index.md listings at the export root and in every post-type and taxonomy directory (Open Knowledge Format), kept current automatically OKF-compliant frontmatter and links — timestamp and flat cross-taxonomy tags frontmatter keys, and internal links rewritten to point at the Markdown file versions, always on Downloadable OKF bundle — optional .zip archive of the export tree with relative internal links, manifest.json, and an ARD discovery catalog panel, kept fresh via bulk-generation rebuilds and a debounced WP-Cron schedule ARD catalog generation — ai-catalog.json document for manual deployment to /.well-known/, discoverable by AI agent directories, shown automatically whenever the bundle toggle is on WP-CLI commands: generate, generate-taxonomies, generate-indexes, prune-stats, status, delete, bundle Fully unit-tested