Tasks

A task is a single, trackable unit of work in AEO Enhancer.

Examples of tasks include:

• Adding or updating schema for a specific page type
• Generating an Optimize Result output like a blog draft or product description
• Creating an llms.txt update
• Running a follow up improvement when a query score drops

Every task is designed to be:

• Previewed before execution
• Approved by a human
• Auditable with a timeline
• Reversible with rollback when applicable

Why tasks exist

Tasks make improvements safe and measurable.

Without tasks, changes become hard to review, hard to attribute, and hard to undo. With tasks, you can always answer:

• What changed
• Why it changed
• Who approved it
• When it was executed
• How to roll it back

The task lifecycle

A task moves through clear states.

Typical flow:

1. Needs review
   A preview exists and is ready for review

2. Approved
   You approved the preview and the task is ready to execute

3. Executed and completed
   The app applied the change successfully

4. Rolled back
   The app reverted the change back to the previous state

Some tasks can also be rejected or reset back to needs review.

Task types

AEO Enhancer supports different task types. The most common categories are:

Schema tasks

These improve structured understanding of your store and pages. They are usually low risk, highly reviewable, and easy to validate.

Optimize Result tasks

These generate publishable content assets tied to a specific query target, such as:

• Blog drafts
• Product descriptions
• Collection descriptions
• FAQ blocks

Outputs are created as drafts first and then written to approved locations during execution.

Operational tasks

Examples:

• llms.txt refresh tasks
• Follow up tasks created after weekly retests detect a score drop
• Competitor intelligence refresh tasks

What a task contains

At minimum, a task includes:

• Target query and target surface
  For example a query target representing what the task is meant to improve

• Preview content
  The exact content or changes you will review

• Approval data
  Who approved and when

• Execution details
  What happened during execution including any ids created in Shopify

• Rollback data
  Enough information to restore the previous state

• Timeline and audit log
  An append only record of the important events for that task

Preview versions and diffs

A task can have multiple preview versions.

This helps when:

• You want to iterate on the output before approval
• You want to compare two versions of a schema block
• You want to refine content tone using brand voice settings

Use the version list and diff tools to compare, then approve the exact version you want executed.

Where tasks show up

You will interact with tasks in two main places:

• Dashboard actions
  Buttons like Fix Now or Optimize Result create or reuse tasks and open the task modal

• Task inbox
  A queue where you can filter, review, and bulk approve or reject tasks

Best practices

• Review previews like you are doing a final edit before publishing
• Approve only when the output meets your standards
• Use reset approval if you want a revision
• Use rollback when a change causes unexpected results

Related pages

• Core concepts then Approval first
• Workflows then Preview approve execute rollback
• Features then Optimize Result
• Troubleshooting then Common errors
• Glossary then Terms