Skip to documentation
SmartLinks Help Center
Step-by-step product guides Read as Markdown ↗
Free to read. Private to operate. These guides never display account data or keys. Using a feature requires your own account, permissions and applicable plan. YOUR_API_KEY is only a placeholder.

ASO and localized store listings

The ASO Wizard prepares store metadata and can publish reviewed content. Research, generated files and store publication are separate stages.

Before you start

Connect the correct Apple/Google credential profile, verify app identifiers and check AI/plan limits. Obtain permission to change the listing before publishing.

Step by step: prepare and generate

  1. Open ASO and review the wizard's current step.
  2. Choose the Publishing Target for each platform. Refresh the target list and verify the selected default or custom listing. Options marked Soon are not available.
  3. Enter the app's actual capabilities in App Content. Use Auto-fill from App Data if appropriate, then correct the imported content.
  4. Prepare seed/tracked keywords. Use Choose iOS Keywords or Choose Android Keywords and review suggestions before adding them.
  5. Verify Technical Details, the iOS version where required, privacy-policy URL and intended locales.
  6. Use Save Draft before starting a job.
  7. Start Run Research Only, Generate Files or the appropriate combined action. A full sequence can include publishing; inspect its purpose before running it.
  8. Open Generated Files and review each locale. Use Structure or JSON mode; validate and save your corrections.

Step by step: publish and verify

  1. Confirm the app, store target, version and selected locales again.
  2. Publish one reviewed locale first when practical. Publish All and Publish Unpublished can write many locales to a store.
  3. Inspect execution history and logs. For partial failures, use Retry failed languages only after fixing the cause.
  4. Read back the actual metadata in App Store Connect or Google Play Console. Store review/release availability is a separate step from uploading metadata.

Advanced workflows

Custom targets must be selected explicitly; creating a target can change provider state. Full-cycle API automation is plan-gated. Use API Explorer to inspect its current contract and avoid accidentally triggering publishing while researching.

Confirm it worked

The reviewed text exists in the intended provider target and locale. A generated file or successful research step is not publication proof.

Troubleshooting

Check credential permissions, target IDs, locale support and character limits. AI-generated claims, keywords and translations need human review. Do not overwrite a partially published file blindly; use the remaining-language option when appropriate.

Related: Competitors, Screenshots, Metadata.

Browse all product guides → · SDK installation guides