Per-Action Autonomy
Decide, per task, what runs full-auto and what needs approval.
Per-Action Autonomy
Your Vibe SEO agents can do a lot of work on your site. The question is how much of it you want to happen automatically, and how much you want to sign off on first. Per-action autonomy is where you make that call, one type of work at a time. You are not stuck choosing between "the agents run wild" and "the agents do nothing." You decide, action by action, whether each change goes live the moment it is made or waits for your approval.
Why this matters
Not all changes carry the same weight. A tightened meta description is low risk. A brand new page for a service area, or a public reply to a Google review, is something you may want to read before it goes out. Per-action autonomy lets you turn the safe, routine work loose while keeping a hand on anything customer facing or higher stakes. New teams start with everything set to approval, so nothing goes live until you have seen the kind of work the team produces.
Where it lives
Open the Agentic page in your Vibe SEO dashboard. Scroll to the settings box with the heading "What the team may do on its own." Inside is a table with one row per action and two columns of choices: Full auto and Approval needed.
Just above that table are two related controls. The "Turn the SEO team on" checkbox is the master switch. When it is off, nothing runs at all. When it is on, the team works, and your per-action settings decide what needs sign-off. There is also a "Daily change limit" field that caps how many changes the team can make in a day. The default is 30.
The actions you control
Every kind of work the team can do is listed separately:
- Meta descriptions, rewriting a page's search snippet
- Title tags, rewriting a page's SEO title
- Heading structure, fixing heading levels and hierarchy
- Content rewrites, improving the wording of existing page copy
- Internal links, adding relevant links between your pages
- Schema markup, structured data and FAQ schema
- Blog posts, writing and publishing new blog articles
- New pages, creating new service area or expansion pages
- Google Business posts, posting updates to your Google Business Profile
- Google review replies, replying to your Google reviews
- Outreach drafts, drafting link building and partnership outreach
When the team turns New pages loose, it builds them through Page Generation under the hood, and Block Variations rotate the wording so each new service area page reads as unique rather than a thin duplicate of the last.
How to set it
For each row, click Full auto or Approval needed, then click Save at the bottom of the box.
Full auto means the change is applied the moment the team makes it. Approval needed means the change is held for you. The team still does the work, it just parks the result until you say yes.
When something is held, it shows up in a "Pending your approval" card near the top of the same page, with a count of how many are waiting. Each row tells you the action, the page it affects, and what it wants to do. You get two buttons: Approve applies the change, Reject holds it back. When you reject, a box appears asking why. Take a second to fill it in. That reason trains your team, so it makes fewer of the same kind of change you did not want.
What a good result looks like
A well tuned setup usually has the low risk, high volume work on Full auto and the visible or one time work on Approval needed. A common pattern: meta descriptions, title tags, headings, internal links, and schema on Full auto, with blog posts, new pages, Google Business posts, and Google review replies held for approval. Your pending queue stays short because most routine work flows through on its own, and the items that reach you are the ones actually worth a look.
Pro tips and common mistakes
Leave everything on Approval needed for the first two to three weeks. This is the built in recommendation, and it is the right one. You see the exact kind of work the team produces, and the team learns your style and preferences from what you approve and reject before it ever runs on its own. Loosen actions one at a time as you build trust.
Do not confuse the master switch with autonomy. Turning the team on does not mean everything goes live. With every action on Approval needed, the team still works, but nothing publishes until you approve it.
Always give a reason when you reject. A blank rejection removes the change but teaches nothing. A one line reason is the single most useful thing you can do to shape the team.
Finally, watch the daily change limit. If your pending queue or activity log looks quiet, check whether the team has hit its cap for the day, then raise the limit if you want more done.