Black Friday Sale is Live: Get up to 30% OFF RankReady Pro - the WordPress AI SEO pluginBlack Friday Sale is Live: Up to 30% OFF Get Deal
Features

Add your ACF and Secure Custom Fields values to the Markdown (Pro)

Last updated November 12, 2026

If you use Advanced Custom Fields or Secure Custom Fields, RankReady Pro adds your field values to the Markdown version of your posts. That is the version AI crawlers read when they request a page ending in .md. There is nothing to set up and no separate screen: every post type you serve as Markdown gets its fields.

Before you start

  • RankReady Pro is installed and the licence is active. Activate your licence.
  • Markdown output is switched on in RankReady, AI Visibility, Markdown, with the post types you want ticked.
  • Advanced Custom Fields or Secure Custom Fields is active. Without one of them, nothing is added.

How it works

  1. Open RankReady, AI Visibility, Markdown.
  2. Tick the post types you want served as Markdown, including custom post types.
  3. Save. Every supported field on those post types is now in their Markdown, in the header block.

To check a post, open its address with .md on the end. A post that is not published, is password protected or is excluded from RankReady gets no fields.

What it can read

  • Text, text area, number, range, email, URL.
  • Select, radio, button group, checkbox, true/false.
  • Date, date and time, time.
  • Link, image, file, WYSIWYG.
  • Taxonomy, relationship, post object, page link.
  • Group, repeater and flexible content. Lists are capped at 25 rows and nesting at 3 levels by default.

What it never reads

  • Password fields and user fields.
  • Fields whose name starts with an underscore, and fields marked private.
  • Fields on an options page.
  • Anything on a draft, private or password-protected post, or on a post you excluded from RankReady.
  • Clone and Gallery fields, and field types RankReady does not know.

To keep one field out, a developer can return true from the rnrd_pro_acf_field_is_private filter for it.

What it looks like

Each value is written as plain text on one line, so a field value cannot add a line or break out of the header block. The key is the field name with custom_ in front. For a text field named subtitle:

custom_subtitle: "A short note"

Good to know

  • Changing a field value, or saving a field group, refreshes the Markdown.
  • Updating from Pro 1.1: if you chose fields on the old Custom fields screen, that choice is kept exactly as it was, so nothing you left out starts showing.