> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rankforce.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Review and approve Rankforce agent recommendations
> Learn how to inspect, approve, or reject each Rankforce optimization recommendation from the approvals queue before changes go live on your site.
The approvals queue is your checkpoint between what Rankforce's agents recommend and what actually changes on your live site. Every time an agent identifies an optimization — a better meta description, a missing schema tag, a heading that could be restructured — it writes up a recommendation with a before-and-after preview and places it here for your review. Nothing in the queue touches your site until you say so.
## Where to find your approvals
Navigate to **Dashboard → Approvals** from the left sidebar. The number displayed on the **Approvals** menu item shows how many recommendations are currently waiting for your review. If you manage multiple connected sites, use the site selector at the top of the page to switch between queues.
If you're using **Supervised** Autopilot mode, only high-risk changes appear in the approvals queue — low-risk changes are applied automatically. On **Manual** mode, every recommendation lands here regardless of risk level. See the [Autopilot guide](/guides/setting-up-autopilot) for details on trust levels.
## Anatomy of an approval card
Each item in the queue is presented as an approval card. Before you approve or reject anything, take a moment to understand what each card is telling you.
The exact URL of the page where the change would be applied. Click the URL to open the live page in a new tab so you can see the current state with your own eyes before deciding.
Which Rankforce agent generated the recommendation — **SEO**, **GEO**, or **AEO**. This tells you the optimization category and the reasoning framework behind the suggestion.
A label describing what kind of change is proposed, such as *Meta Description Update*, *FAQ Schema Addition*, *Heading Restructure*, or *Alt Text Addition*.
A side-by-side or toggle view showing the exact current value (Before) and the agent's proposed replacement (After). For structured changes like schema, the preview shows the raw markup.
The card also shows the **estimated impact** of applying the change (Low / Medium / High) and a brief **agent rationale** explaining why the change was recommended and what improvement it's expected to deliver.
## Approve a single change
Click anywhere on an approval card to expand it and review the full before-and-after preview. For longer content changes, you can scroll through the preview panel to see the complete proposed text.
Read the agent's rationale and compare the Before and After values. If the change aligns with your content standards and intent, proceed. If something looks off — a tone mismatch, a factual inaccuracy, or an edit you simply disagree with — reject it instead.
Click the **Approve** button on the card. Rankforce applies the change to your live site immediately and moves the item from the queue to your audit trail with a timestamp.
If you want to use the agent's suggestion as a starting point rather than applying it verbatim, copy the proposed value from the preview, reject the card, and make the edit manually in your CMS. You'll get the benefit of the AI research without being locked into exact wording.
## Reject a change
Expand the card you want to dismiss by clicking on it.
Click the **Reject** button. A small dialog appears asking if you'd like to add an optional reason for the rejection — for example, *"Brand voice mismatch"* or *"Already handled manually"*.
Click **Confirm Reject** to dismiss the item. It disappears from the queue and is recorded in the audit trail as **Rejected**, along with your reason if you provided one.
Rejected items are not permanently forgotten. If the same underlying issue is detected again in a future audit, the agent may resurface it as a new recommendation. To prevent a specific type of suggestion from appearing again on a particular page, use the **Suppress this finding** option in the rejection dialog.
## Bulk approve multiple changes
When you have a large queue, approving items one by one can take time. Use bulk approval to clear groups of similar or trusted changes at once.
Check the checkbox on the left side of each approval card you want to approve. To select all visible items at once, check the **Select All** checkbox at the top of the list.
Once you've made your selections, click the **Approve Selected** button that appears in the action bar at the top of the queue. A confirmation dialog shows you a summary of how many items you're approving and which pages will be affected.
Click **Confirm** to apply all selected changes simultaneously. Rankforce processes each one in sequence and logs every change individually in the audit trail.
Bulk approval applies changes without requiring you to review each before-and-after individually. Before using bulk approval, filter the queue to a specific change type or agent you already trust — for example, selecting only *Alt Text Addition* items from the SEO agent keeps the scope narrow and predictable.
## Filter the approvals queue
On sites with a lot of activity, the queue can grow long. Use the filter controls above the card list to narrow down what you're looking at.
| Filter | Options |
| --------------- | ------------------------------------------------------------------------------------------- |
| **Agent** | SEO, GEO, AEO |
| **Change Type** | Meta Title, Meta Description, Schema, Heading, Body Copy, Alt Text, Internal Link, and more |
| **Page** | Search by URL or path segment |
| **Date** | Filter by when the recommendation was generated |
| **Impact** | Low, Medium, High |
Filters are additive — you can combine them. For example, filtering by **Agent: SEO** and **Impact: High** shows only the highest-value SEO recommendations, letting you prioritize those before working through lower-impact items.
## After you approve: what happens next
When you approve a change, Rankforce sends the update to your connected CMS immediately. For WordPress sites, the change is written through the Rankforce plugin using the WordPress API. For Framer sites, it's applied via the Rankforce integration token.
The item moves from the approvals queue to the **Audit Trail** under **Dashboard → Audit Log**, where it's recorded with:
* The page URL and field that was changed
* The before and after values
* The agent that recommended it
* The timestamp of your approval
* Your account name as the approver
Your site's SEO, GEO, and AEO scores update on the next audit cycle, which runs automatically or can be triggered manually via **Run Audit**.
## After you reject: what happens next
Rejected items are removed from the active queue and logged in the Audit Trail with a status of **Rejected**. Your site is unchanged. If you added a rejection reason, it's stored alongside the log entry.
Rankforce uses rejection patterns over time to calibrate future recommendations — if you consistently reject a certain type of change, the agents learn to deprioritize similar suggestions for your account.
## Reduce manual review with Autopilot
If you find yourself working through a large volume of approvals regularly, Autopilot can take the routine items off your plate.
Switching to **Supervised** Autopilot mode automatically applies low-risk changes — like meta description updates and alt text additions — without queuing them. Only high-risk changes, like body copy rewrites, continue to land in your approvals queue. This typically reduces queue volume by 60–80% for most sites. See the [Autopilot setup guide](/guides/setting-up-autopilot) to get started.