Term fields are the ones everyone forgets. You add an accent color, an icon, or a short blurb to your category field group, style the archive around it, and then half the categories never get their value filled in, so the archive falls back to a plain default for the ones nobody got to.
This walks the whole taxonomy for you, shows you which terms are blank or inconsistent, and fills the gaps once you approve them.
I want every category in my [product] taxonomy to have its ACF [accent color] and[icon] set, and right now they are hit or miss.
Start read-only. Pull the ACF field groups so we agree on the field keys, listthe terms in [product], and read the current ACF values on each term. Hand me atable: term name, current color, current icon, and the value you propose foranything blank or off-pattern. I will paste a reference list of the values I wantwhere you need one.
I decide what changes. After I approve, write the values back a few terms at atime and show me each batch first. At the end, list every term you touched andwhat changed on it so I can reverse any single one.Why this is safe to run
The whole first pass is reads. Listing the field groups returns structure only, and listing the terms and reading each term’s ACF values writes nothing, so you see the full table of proposed changes before a single value is saved.
The write half reaches only the term fields you named, on only the terms in that taxonomy, and never touches a post filed under them. The ACF write ability stays off until you enable it, 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 term it changed. Because the read pass captured the old values, reversing any term is just writing its old value back.
Already connected? You do not have to paste this. Ask your agent for the “sync an ACF term field across a taxonomy” recipe, or just describe the field you want filled in, and it runs the same read-first flow on your own site.