Fix the content warnings a write sends back

A write that saves is not always a write that looks right. The agent put a style element in the markup and it was stripped out, or it used a block name your site does not have, or it filled an ACF block with keys ACF does not know. The plugin’s post, page and block writes tell the agent about all of this in a content_warnings list on the response, and most of the time nobody reads it.

This prompt makes reading it part of the job. The agent explains each warning, looks up what the block should have been, and fixes the affected blocks one at a time.

You just saved [the Landing page, id 88]. Look at the content warnings in
that write's response. If there are none, say so and stop.

For each warning, tell me in plain words which block it is about, what
the code means, and whether a visitor or editor would see something wrong
because of it.

Where a warning says a block is not registered, check the block types on
this site and suggest the closest real one. Where it says ACF ignored some
keys, open that block type and match my values to its real field names.

Read the page as raw block markup, then show me the fixed markup for each
affected block next to the current one. Do not save until I approve. When
I do, replace each block on its own, checking the block name at each
position, and confirm the warnings are gone.

Why this is safe to run

Reading the warnings, the page and the block type definitions changes nothing. Each warning names the block it is about, carries a stable code, and has a message written for the agent to act on, so the explanation is grounded in what the plugin returned, not in a guess.

The fixes are single Replace block calls, each against one block you approved, each checked against the block name expected at that position. Replace block is off until you enable it, it runs as the user you bound the agent to and needs edit access to the page, and every call lands in the Activity Log. If revisions are on, the page’s history holds each earlier version.

The best way to get fewer warnings is to check first: find the block types you can use before building, and read an ACF block’s fields before filling one.

Already connected? You do not have to paste this. Ask your agent for the “fix the content warnings a write sends back” recipe right after a write, and it runs the same review on your own site.