Spek Documentation

Start with What is Spek for the product's purpose and boundaries, then follow Quick start for the first workspace and app workflow. The App Store Connect guide covers Apple's API-key setup in detail. Once the app is connected, Agent setup explains market and competitor choices, and Review and apply proposals explains how research becomes a draft. You can return to individual articles as a task arises rather than reading every guide before beginning. Keep the selected store in view when a chapter describes an Apple-specific feature.

Read the proposal-review, Editor and Publishing guides together. A metadata proposal is something to evaluate, an accepted proposal updates a Spek draft, and publishing is a separate authorized provider action. The store's review and public release can introduce further stages after a successful write. These guides explain the user-facing controls and the prerequisites for the documented App Store workflow. Understanding those stages helps you tell a teammate whether text is only prepared, has reached the provider or is actually visible on the store.

Markets explains storefront scope, the keyword guide defines the supporting estimates shown with proposals, and Competitors explains how the tracked list relates to local observations. The glossary gives concise definitions of rank, visibility, market and other terms. Read those definitions before comparing reports from different countries or tools. Spek's search metrics do not measure installs, revenue or conversion, so use your own store and business analytics when the decision depends on those outcomes.

Check the selected app and workspace, your role, completion of setup and the relevant provider prerequisites. Availability explains which surfaces have additional conditions, including App Store eligibility. A product illustration does not establish that every app can use the same control. If the article and your situation still disagree, use the support guide to report the page, expected action and visible state. Include useful context without sending private store credentials, passwords or unrelated customer information.

Workspace and members explains team boundaries and roles, Integrations covers the connected account controls, and Plans and billing describes workspace subscriptions and credit behavior. These are separate responsibilities: a billing change does not act as a store-key revocation, and access to one workspace does not automatically grant access to another. Use the guide that matches the intended action and verify the selected workspace first, especially when you manage several clients or app portfolios.

Yes. Use the relevant workflow article as a reference, keep its platform and permission boundaries intact, and add your team's own responsibilities for product accuracy, language review and approval. Distinguish research estimates from observed rankings and separate draft preparation from store publication. Link to the current official source so colleagues can check the underlying guidance later. For a compact product overview or material intended for an assistant to read, the official AI information page and its plain-text editions provide maintained facts and source links.