Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ardocs.autonome.in/llms.txt

Use this file to discover all available pages before exploring further.

Actions are available on paid plans.
The Actions page turns diagnostics into an execution queue. It is where analysis becomes work. For catalog-wide readiness work, Actions now summarizes the recurring issue and links directly into the matching view on the Products page. The actual remediation flow in Phase 2 is still manual.

​
What you see first

At the top of the page, Actions summarizes the current queue:
  • Active
  • Quick wins
  • Completed
  • Verified
This gives you a fast sense of how much work is open and how much has already been addressed.

​
Reading an action card

Each action includes:
FieldMeaning
TitleWhat to do, in plain terms
SeverityDeterministic priority based on prompt coverage plus fixed floors for important issue buckets
DifficultyHow much effort is required to fix it
ExecutionWhether it is automatable or manual
StateWhether it is open, in progress, completed, verified, or dismissed
Affected promptsWhich tracked queries this fix will impact
Expected impactWhy this action matters in practice

​
Action categories

CategoryWhat it involves
CatalogAdd or update product metafields, attributes, tags, or taxonomy
ContentRewrite product titles, descriptions, or collection page copy
SchemaAdd or fix JSON-LD structured data on product pages
OutreachPitch products for editorial coverage or third-party reviews
CollectionCreate or restructure collections to match how buyers search

​
Filters and sorting

You can filter the queue by:
  • State
  • Severity
  • Type
  • Difficulty
  • Execution
You can also sort by highest impact, newest, or easiest. This makes it easier to split the queue by owner, urgency, or execution style.

​
Quick wins and backlog

Actions that are both high-leverage and relatively easy are called Quick wins. They appear separately from the broader backlog so teams can move fast on the highest-return work. Everything else stays in the main backlog for ongoing prioritization.

​
Severity levels

SeverityMeaning
CriticalDirectly blocking you from appearing in high-value prompts
HighSignificantly reducing your rank in prompts where you appear
MediumImprovement opportunity with measurable impact
LowMinor polish — worth doing, but not urgent

​
How to use Actions

Start with Quick wins and High severity. These usually represent the best tradeoff between impact and effort. Then open the affected products. Catalog-wide readiness actions include a View affected products shortcut so you can inspect the exact product rows, issue evidence, and Shopify or storefront links before making changes on the Products page. Then work by owner. Catalog and schema fixes often belong to product or engineering, while content and outreach work may belong to marketing or SEO. Use state transitions actively. Move actions through open, in progress, completed, verified, or dismissed so the queue stays trustworthy.
After implementing a batch of actions, use Overview to watch metric movement, Analysis to confirm whether the original gap is shrinking, and Products to validate the exact catalog rows that were affected.