Preview approve execute rollback

Every change in AEO Enhancer follows the same workflow:

1. Preview
2. Approve
3. Execute
4. Rollback

This workflow is designed to be trust critical. You always know what will happen before it happens, and you can reverse it if needed.

Step 1 Preview

A preview is the exact artifact that will be applied during execution.

Depending on task type, a preview can be:

• A schema block that will be added or updated
• A blog draft that will be created in Shopify
• A product or collection description in HTML
• An FAQ block in structured format
• An llms.txt update

What you should check during preview:

• The preview matches the intended query target
• The output is accurate and reflects your products and policies
• Tone matches your brand voice
• Any claims are compliant for your industry
• The format is correct for where it will be stored and rendered

If the preview is not good enough, do not approve it.

Step 2 Approve

Approval is an explicit action that authorizes execution of the preview.

Approval means:

• You reviewed the preview
• You accept the changes exactly as shown
• You are ready for the app to apply them

Approval does not mean:

• Rankings are guaranteed to improve
• The app will change anything outside the preview

Some stores may have extra confirmations if regulated industry mode is enabled.

Step 3 Execute

Execution applies the approved preview to your store.

Execution can include:

• Creating draft resources in Shopify, such as draft blog articles
• Writing draft metafields for previewed content
• Writing approved metafields used for storefront rendering
• Publishing content only when the task is executed and designed to publish
• Recording ids and previous values needed for rollback
• Logging timeline events for auditability

Execution is designed to be idempotent. If the same execution is triggered again, it should not create duplicates or drift the output.

If execution fails, you will see an error code and the task timeline will show where it stopped.

Step 4 Rollback

Rollback reverses the effects of execution.

Rollback can include:

• Restoring previous metafield values
• Removing draft resources created during execution
• Unpublishing content that was published by execution when applicable

Rollback exists so you can safely test improvements and revert if they cause unexpected issues.

Practical example

Here is an example flow for an Optimize Result blog draft:

1. Preview shows the full blog content and metadata
2. You approve the preview
3. Execute creates a Shopify article, writes approved blog content storage, and publishes the article if that flow is enabled
4. Rollback can unpublish the article if published by execution, restore previous approved values, and delete the created article

Best practices

• Treat previews like final edit before publishing
• Approve only when content is accurate and compliant
• Use reset approval when you want revisions
• Avoid manual edits to app created draft resources if you want rollback to work cleanly
• Render only approved content on the storefront

Common pitfalls

Approving the wrong version

If multiple preview versions exist, confirm the correct one is active and approved before executing.

Expecting draft content to render live

Draft content is for review. Your storefront should render approved outputs only.

Manual deletion breaks rollback

If you manually delete a Shopify resource created by execution, rollback may not be able to remove it cleanly. Approved metafield rollback may still be possible.

Related pages

• Core concepts then Approval first
• Core concepts then Tasks
• Features then Optimize Result
• Troubleshooting then Common errors