I confirm that name and acceptedAnswer are in the LD-JSON of the source code. Unfortunately they don’t show up when you unfold the FAQ element under ‘Detected Items’ in the Google Structured Data Testing Tool (see https://search.google.com/test/rich-results?url=https%3A%2F%2Fyoast.com%2Fyoastcon%2Ffaq%2F&user_agent=1).

However I can verify that given above, still Google is able to detect it and show it accordingly on the Google Search page (see https://www.google.com/search?q=site%3Ayoast.com+yoastcon+faq).

So let’s close it for know. We will continue to do further research why our FAQ is not showing up in Google Search (probably other policies).

Thanks,
Andre

• This reply was modified 1 month, 4 weeks ago by drsdre.

See https://github.com/Yoast/wordpress-seo/issues/15453

After some fiddling around, the code below (to be used as a plugin) is doing the job for me. If you implement this, you probably want to add a setting to enable it explicitly and also split the thirstyData field into specific fields.

<?php
/**
 * Plugin Name:     ThirstyAffiliates API
 * Plugin URI:      https://github.com/drsdre
 * Description:     Enable WP Core Rest API v2 for ThirstyAffiliates data
 * Author:          Andre Schuurman
 * Author URI:      https://github.com/drsdre
 * Text Domain:     thirstyaffiliates-api
 * Domain Path:     /languages
 * Version:         0.1.0
 *
 * @package         thirstyaffiliates-api
 */

/**
 * Add REST API support to thirstylink post type.
 */
add_action( 'init', 'thirstylink_post_enable_rest_api', 25 );
function thirstylink_post_enable_rest_api() {
	global $wp_post_types;

	$post_type_name = 'thirstylink';
	if ( isset( $wp_post_types[ $post_type_name ] ) ) {
		$wp_post_types[ $post_type_name ]->show_in_rest = true;
		$wp_post_types[ $post_type_name ]->rest_base    = $post_type_name;
		$wp_post_types[ $post_type_name ]->supports['custom-fields'] = true;

	}
}

/**
 * Add REST API support to thirstylink-category taxonomy type.
 */
add_action( 'init', 'thirstylink_category_enable_rest_api', 25 );
function thirstylink_category_enable_rest_api() {
	global $wp_taxonomies;

	$taxonomy_name = 'thirstylink_category';
	if ( isset( $wp_taxonomies[ $taxonomy_name ] ) ) {
		$wp_taxonomies[ $taxonomy_name ]->show_in_rest = true;
		$wp_taxonomies[ $taxonomy_name ]->rest_base    = $taxonomy_name;

	}
}

/**
 * Add REST API support to thirstylink title and thirstyData fields.
 */
add_action( 'rest_api_init', function () {
	register_rest_field( 'thirstylink', 'title', [
		'get_callback'    => function ( $thirstylink_data ) {
			$thirstylink_obj = get_post( $thirstylink_data['id'] );

			return $thirstylink_obj->post_title;
		},
		'update_callback' => function ( $title, $thirstylink_obj ) {
			$ret = wp_update_post( [
				'id'         => $thirstylink_obj->ID,
				'post_title' => $title,
			] );
			if ( false === $ret ) {
				return new WP_Error( 'rest_thirstylink_title_failed', __( 'Failed to update title.' ),
					[ 'status' => 500 ] );
			}

			return true;
		},
		'schema'          => [
			'description' => __( 'Thirstylink title.' ),
			'type'        => 'string',
		],
	] );

	register_rest_field( 'thirstylink', 'thirstyData', [
		'get_callback'    => function ( $thirstylink_data ) {
			$thirstylink_data_obj = get_post_meta( $thirstylink_data['id'], 'thirstyData', true );

			return $thirstylink_data_obj;
		},
		'update_callback' => function ( $data, $thirstylink_obj ) {
			$ret = update_post_meta( $thirstylink_obj->ID, 'thirstyData', $data);

			if ( false === $ret ) {
				return new WP_Error( 'rest_thirstylink_data_failed', __( 'Failed to update data.' ),
					[ 'status' => 500 ] );
			}

			return true;
		},
		'schema'          => [
			'description' => __( 'Thirstylink data.' ),
			'type'        => 'string',
		],
	] );
} );