Skip to main content
Every time a Rankforce agent proposes or applies a change to your site, that action is recorded permanently in the Audit Log. The log is your complete, timestamped record of what changed, when it changed, which agent changed it, and exactly what the page looked like before. If you ever want to undo something — whether it was applied five minutes ago or five months ago — the Audit Log is where you go. This page explains what the log contains, how to navigate it, and how rollback works.

​
What the Audit Log is

The Audit Log is a chronological, filterable record of every action taken by any Rankforce agent on your connected site. It captures both changes that were applied automatically (in Supervised or Full Autopilot mode) and changes that were queued and manually approved, giving you a single source of truth for everything Rankforce has ever done. The log is not just a record — it is also the control panel for reverting changes. Each entry carries the full data needed to restore your site to its exact previous state, and that restore operation is available at any point, with no time limit.
The Audit Log records agent proposals as well as applied changes. If an agent recommended a change that you rejected, that rejection is also logged — so you always have a complete picture of what agents analysed, not just what they wrote.

​
What each log entry contains

Every entry in the Audit Log captures the following information:

Page URL

The full URL of the page the change was applied to, linking directly to the live page so you can verify the current state with one click.

Change type

The category of change — for example, Meta Title Update, Meta Description Update, Alt Text Addition, JSON-LD Injection, Body Content Rewrite, or Internal Link Insertion.

Before & after content

The exact value of the field or content block before the change, and the exact value after. For content rewrites, a word-level diff is shown so you can see precisely what was altered.

Agent

Which of Rankforce’s three agents proposed and applied the change — SEO Optimization Agent, GEO Visibility Agent, or AEO Schema Agent.

Status

The current status of the entry: Applied, Pending Approval, Rejected, Rolled Back, or Failed. Entries that have been rolled back show both the original apply timestamp and the rollback timestamp.

Timestamp

The date and time the change was proposed and, if applicable, the date and time it was applied. All timestamps are shown in your account’s configured timezone.

​
How to view the Audit Log

The Audit Log is accessible from your Rankforce dashboard at any time.
1

Open your dashboard

Log in to Rankforce and select the site you want to review from the site selector at the top of the dashboard.
2

Navigate to the Audit Log

Go to Dashboard → Autopilot → Audit Log. The log opens showing all entries for your site, sorted by most recent first.
3

Filter the entries

Use the filter bar to narrow the log by page URL, change type, agent name, status, or date range. You can combine multiple filters — for example, filtering to all Body Content Rewrite entries applied by the GEO Visibility Agent in the last 30 days.
4

Inspect an entry

Click any log entry to expand it and see the full before-and-after comparison, the agent’s original plain-language reasoning for the change, and the available actions (Rollback, if the change has been applied).
If you want to review all changes applied to a single page, type the page URL into the filter bar. This gives you a full history of every agent action on that page in chronological order — useful when you’re auditing a specific piece of content or troubleshooting an unexpected change.

​
How snapshots work

Before any agent writes a change to your site, Rankforce captures a snapshot of the exact current state of the field or content block being modified. This snapshot is the restore target for rollback — it is what your site returns to if you roll back that entry. What a snapshot captures:
  • The exact string value of the field being changed (meta title, meta description, alt attribute, JSON-LD block, or body content segment)
  • The full page URL and CMS post or page ID
  • The timestamp at the moment of capture, before the write begins
  • The Rankforce plugin connection used to perform the write
Snapshots are stored independently from the live page — they are not affected by subsequent changes to the same page. This means you can roll back a meta title change even if the agent has since proposed and applied a second meta title change on the same page. Each entry’s snapshot reflects the state that existed at the moment that specific change was made.
Snapshots capture field-level state, not full-page HTML. If you make manual changes to a page in WordPress or Framer after Rankforce applies a change, those manual changes are not included in the Rankforce snapshot. Rolling back a Rankforce change will only restore the specific field that Rankforce modified — it will not affect anything you changed manually.

​
How to roll back a change

Rolling back a change restores the before-state snapshot for that specific entry and marks the log entry as Rolled Back. The process takes only a few seconds.
1

Find the entry in the Audit Log

Navigate to Dashboard → Autopilot → Audit Log. Use the filters to locate the specific change you want to revert. You can search by page URL, change type, date, or agent to narrow the list quickly.
2

Open the entry

Click the entry to expand it. Review the before-and-after comparison to confirm this is the change you intend to revert.
3

Click Rollback

Click the Rollback button at the bottom of the expanded entry. A confirmation dialog will appear showing you the before-state value that will be restored.
4

Confirm

Click Confirm Rollback. Rankforce sends the restore instruction to the plugin on your site, which overwrites the current field value with the snapshot. The log entry status updates to Rolled Back and the rollback timestamp is recorded.
5

Verify on your live site

Click the page URL in the log entry to open your live page in a new tab. Confirm the field has been restored to the expected value.
Rollback is irreversible in the sense that it will overwrite what the agent applied. If you roll back a change and then decide you want the agent’s version back, you will need to re-approve the recommendation from the original entry or trigger a new audit to generate a fresh recommendation for that page.

​
Log retention by plan

How long your Audit Log entries are stored depends on your Rankforce plan:
PlanAudit Log retentionSnapshot retention
Starter30 days30 days
Growth6 months6 months
Pro12 months12 months
AgencyUnlimitedUnlimited
Entries older than your plan’s retention period are removed from the log and their snapshots are deleted. If you are on a Starter or Growth plan and want to preserve a longer history, you can export your Audit Log at any time as a CSV from Dashboard → Autopilot → Audit Log → Export.
After an entry’s snapshot is deleted (at the end of your retention period), rollback is no longer available for that entry — the entry itself remains visible in the log as a historical record, but the Rollback button is replaced with a Snapshot Expired label.

​
Frequently asked questions

Not currently — rollback operates at the individual entry level, one change at a time. This is intentional: bulk rollback carries a higher risk of unintended side effects when changes on the same page interact with each other. If you need to revert a large batch of changes, use the URL filter in the Audit Log to work through them page by page.
If the Rankforce plugin is not reachable on your site at the time you attempt a rollback, the rollback will fail and the log entry will show a Rollback Failed status. Reconnect the plugin and try again — the snapshot data is preserved and the rollback will succeed once the plugin is available.
Rolling back a change restores your page to its previous state, which may mean undoing an optimisation. If you find yourself rolling back many changes from a particular agent, consider adjusting the agent’s recommendations from your feedback settings rather than routinely rolling back — this trains the agent to better match your preferences going forward.
Yes — upgrading your plan extends your retention going forward but does not recover entries that were already deleted under your previous plan’s retention policy. If you upgrade from Starter to Pro, entries from the last 12 months will be retained from that point forward, but entries older than 30 days that were already deleted cannot be recovered.