The Content Parser addon works in the background — you don’t need to do anything manually. Its purpose is to help AI Engine handle content it can’t parse by default. For example, when using Content Awareness or syncing embeddings, certain content like ACF fields wouldn’t normally be included. With the Content Parser, that data is retrieved and treated as part of the main content automatically.
If you see only red ❌ icons in the Plugins section, it means none of those plugins were detected as installed on your server. That list shows all the themes and plugins the Content Parser is currently compatible with. If the plugin or theme you’re using isn’t listed there, the parser won’t provide any benefit for it.
If you need support for a new plugin or theme, just let us know — we can add a parser for that specific use case. If it’s a paid plugin, you can share a ZIP file and a license with us, and we’ll create a test environment to build a parser for you and other users.
Custom Meta-data
If you’re not interested in using a specific plugin’s post-related data, or if you’ve built your own plugin or custom post metadata manually, you can declare key–name pairs manually. Whenever a post is parsed, AI Engine will check if the specified key exists in the post meta, and if it does, it will include that value in the parsed content using the name you’ve registered.
Example
| Post ID | Post Content |
|---|---|
| 1 | Hello World! |
| Post Meta ID | Post ID | Key | Value |
|---|---|---|---|
| 998 | 1 | total_likes | 145 |
| 999 | 1 | total_dislikes | 11 |
Post Content Without Content Parser:
Hello World!Post Content With Content Parser:
Hello World!
User positive reviews: 145
User negative reviews: 11Of course, as with any AI Engine feature, this can be done for free without any add-on by building it yourself — all the add-ons rely on AI Engine filters, which you can also use. The add-ons are simply convenient no-code solutions we provide.