Trust levels
Your trust level determines how much authority agents have to apply changes without waiting for your explicit approval. You set one trust level per site, and you can change it at any time from Dashboard → Autopilot → Settings. Your setting does not affect changes that have already been applied — those remain in the Audit Log and can be rolled back regardless of what your current trust level is.Manual
You approve every change.All agent recommendations are queued in Pending Approvals. Nothing is written to your site until you review each item and click Approve. This is the safest mode and the recommended starting point for new users.
Supervised
Low-risk changes apply automatically. High-risk changes are queued.Agents apply changes that carry a low risk of unintended side effects — meta descriptions, alt text, JSON-LD injection — without asking. Changes that touch body content, headings, or internal link structure are queued for your review.
Full Autopilot
Agents apply all changes automatically.Every recommendation is applied as soon as the agent generates it, with no queue and no approval step. Best suited for teams that have reviewed agent behaviour on their site over time and are comfortable with the agent’s judgment. Every change remains fully reversible.
Regardless of trust level, agents always capture a before-state snapshot before writing anything to your site. Full Autopilot does not reduce the safety of individual changes — it only removes the manual approval gate.
What counts as low-risk vs. high-risk
In Supervised mode, Rankforce categorises each change type before deciding whether to apply or queue it:| Change type | Risk level | Supervised behaviour |
|---|---|---|
| Meta title update | Low | Auto-applied |
| Meta description update | Low | Auto-applied |
| Image alt text addition | Low | Auto-applied |
| JSON-LD structured data injection | Low | Auto-applied |
| Canonical tag update | Low | Auto-applied |
| Body content rewrite (GEO) | High | Queued for approval |
| Heading text change | High | Queued for approval |
| Internal link insertion | High | Queued for approval |
| New FAQ or HowTo section addition | High | Queued for approval |
Protected pages
Some pages are too important, too carefully crafted, or too legally sensitive to expose to any automated changes. The Protected Pages list lets you mark specific URLs that agents should never read or modify — regardless of your trust level. Common pages to protect:- Your homepage
- Pricing and plan comparison pages
- Terms of service, privacy policy, and legal pages
- High-converting landing pages with carefully tested copy
- Pages with custom structured data you’ve written manually
How to add a protected page
Open Autopilot Settings
Navigate to Dashboard → Autopilot → Settings and select the Protected Pages tab.
Add the URL
Paste the full URL of the page you want to protect, or select it from the dropdown list of crawled pages. You can add individual URLs or use a path prefix to protect an entire section (for example,
/legal/* to protect all pages under your legal directory).Every change is logged and reversible
Safe Autopilot doesn’t ask you to simply trust that agents did the right thing. It makes every change independently verifiable and reversible at any time.Before-state snapshots
Before an agent writes any change to your site — regardless of trust level — Rankforce captures a complete snapshot of the affected field or content block. This snapshot is stored against the Audit Log entry for that change and is used as the restore target if you roll back. Snapshots capture:- The exact current value of the field being changed (e.g., the current meta title string)
- The full page URL and the timestamp at the moment of capture
- The agent that proposed the change and the recommendation ID it belongs to
The Audit Log
Every agent action is recorded in the Audit Log — a timestamped, filterable record of every change proposed or applied across your site. From the Audit Log you can see exactly what each agent did, when it did it, and what the page looked like before and after. You can reach the Audit Log from Dashboard → Autopilot → Audit Log.One-click rollback
If you ever want to undo a change, find its entry in the Audit Log and click Rollback. Rankforce restores the before-state snapshot via the plugin and marks the entry as rolled back. The entire operation takes a few seconds and requires only a single confirmation click. Rollback is available for every applied change, including changes applied in Full Autopilot mode. There is no expiry on rollback availability — as long as the entry exists in your Audit Log, you can revert it.Rolling back a change does not delete the Audit Log entry. The entry is updated to show its Rolled Back status, the timestamp of the rollback, and who performed it. Your full history remains intact.
Best practices for new users
If you are connecting Rankforce to your site for the first time, the following approach will help you build confidence in agent behaviour before increasing automation.Start with Manual mode
Set your trust level to Manual for the first two to four weeks. Review every recommendation the agents surface, approve the ones you agree with, and reject the ones you don’t. This teaches you what the agents prioritise and lets you calibrate your trust.
Protect your most important pages
Before the first crawl completes, add your homepage, pricing page, and any legal pages to the Protected Pages list. These can always be optimised later under your direct supervision.
Review your first Audit Log
After approving your first batch of changes, check the Audit Log to confirm each one looks as expected. Spot-check a few pages on your live site to verify the changes are displaying correctly.
Graduate to Supervised mode
Once you’re comfortable with the quality of agent recommendations, switch to Supervised mode. Low-risk changes will apply automatically, saving you time, while high-impact content changes still come to you for review.