You decided a batch of posts all belong under one tag, or should join a category you use for a landing page, and now you are opening each post just to tick the same box. It is the kind of repetitive edit that is easy to get wrong halfway through, and easy to accidentally clear an existing term while you are in there.
This applies the one term across the whole set at once, from a list you approve, and it only ever adds.
I want to add a single [tag] to a set of posts. First, find the posts thatmatch [the ones about onboarding in the "Guides" category] and list them so Ican confirm the batch. Then read the available terms and confirm the exact[tag] I mean, so we are not creating a near-duplicate.
Show me the full list of posts you are about to tag and wait for me to approve.The term should be added on top of whatever these posts already have, neverreplacing their current categories or tags. Once I approve, apply it in smallbatches and show me each batch. At the end, list every post you tagged so I cancheck a few.Why this is safe to run
The whole first pass is reads. Listing the posts and reading the terms writes nothing, so you confirm the exact batch and the exact term, near-duplicates and all, before anything is applied. You approve the full list, and any post that does not belong gets struck before a write happens.
The write only ever adds. The add-post-terms ability appends the term you named and leaves every existing category and tag on each post in place, so a bulk run cannot quietly strip a post’s current filing. The ability stays off until you enable it, every call is checked against your edit access to the post and the taxonomy’s assign-terms capability, and each change lands in the Activity Log with the post it touched.
Already connected? Skip the paste. Ask your agent for the “bulk-assign a category or tag” recipe, or just describe the set of posts and the term to add, and it runs the same approve-first, append-only flow on your own site.