Skip to content

The Watchtower Dashboard

The Watchtower is a project’s home screen. It opens by default when you enter a project and summarizes the latest audit for the selected storefront and locale: an overall readiness score, a per-engine breakdown, and the banners that tell you when something needs your attention.

The Watchtower is where you decide what to do next. Rather than opening each engine one by one, you read the top-line score and the per-engine grid, spot the weakest areas, and jump straight to them. It reflects the currently selected storefront and language from the top bar, so switching stores or locales re-scopes what you see.

At the top, a hero card shows your Overall ASO Readiness score with a band label, a headline, and a short narrative summary. Below the headline are the top few recommended actions or key issues pulled from the audit. Use this as the executive summary — if you only look at one thing, look here.

Under the hero, each audit engine gets its own scorecard (keywords, store text, screenshots, icon, competitors, sentiment, AI discoverability, and so on). Scan the grid for the lowest scores — those are where the audit found the most room to improve. Click into a scorecard, or use the sidebar, to open that engine’s full analysis.

If an engine is included in the audit but not in your plan, its tile shows an upgrade affordance rather than a score. If an audit ran only partially, engines that didn’t complete are called out instead of showing a number.

Between the hero and the engine grid, a Conversion KPIs section teases store performance data with a Performance → button to the full analytics. If the store isn’t connected yet, this section prompts you to connect App Store Connect or Google Play Console first. Live conversion metrics are being rolled out, so this area may read as coming soon depending on your project.

The Watchtower surfaces status banners above the scores when action is needed:

  • Credential errors — if App Store Connect or Google Play Console access has a permission problem, a banner explains it. Keyless Google Play links offer a Re-verify action.
  • Missing App Store vendor number — a banner prompts you to add it so reporting data can be pulled.
  • Review your app brief — a control to open the Anchored App Brief, the app description the audit reasons against. Keep it accurate for better recommendations.
  • Upgrade prompt — after your first audit, free-tier projects see a prompt to unlock full audit depth, automated audits, more apps and regions, and competitor tracking. It’s dismissible.

A new project has no scores until you run an audit:

  • If the store isn’t connected, the Watchtower shows a “{store} Not Connected” card with a Connect {store} button.
  • If the store is connected but no audit has run, it shows a No Audit Available card with a Run Full Audit button.

To re-run an audit on a project that already has one, use Run Fresh Audit from the audit-actions menu in the top-right of the top bar.

  • Read the overall score, then open the weakest engines from the grid or the sidebar.
  • Clear any credential or vendor-number banners so audits and analytics have the data they need — see App Store linking and Google Play linking.
  • Compare the scored view against your actual store listing in the Live Listing viewer.