Find and fix duplicate content

Duplicate content usually is not malicious, it is drift. You wrote two posts on nearly the same subject a year apart, or a category and a tag page cover the same ground, and now search engines have to guess which one to rank. Often they split the signal and rank neither.

This gives the agent the job of finding the overlaps and comparing them, and keeps the calls, which page wins, which points to it, which gets rewritten, with you. It never deletes or merges a thing. It sets canonicals through your SEO plugin and, only where you approve, edits a body to make the thin one genuinely different.

I want to find and fix duplicate or near-duplicate content about [our pricing
and plans]. I have [Yoast] turned on, and content writes are on too.

First pass, change nothing. Search my content for that topic, list the posts
that overlap, read them, and group them into clusters of near-duplicates or
thin repeats. For each cluster recommend: which post should be canonical, which
ones should point their canonical at it, and which are worth differentiating
rather than pointing away. Explain each call briefly.

I will tell you what to keep. Only after I approve, set the canonicals through
the SEO plugin and make any body edits I signed off on, work in small batches,
and show me each batch before it saves. Do not delete or merge anything, and do
not touch post status. At the end, list every post you touched and what changed
on each.

Why this is safe to run

The whole analysis pass is reads. Searching, listing, and reading the overlapping posts writes nothing, so the full cluster map and every recommendation reach you before a single save.

The write half is split and narrow. Canonicals go through your SEO plugin’s own field, which never touches the visible copy, and any body differentiation edits the content only and never publishes or unpublishes. Both the SEO write ability and the content write ability stay off until you enable them, every call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log with the post it changed. Body edits go through revisions, and there is no delete or merge in this recipe at all, so the destructive decisions stay firmly in your hands.

Already connected? Skip the paste. Ask your agent for the “find and fix duplicate content” recipe, or just name the topic, and it runs the same compare-then-approve flow on your own site.