Set Up Real-Time Data Feed Max on WordPress

Expose posts, pages, or custom post types as a JSON feed for your chatbot

Pro Plan

Running a WooCommerce store? Use our WooCommerce guide instead — it's purpose-built for product catalogs.

What Your Feed Should Look Like

Real-Time Data Feed Max accepts any public URL returning JSON or plain text. The AI reads whatever you give it — products, services, bookable slots, property listings, menus, opening hours, anything — and uses it to answer visitor questions. There is no required shape or field name.

The one exception is Dynamic Product Cards. If you want matching items to render as visual cards in the chat, use these specific field names: name, price, description, image_url, button_link, in_stock.

Example — products (triggers Dynamic Product Cards)

{
  "products": [
    {
      "name": "Wireless Headphones Pro",
      "price": "$149.99",
      "description": "Premium over-ear wireless headphones with ANC.",
      "image_url": "https://example.com/images/headphones.jpg",
      "button_link": "https://example.com/products/headphones",
      "in_stock": true
    }
  ]
}

Example — services (any shape works)

{
  "services": [
    {
      "service": "Deep tissue massage",
      "duration_minutes": 60,
      "price_from": "$95",
      "therapists_available": ["Anna", "Mark"],
      "booking_link": "https://example.com/book/deep-tissue"
    },
    {
      "service": "Haircut & style",
      "duration_minutes": 45,
      "price_from": "$55",
      "booking_link": "https://example.com/book/haircut"
    }
  ]
}

Example — plain text (works too)

Opening hours: Mon-Fri 9-6, Sat 10-4, closed Sunday.
Delivery: Free over $30, minimum order $15, within 5 miles.
Lunch specials (weekdays only):
- Margherita pizza $12
- Caesar salad $9
- Soup of the day $7

Rule of thumb: Use descriptive field names the AI can interpret (service, duration, price, location, etc.). If Dynamic Product Cards make sense for your business, follow the exact field names above. If they don't, use whatever shape fits your data — the AI still searches it and answers questions correctly.

Option 1 — Built-in REST API (fastest)

WordPress ships with a public REST API. Published posts and pages are readable without any authentication.

Posts:

https://your-site.com/wp-json/wp/v2/posts?per_page=100&_fields=title,excerpt,link,content

Pages:

https://your-site.com/wp-json/wp/v2/pages?per_page=100&_fields=title,content,link

Tip: The _fields parameter keeps the payload small by returning only the fields the AI actually needs — it cuts feed size dramatically on content-heavy sites.

Option 2 — Custom Post Types

If your knowledge lives in a custom post type (FAQs, properties, vehicles, events), make sure it was registered with show_in_rest: true — then it's available at a matching endpoint:

https://your-site.com/wp-json/wp/v2/faq?per_page=100
https://your-site.com/wp-json/wp/v2/property?per_page=100

If you created your custom post type without REST support, add this to your theme's functions.php or via a snippets plugin:

add_action('init', function() {
  // Enable REST API for an existing custom post type
  global $wp_post_types;
  if (isset($wp_post_types['faq'])) {
    $wp_post_types['faq']->show_in_rest = true;
    $wp_post_types['faq']->rest_base = 'faq';
  }
});

Option 3 — Custom Endpoint (full control)

For full control over fields, combining multiple post types, or including Advanced Custom Fields (ACF) data, register your own REST route:

add_action('rest_api_init', function() {
  register_rest_route('ai-feed/v1', '/content', [
    'methods' => 'GET',
    'permission_callback' => '__return_true',
    'callback' => function() {
      $posts = get_posts([
        'post_type' => ['post', 'page', 'faq'],
        'posts_per_page' => -1,
        'post_status' => 'publish',
      ]);
      $out = [];
      foreach ($posts as $p) {
        $out[] = [
          'name'        => $p->post_title,
          'description' => wp_strip_all_tags($p->post_content),
          'button_link' => get_permalink($p->ID),
          // Add ACF fields if you use them:
          // 'category' => get_field('category', $p->ID),
        ];
      }
      return ['products' => $out];
    }
  ]);
});

Feed URL: https://your-site.com/wp-json/ai-feed/v1/content

REST API size limits: The built-in endpoints cap at 100 items per page. For sites with more than 100 items, use Option 3 to return everything in one response, or switch per_page=100 and combine multiple requests server-side before exposing.

Troubleshooting

I see a password page instead of JSON

Your site is in maintenance, staging, or password-protected mode. Real-Time Data Feed Max needs a fully public URL.

Real-Time Data Feed Max says the feed failed

Open the URL in a private browser window. If you don't see JSON, the URL is wrong or the endpoint is down. If you see JSON but we still fail, the response may be missing a Content-Type: application/json header or exceeding the 10,000,000 character limit.

Product cards don't render

Dynamic Product Cards require specific field names (name, price, image_url, button_link, in_stock). If your platform uses different names, reshape the response in a small custom script before exposing it.

Data looks wrong or outdated

The feed auto-refreshes every 24 hours. For immediate updates, click Refresh Now in Real-Time Data Feed Max. For live fields (price, stock), the AI pulls fresh data on every message — so the 24h cycle only affects which items are known, not their current state.

Feed size exceeded

Real-Time Data Feed Max accepts up to 10,000,000 characters (~25,000 items). If you exceed that, trim fields (skip long HTML descriptions), split your catalog, or use the standard Real-Time Data Feed alongside for secondary data.

Still stuck? Start with the simplest option for your platform and verify the URL works in a browser before pasting it into Real-Time Data Feed Max. You can always upgrade to a more advanced option later — only the URL field changes on our side.

Documentation