The Approval Feed
Review, approve, or reject the team's proposed work.
What the Approval Feed is
Your Agentic SEO team can work in two modes. Some actions it applies on its own, the moment it makes them. Others it holds and waits for your sign-off. The Approval Feed is where that held work shows up, so you can read exactly what the team wants to do to a page, then approve it or reject it with a reason.
This matters because it is the safety valve on an autonomous system. Nothing you set to "Approval needed" ever touches your live site until you say yes. You get to watch the team's judgment before you trust it, and every time you reject something and explain why, that feedback trains the team on your preferences for next time.
Where it lives
Open Vibe SEO in your WordPress admin and go to the Agentic tool. Near the top of the page, above your daily report and settings, you will see a card titled Pending your approval with a count next to it, for example "Pending your approval (3)". It has an amber left edge so it stands out. If nothing is waiting, the card does not appear at all. That empty state is normal and usually good.
Below the heading is a short line reminding you that the team is holding these items because you set them to Approval needed, and that approving applies the change while rejecting with a reason teaches it your preferences.
Why something lands here
Whether an action needs your approval is decided per action type in the settings form lower on the same page, under What the team may do on its own. Each action has two choices: Full auto (applied the moment it is made) or Approval needed (held for you). The action types 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.
New teams default to Approval on everything. The recommendation built into the tool is to leave it that way for two to three weeks so you can see the kind of work being produced and the team can learn your style before it runs anything on its own.
How to review and decide, step by step
- Open the Agentic page and find the Pending your approval card.
- Read across each row. The table has four columns: Action (what kind of change, such as "Meta descriptions"), Page (the page it affects, which is a link straight to that page's editor when there is one), What it wants to do (a plain summary of the specific change), and the buttons.
- Click the Page link if you want to see the page in context before deciding. It opens the WordPress editor for that page.
- To accept a change, click Approve. The row disappears from the list right away. Your approval is recorded, and the team applies the change on its next pass.
- To decline a change, click Reject. The buttons are replaced by a text box with the prompt "To train your team better, tell it why you rejected this." Type a short reason, then click Submit rejection. If you change your mind, click Cancel to go back to Approve and Reject.
Every decision you make is also written to the What your agents did log further down the page, recorded as an approval or a rejection, so you always have a trail of what you signed off on.
What a good result looks like
A healthy Approval Feed is one you actually clear. You open it, you read each row, and you either approve confidently or reject with a specific reason. Over the first weeks the pending count rises and falls as the team works and you review. As you build trust in a particular action type, you switch that one action to Full auto in the settings, and it stops showing up here. The goal is to graduate the routine work to automatic while keeping a real human check on anything you are not ready to hand over.
Pro tips and common mistakes
- Reject with a reason, not just a click. The reason box is the training signal. A rejection with a clear "why" makes the team better. A silent rejection throws that away.
- Read the "What it wants to do" summary before approving. It is easy to rubber-stamp a list. The summary is there so you approve the actual change, not the category.
- Do not flip everything to Full auto on day one. The two to three week review window exists so the team can learn your voice first. Skipping it means the team runs on guesses about your preferences.
- An empty card is not a bug. No pending items means either the team has nothing to propose right now or everything is already set to Full auto. Check your per-action settings if you expected to see something.
- Approving does not mean instant. The change is applied on the team's next run, not the split second you click. If a page has not updated yet, give it a pass.
- Remember the master switch is separate. Turning the team off pauses all activity, but it does not clear or decide your pending items. Approvals are a per-action choice, not the on/off switch.