Fix Content — let AI improve the page body

What it is

Fix Content is the step beyond Auto SEO Fix: it doesn't just rewrite meta, it edits the page body to clear the content-level audit failures. Guided by the failing checks, it can place the keyphrase in the first paragraph, raise keyphrase density naturally across one or two paragraphs, work the keyphrase into a subheading, and expand thin content with new paragraphs that match your tone and brand. It does this with a single AI call that returns targeted node rewrites plus any new paragraphs, then validates each change (keyphrase kept verbatim where required) before applying.

Crucially, edits are positional. AISA extracts the real text nodes (paragraphs, H2/H3) with their offsets and rewrites only the nodes that need it — never a global search-and-replace. Nodes containing links, images or shortcodes are locked and left untouched, so it won't destroy markup. Because the content is being modified, AISA shows a consent modal first and saves a restore point.

Where to find it

The 📝 Fix Content button sits in the "🩺 Auto SEO Fix" meta box on the editor, next to Fix SEO and Fix All. The box also shows a badge for the detected editor (e.g. "Editor: Gutenberg") and, for Elementor, how many third-party widgets were ignored.

Requirements & tier

Fix Content is Premium and only enabled when the editor is supported and there are failing content checks (intro, density, heading, or length). In Cloud mode it shows a 2–3 credit cost (2 for targeted rewrites, 3 when text expansion is needed). Supported editors are Classic, Gutenberg, WPBakery, Elementor and Divi; third-party Elementor widgets are recognised but ignored.

How to use

Run the audit and confirm at least one content check (first-paragraph keyphrase, density, heading, or word count) is failing.
Check the editor badge in the box to confirm your builder is supported.
Click 📝 Fix Content.
Read the consent modal — it warns the body will be modified and that a restore copy is saved — then confirm.
Let the single AI pass run; AISA rewrites only the needed nodes and appends any expansion paragraphs.
Review the page. For Classic/Gutenberg/WPBakery/Divi a normal WP revision is saved; for Elementor use the "↺ Restore Elementor content" button if you want to revert.

Questions people ask

Will it rewrite my whole page? No — only the specific nodes that fail the audit, plus optional new paragraphs for expansion.
Are links and images safe? Yes. Nodes with links, images or shortcodes are locked and never rewritten.
How do I undo it? Classic/Gutenberg/WPBakery/Divi save a WP revision; Elementor saves its own backup with a one-click restore swap.
Does it handle my page builder? Classic, Gutenberg, WPBakery, Elementor and Divi are supported. Third-party Elementor widgets are skipped and counted in the result.
What does it cost in Cloud? 2 credits for rewrites, 3 if content expansion is included; the exact estimate is shown in the consent modal.

Troubleshooting

If the button is greyed out, either no content checks are failing or the editor isn't supported — the badge will say so. If an expected change didn't happen, the verbatim guard likely rejected an output that dropped the keyphrase, so that node was left as-is. On Elementor, remember third-party widgets are ignored by design (the count is reported); use the restore button to revert since Elementor revisions don't store the post meta. New paragraphs are inserted inside the last text block/module so they render within the layout.

Auto SEO Fix — on-page audit and one-click fix · Supported editors and page builders · The SEO score badge and admin column.