Keystone Documentation

Appearance

Version History ​

Version History is your safety net in Keystone AI SEO. Every change made to a product or article — whether by an automated workflow or a manual edit — is recorded with full details. This means you can always see what changed, when it changed, and why, and you can restore any previous version if something doesn't look right.

Where to Find Version History ​

Version History lives at the bottom of each item's editor page in Manual Optimization. When you open a product or article for editing, scroll down past the editable fields and SEO preview to find the Version History section.

Each product and article has its own independent version history.

What Gets Tracked ​

Every time a field is updated and saved — either by you or by a workflow — the following information is recorded:

Field changed ​

Which SEO field was modified. This could be any of the available fields: title, description/content, meta title, meta description, FAQ, or alt text. Each field change is tracked individually, so if a workflow updates both the meta title and meta description in one run, you'll see two separate entries.

Original value ​

The content that was in the field before the change. This is stored in full so you can compare the old and new versions side by side.

New value ​

The content that replaced the original. This is what's currently live on your store (or was live at the time, if a subsequent change has since been made).

Date and time ​

The exact timestamp of when the change was saved. This helps you trace when specific optimizations happened and correlate them with search performance changes.

Source ​

How the change was made:

  • Workflow — the change was made by an automated workflow. The entry includes a link to the specific workflow that made the change, so you can see which workflow was responsible and review its full details.
  • Manual — the change was made by you (or someone on your team) through the Manual Optimization editor.

Reading the Version History ​

The version history is displayed as a list of entries in reverse chronological order — the most recent change appears at the top. Each entry is a self-contained record showing all the information described above.

For fields with longer content (like product descriptions or article bodies), the original and new values may be truncated in the list view. You can expand them to see the full content.

Restoring a Previous Version ​

If an optimization didn't produce the results you expected — or if you simply prefer an earlier version of a field — you can restore it directly from the version history.

How to restore ​

  1. Open the product or article in Manual Optimization
  2. Scroll down to the Version History section
  3. Find the entry with the version you want to restore
  4. Click the restore action on that entry
  5. The field reverts to the previous value
  6. Click Save to push the restoration to your Shopify store

The restoration itself is also recorded as a new entry in the version history. This means you always have a complete audit trail — even of undo actions.

What you can restore ​

You can restore any individual field independently. For example, if a workflow updated both the meta title and meta description but you only want to revert the meta title, you can do that without affecting the meta description.

Common Scenarios ​

Reviewing workflow results ​

After a workflow completes, open a few of the affected products or articles and check their version history. You'll see entries for each field the workflow optimized, with the original and new values side by side. This is the fastest way to audit what the AI changed.

Undoing an AI optimization ​

If the AI generated a product title that doesn't match your brand voice, find the title change in version history and restore the previous version. Your original title goes back to the Shopify store, and the version history records the restoration.

Tracking changes over time ​

For products or articles that have been through multiple workflow cycles, the version history provides a complete timeline of SEO evolution. You can see how the content has changed over months — which is useful for understanding whether ongoing optimization is improving your search performance.

Identifying which workflow made a change ​

Each workflow-generated entry links back to the source workflow. If you notice an unexpected change on a product, check the version history to see which workflow was responsible, then review that workflow's configuration to understand why the change was made.

Tips ​

  • Check version history after your first workflow run. This gives you confidence in the AI's output and helps you decide if you need to adjust your workflow configuration.

  • Use restore liberally. There's no penalty for restoring a previous version. If something doesn't look right, restore it and move on.

  • Compare old and new values before restoring. Sometimes the AI's version is better than the original, even if it looks different at first glance. Read both versions carefully before deciding.

  • Version history is cumulative. It grows over time as more changes are made. For items that go through many optimization cycles, the history becomes a valuable record of how your SEO content has evolved.