Supported editors and page builders (Classic, Gutenberg, WPBakery, Elementor, Divi)

What it is

Fix Content edits the real body text of a page, so it needs to understand how each editor stores that text. AISA's content fixer supports five: Classic, Gutenberg, WPBakery, Elementor and Divi. For each it extracts the text nodes (paragraphs and H2/H3) with their offsets, rewrites only the nodes that need it, and appends any expansion paragraphs inside the correct container so they render in the layout.

Handling differs by editor: Classic and Gutenberg are read natively from the post content (Gutenberg respects block comments). WPBakery and Divi pull text from inside their shortcodes (vc_column_text, vc_custom_heading; et_pb_text) without ever touching the shortcode structure. Elementor is parsed from its JSON data using a whitelist of standard widgets (heading, text-editor, image-box, icon-box, blockquote, call-to-action). Third-party Elementor widgets are recognised, counted, and ignored — AISA won't risk editing markup it doesn't understand.

Where to find it

The "🩺 Auto SEO Fix" meta box shows a badge for the detected editor (e.g. "Editor: Elementor"). When the editor isn't supported for content fixing, the badge says the body fix is coming for that editor and the Fix Content button stays disabled. For Elementor, the result reports how many third-party widgets were ignored, and a "↺ Restore Elementor content" button appears once a fix has run.

Requirements & tier

The detection and audit work for everyone; the content rewrite (Fix Content / Fix All) is Premium. Fix Content is only enabled when the editor is one of the five supported builders and there are failing content checks. The audit reads the true rendered content per builder — for Elementor it reads the real Elementor render, and for WPBakery/Divi it uses the same nodes the fixer extracts, so the audit and the fix always agree.

How to use

Open the post and check the editor badge in the Auto SEO Fix box.
If the badge shows a supported builder and content checks are failing, the Fix Content button is enabled.
Click Fix Content, confirm the consent modal, and let AISA rewrite only the needed nodes.
On Elementor, review the ignored-widgets count in the result.
To revert: Classic/Gutenberg/WPBakery/Divi use the normal WP revision; Elementor uses the dedicated "↺ Restore Elementor content" swap button.

Questions people ask

Which builders are supported? Classic, Gutenberg, WPBakery, Elementor and Divi.
What about third-party Elementor widgets? They're skipped on purpose and counted in the result, so your custom widgets stay untouched.
Does it edit shortcode structure in WPBakery/Divi? No — it only rewrites the text inside the modules; the [vc_*] / [et_pb_*] structure is never altered.
How do new paragraphs get added? Inside the last text block/column/module so they render correctly within the builder's layout.
Why is Fix Content disabled on my page? Either no content checks are failing, or the editor isn't a supported builder — the badge will tell you.

Troubleshooting

If the wrong editor is detected, AISA infers it from the content (Elementor data, [et_pb_/[vc_ shortcodes, or Gutenberg block comments) — make sure the page is saved in its real builder. On Elementor, if a fix didn't reach some text, that text likely lives in an ignored third-party widget (see the count) or in a non-whitelisted setting. Always use the Elementor restore button to revert, since Elementor revisions don't store the post meta the fixer changes.

Fix Content — let AI improve the page body · Auto SEO Fix — on-page audit and one-click fix · The SEO score badge and admin column.