Approval first

Approval first means nothing is applied to your store until you review a preview and explicitly approve it.

This is the core safety contract of AEO Enhancer.

Why this exists

AEO Enhancer can generate schema changes and content outputs quickly, but speed is not worth risking unintended storefront changes. Approval first is designed to ensure:

You always see the exact change before it is applied
Changes are tied to a specific query and task
Every change is auditable
Every change can be rolled back

The approval first contract

A task must meet these rules:

A preview must exist before you can approve
Only an approved preview can be executed
Execution is locked to the approved preview
Rollback is available for executed tasks
Logs must capture what happened and when

If any of these rules cannot be met, the task should not execute.

What you review in a preview

A preview is not a promise like we will improve your SEO.

A preview is a concrete artifact that shows what will be written or changed, such as:

A schema JSON LD block that will be added or updated
A blog draft that will be created in Shopify
A product description HTML draft that will be stored in a draft location
An FAQ block in structured format

Previews are meant to be publishable or directly applicable with minimal edits.

What approval means

Approving a task means:

You reviewed the preview content
You understand what will be created or changed
You authorize the app to execute that exact preview

Approval does not mean:

The result is guaranteed to improve rankings
The app will change anything beyond what the preview shows

How execution is kept locked to the preview

AEO Enhancer uses a preview integrity lock so the executed content matches what you approved.

In practice this means:

The preview content is stored at creation time
Execution checks that the preview matches the approved version
If the preview does not match, execution is blocked

This prevents accidental or malicious changes between approval and execution.

Regulated or sensitive industries

If regulated industry mode is enabled for a merchant, tasks can require additional confirmation steps before execution.

This is intended for stores in categories where claims, compliance language, or policy risk are higher.

Common scenarios

You approve, then want to adjust the content

Reset the task back to needs review, generate a new preview, and approve the updated preview.

Do not edit live storefront content outside the approval flow if you want auditability and rollback.

You approved the wrong version

Use the preview versions panel to set the correct version active, then approve the correct version.

If the task is already approved, reset approval and re approve the right version.

You want auto apply

Approval first is the default. Auto apply should only be enabled later for low risk changes and only after you are comfortable with the workflow.

Core concepts then Tasks
Workflows then Preview approve execute rollback
Troubleshooting then Common errors