Turning the Team On
The master switch and what it does and does not control.
Turning the Team On
Agentic gives you an autonomous SEO team that works on your site continuously. It scans for issues and improves your content on its own, and it never touches your design or theme. Before any of that happens, you have to do two things: switch the team on, and decide how much it is allowed to do without asking you first. This lesson walks through both, exactly as they appear on the Agentic page in your Vibe dashboard.
What the master switch actually is
Near the settings box you will find a checkbox labeled "Turn the SEO team on." This is the master switch. When it is checked, the team runs: it scans your site and does its work. When you uncheck it, everything pauses instantly. Nothing is scanned, nothing is changed, and no work is queued. It is the one control that turns the whole operation off in a single click.
The important thing to understand is what the switch does not do. It only controls whether the team runs at all. It does not decide what the team is allowed to change on its own. As the page itself says, "This only controls whether the team runs at all. What needs your sign-off is set per action below." So flipping the switch on does not hand the team free rein. It just starts the engine. The approval rules you set separately still apply to every single change.
Out of the box the switch is off. Nothing runs until you turn it on, which means you are always the one who starts the team.
Per-action approval is a separate decision
Directly below the switch is a section titled "What the team may do on its own." This is where the real control lives. Every type of work the team can perform is listed as its own row, and for each one you pick between two settings:
- Full auto means the change is applied the moment it is made.
- Approval needed means the change is held for you to approve or reject before it goes live.
The actions you can govern individually are Meta descriptions, Title tags, Content rewrites, Heading structure, Internal links, Schema markup, Blog posts, New pages, Google Business posts, Google review replies, and Outreach drafts. Each row has a short description so you know exactly what it covers.
New teams default to Approval needed on everything. That is deliberate. With everything set to Approval needed, the team still does all of its work, it just parks each result for your sign-off instead of publishing it. You lose nothing by leaving it there, and you get to see the kind of work being produced before you trust it to run unattended.
Step by step
- Open the Agentic page in your Vibe dashboard. Confirm the top of the page reads "Agentic is active." If it does not, your access key does not include the Agentic add-on yet. Add the add-on from your account, enter that key in the Access key box, and save.
- Find the settings box and check "Turn the SEO team on."
- Set the Daily change limit if you want a tighter cap. It defaults to 30 changes per day and accepts any number from 1 to 200. This is a safety backstop, not a target.
- Go through the per-action list and leave every action on Approval needed for now.
- Click Save.
Once saved, the status line near the top will show a green dot and read "Your agents are running," alongside a counter of how many changes have been made today against your daily limit.
What a good result looks like
After the first run, held changes show up in a panel called "Pending your approval". Each row tells you the action, the page it affects, and what it wants to do, with Approve and Reject buttons. Approving applies the change. Rejecting lets you type a short reason, and that reason trains your team to match your preferences over time. A healthy first few weeks looks like a steady stream of items in this panel that you mostly approve, with the occasional rejection teaching the team where your line is.
Pro tips and common mistakes
- Leave everything on Approval needed for 2 to 3 weeks. This is the recommendation on the page itself. It lets you watch the work and lets the team learn your style before it runs on its own.
- When you reject something, always give a reason. A blank rejection removes the change but teaches nothing. A one line reason is how the team gets better.
- Do not confuse the switch with the approval settings. Turning the team on with everything still on Approval needed is the safe, correct starting point, not an oversight.
- Use the daily limit as a backstop, not a throttle you fiddle with. The default of 30 is fine for most sites.