Gutenberg and Classic Editor
How Aimogen Pro works inside the WordPress editors - blocks, the Content Wizard, the post creator sidebar, and block-aware content editing.
Aimogen Pro adds AI to both WordPress editors.
Blocks#
23 blocks in the Aimogen Blocks category. See Gutenberg blocks.
The Content Wizard#
Select text in the editor, choose an action, and the model rewrites it in place. Works in both Gutenberg and the Classic Editor.
Configure under Settings › Content Wizard. %%selected_text%% carries the highlighted text into the
prompt.
This tutorial was recorded before Aiomatic was renamed to Aimogen Pro. Some labels or interface elements may differ slightly from the current version.
This is the feature editors actually use day to day — more than any of the bulk tooling.
The AI post creator sidebar#
A panel in the editor for generating a whole post from a topic, without leaving the editor. The Gutenberg and Classic Editor versions are separate implementations of the same idea.
The AI custom field generator#
Added in 2.7.7. Generates custom field values with AI from inside the editor. Useful for ACF fields, theme options stored as post meta, and structured data.
The AI meta generator#
Generates SEO title and description from the editor, written into your SEO plugin.
Block-aware content editing#
The AI Content Editor can process Gutenberg content block by block:
| Setting | What it does |
|---|---|
Enable Gutenberg Block Support | Runs the editing prompt separately for each block, preserving structure |
Enable Editing For These Gutenberg Blocks | Restricts which block types are edited |
The block-type restriction is useful: edit paragraphs and headings, leave galleries, embeds and custom blocks alone.
Converting generated HTML to blocks#
Convert Gutenberg (Settings › General Settings) turns generated article HTML into proper Gutenberg
blocks rather than one classic block.
Enable it if your editors work in the block editor — they get editable paragraphs, headings and lists.
Leave it off if your theme or page builder prefers raw HTML.
Classic Editor#
The Classic Editor is detected and supported: the Content Wizard works there, and the plugin adds its buttons to the TinyMCE toolbar.
Editor availability settings#
Two settings under Settings › General Settings control where the editor integrations appear:
| Setting | Effect |
|---|---|
No Post Editor | Disables the post editor integration |
No Elementor | Disables the Elementor integration |
No Media Library | Disables the Media Library integration |
Useful on a site where editors should use AI only through specific tools.
Common problems#
The Content Wizard does not appear. It is disabled in settings, or the licence is not activated.
Blocks are missing from the inserter. Same causes.
Generated content is one big classic block. Convert Gutenberg is off.
Block layout broken after AI editing. Block support was not enabled.
Block validation errors after editing. The edited HTML no longer matches what the block expects. Use block support so blocks are edited individually.
Related#
Still stuck? Open a support ticket and include the diagnostics from Aimogen Pro › System & Logs › System Info.