Restructure and rewrite key pages

Some pages grow by accretion. A paragraph gets added here, a section there, and two years later the page buries its point under three intros and a wall of text nobody reorganized. You know it needs a rewrite, but opening it and facing the whole thing at once is exactly why it never happens.

This lets the agent read the page cold, propose a tighter structure, and show you the rewrite next to what is there now. You approve before anything saves.

Read the page at [/pricing/] and help me tighten it. Do not change anything
yet.

First, give me your read: what the page is trying to say, where it repeats
itself, and where the structure works against the reader. Then propose a
cleaner outline (the headings in order) and a full rewrite, and show it next
to the current copy so I can compare section by section.

I will tell you which sections to keep. Only after I approve, apply the
rewrite to the page body. If a section only needs a small fix, do a targeted
find-and-replace on that exact text instead of rewriting the whole block.
Do not change whether the page is published. When you are done, list what you
changed and remind me the old version is saved as a revision.

Why this is safe to run

Reading the page writes nothing, so you see the proposed structure and the full rewrite before a single character is saved. You can approve the whole thing, approve section by section, or walk away.

When you approve, the write only edits the page body. It never publishes or unpublishes the page, and the find-and-replace option touches only the exact text you pointed at. WordPress saves the previous version as a revision, so a rewrite you dislike is one restore away. As always, the update ability is off until you enable it, every call is checked against the capability of the user you bound the agent to, and each edit lands in the Activity Log with the page it changed.

Already connected? Skip the paste. Ask your agent for the “restructure and rewrite key pages” recipe, or just point it at a page and say it reads rough, and it runs the same read-propose-approve flow on your own site.