Markdown for Agents and Statistics

FAQ

Where are the Markdown files stored?

Inside wp-content/uploads/{export_dir}/ (configurable in Settings). Post files
live under {export_dir}/{post-type}/{slug}.md. Taxonomy archive files live under
{export_dir}/taxonomy/{taxonomy}/{term-slug}.md. The directory is served by
WordPress when content negotiation is triggered.

Will this slow down my site?

No. Markdown files are generated ahead of time (on post save or via manual/CLI
bulk generation). Serving them is a simple file read, much faster than rendering
a full WordPress page.

What are taxonomy archive files?

For every public taxonomy term (categories, tags, custom taxonomies) the plugin
generates a Markdown file listing all published posts in that term with links and
excerpts. These are served automatically when an AI agent requests a taxonomy
archive URL. This lets agents navigate your site structure by exploring term listings,
not just individual posts.

What is the manifest.json file?

When you generate with --with-manifest or --incremental, a manifest.json is
created inside each post-type export folder (e.g. wp-mfa-exports/post/manifest.json).
It contains a registry of all exported documents with content hashes and change
tracking (new/modified/unchanged/deleted), enabling RAG systems to identify what
changed since the last export without reprocessing all documents.

How does incremental export work?

Use wp markdown-agents generate --incremental to only re-export documents that
have changed since the last export. The plugin compares content hashes against the
previous manifest.json and skips unchanged posts. This also generates a
changes.json delta file listing new, modified, and deleted documents — your RAG
system can read this to know exactly what to re-embed.

How do I configure fields per post type?

In Settings → Markdown for Agents, each enabled post type has its own
«Field Configuration» section with two textareas:

• Frontmatter fields — meta or ACF fields added to the YAML frontmatter.
• Content fields — meta or ACF fields used as the body content. When set,
  post_content is automatically excluded.

Use dot notation for ACF group fields (e.g. clause_fields.clause_summary).
Plain meta keys work too (e.g. _yoast_wpseo_title). ACF relationship fields
are automatically converted to a list of post titles.

Can I customise the Markdown output?

Yes. Several filters are available:

• markdown_for_agents_pre_convert — filter HTML before conversion
• markdown_for_agents_post_convert — filter Markdown after conversion
• markdown_for_agents_frontmatter — modify frontmatter fields for a post
• markdown_for_agents_taxonomy_frontmatter — modify frontmatter fields for a taxonomy archive
• markdown_for_agents_serve_enabled — enable/disable serving for a specific post
• markdown_for_agents_serve_taxonomies — enable/disable serving for taxonomy archive pages
• markdown_for_agents_file_generated — action fired after a file is written
• markdown_for_agents_file_deleted — action fired after a file is deleted

How do I generate taxonomy archives via WP-CLI?

wp markdown-agents generate-taxonomies
wp markdown-agents generate-taxonomies --taxonomy=category
wp markdown-agents generate-taxonomies --dry-run