FAQ

High-frequency questions about StorePilot

This page is the shared answer layer for search visitors and AI retrieval systems, with direct answers about workflow, domain architecture, and bilingual publishing.

Who is StorePilot designed for?

StorePilot is built for app teams that need one workflow for positioning, listing copy, screenshot narrative, billing-aware iteration, and multilingual review.

Does StorePilot only generate copy?

No. The product is designed to keep metadata, screenshot direction, project state, quotas, and review context inside one workspace.

Can we use StorePilot for Chinese and English launches together?

Yes. The workflow and public site structure are set up to support stable Chinese and English content without mixing both languages at the same URL.

What makes StorePilot different from manual ASO documents?

Manual docs can store content, but they rarely capture screenshot structure, regenerate control, approval state, and billing entitlements in one operating surface.

Why separate public, app, and admin domains?

The split keeps SEO content on the main domain, product flows on the app domain, and internal operations isolated behind a noindex admin domain.

Knowledge paths

Move from direct answers into the actual workflow pages.

If the FAQ already answered the high-level question, use one of these guided paths to continue into definitions, workflows, and case studies.

Guides

6 pages

Operational articles for launch planning, review, and asset handoff.

Compare

4 pages

Decision pages that explain the gap between manual ops and structured workflows.

Glossary

6 pages

Entity definitions and ASO vocabulary written for both teams and AI retrieval systems.

Case studies

3 pages

Narrative case studies with concrete workflow, decisions, and outcomes.