Inside the Audit (06/12): How Your Title, Subtitle, and Description Actually Get Scored

Apptonomy is an ASO intelligence and execution platform. Paste an App Store or Google Play URL, and the platform runs a full audit across multiple specialized engines, delivering scored findings and prioritized recommendations in minutes. For the full picture of how an audit works, read What You Get From an Apptonomy Audit.

The Orchestrator

Behind every audit is the Audit Engine, an orchestrator that spins up each specialized subengine in parallel and synthesizes their findings into a single unified report with an ASO Readiness Score (0-100). The current subengines:

Keyword Engine
Store Text Engine
Screenshot Engine
Icon Engine
Sentiment Engine
Competitor Discovery Engine
Policy Checker
Content Engine
AI Discovery Engine
Search Term Engine
Intent Engine

This post covers the Store Text Engine and what happens when it analyzes your listing’s text metadata.

The ASO Problem: Store Text Is Where Most Listings Fail Quietly

Your title, subtitle, and description are the three fields you control most directly in the app stores. They are also where significant ranking and conversion potential goes unrealized. Apps we’ve audited typically have 3-5 high-value keyword clusters completely absent from their store text.

The pattern we see across hundreds of client accounts after 12+ years of ASO work: teams write their store text once at launch, revisit it after a major update (maybe), and otherwise treat it as static content. The result is predictable. Titles that waste characters on the brand name alone. Subtitles that duplicate the title’s keywords instead of expanding coverage. Descriptions that read like feature changelogs with no keyword strategy and no conversion structure. If you wrote your store text at launch and haven’t revisited it strategically since, you’re almost certainly leaving ranking potential unrealized, and you have no way to quantify how much.

Each field has different character limits, different rules for how the store uses them in search, and different weight in the store’s ranking algorithm. App Store indexes title, subtitle, and description for search. Google Play indexes all three fields too, but weights them differently. On either platform, how you distribute keywords across these fields directly affects which search queries surface your app and how many of those impressions convert to installs.

The challenge compounds at scale. Even for a developer with 3-5 apps across both platforms, that’s 18-30 text fields to keep optimized. An agency managing 30 client apps across iOS and Android is looking at 180 text fields, each with its own keyword context, competitor set, and platform-specific rules. Now factor in localization: the App Store and Google Play support 88 languages across roughly 200 regions. A single app localized into even 15 markets multiplies those 6 text fields into 90, each requiring local keyword research and culturally appropriate copy. Across a 30-app portfolio, the number of text fields that need optimization is in the thousands. No team can maintain that at high quality by hand. Doing it partially means leaving ranking improvements unrealized. For analysis of localized store text across multiple markets and languages, the L11n Analysis Engine handles per-locale keyword clustering and culturally adapted copy evaluation; see that post in this series.

Our position is direct: store text optimization requires field-level analysis with keyword intelligence baked into every recommendation. Checking whether a title “looks good” or a description “reads well” tells you almost nothing about whether those fields are actually working for discoverability and conversion. You need to know which keyword clusters each field covers, which high-value clusters are missing entirely, and how the three fields work together as a system.

That is what the Store Text Engine does.

Under the Hood

The Store Text Engine runs a multi-phase pipeline: semantic preprocessing, parallel per-field analysis (title, subtitle/short description, description), cross-field scoring, and factual grounding. Here is what each phase produces.

Semantic Keyword Clustering

The problem: You have a list of target keywords from the Keyword Engine. Knowing which keywords to target is step one. Knowing how to organize them across your three text fields, by user intent, is the part that separates good ASO from mediocre ASO.

How the engine handles it: Before analyzing any individual field, the Store Text Engine runs a semantic preprocessing step. It takes the full keyword set (sourced from the Keyword Engine’s analysis of your app and competitors; see that post for the full breakdown), with volume, difficulty, rank position, trend direction, and branded/non-branded classification for each term, and groups them into 3 to 10 intent-based clusters. Each cluster represents a distinct theme users search for. The engine then maps which clusters are already represented in each field (title, subtitle, description) and which are missing.

Cluster strength gets rated as strong, moderate, weak, or opportunity based on current ranking signals, search volume, and metadata presence. An “opportunity” cluster is the most actionable: high volume, low difficulty, and your app currently has no ranking presence for those terms.

What you get: A semantic cluster map showing every keyword grouped by intent, with per-cluster strength ratings. Per-field coverage analysis showing which clusters appear in your title, subtitle, and description. Specific recommendations per field indicating which high-priority clusters to add and which keywords to use.

Title Analysis

The problem: You have 30 characters. On both App Store and Play Store, the title carries the highest keyword weight of any text field. Every wasted character is a missed ranking opportunity.

How the engine handles it: The engine evaluates your title against two dimensions. First, a field optimization score (0-100) measuring keyword coverage, character utilization, and alignment with high-priority semantic clusters. Second, a content quality score (0-100) assessing clarity, brand representation, and conversion appeal.

The analysis is informed by the semantic cluster context from the preprocessing step. If your title only represents one cluster and three high-volume clusters are absent, that gets surfaced with specific recommendations for which keywords to incorporate.

What you get: Two scores (field optimization and content quality) with justification text explaining the reasoning. A set of recommendations specific to the title field. Three alternative title rewrites, each following a different strategy: conservative (minor adjustments preserving current structure), keyword-optimized (maximum keyword coverage within the character limit), and creative (a fresh approach emphasizing conversion or differentiation). Each alternative includes commentary on why that approach was chosen. For a meditation app currently titled “Calm Mind,” the conservative rewrite might become “Calm Mind: Daily Meditation,” the keyword-optimized version “Meditation & Sleep Sounds - Calm,” and the creative approach “Calm Mind - Breathe, Sleep, Focus.”

Subtitle / Short Description Analysis

The problem: The App Store subtitle (30 characters) and Google Play short description (80 characters) serve a dual role: they are indexed for search and they are visible to users browsing the store. On App Store, title and subtitle are cross-indexed (Apple treats keywords in both fields as a single combined pool for search), meaning keyword duplication between them is wasted space. On Google Play, the short description has secondary search weight but more room for messaging.

How the engine handles it: The analysis mirrors the title workflow but with platform-specific adjustments. For App Store, the engine checks whether subtitle keywords duplicate title keywords and penalizes redundancy. It also evaluates combined title-plus-subtitle cluster coverage to assess whether the two fields together cover the highest-priority intent themes.

For Google Play, the 80-character limit allows more room, and the engine weights conversion-oriented messaging more heavily alongside keyword placement.

What you get: Field optimization and content quality scores (0-100 each). Recommendations addressing keyword overlap (App Store) or messaging gaps (Play Store). Three alternative rewrites per the same conservative / keyword-optimized / creative framework.

Description Analysis

The problem: You have 4,000 characters. Both stores index the description for search. The first three lines are visible before the user taps “more,” making them critical for conversion. Most descriptions either over-stuff keywords (hurting readability) or ignore keywords entirely (hurting discoverability).

How the engine handles it: The engine analyzes keyword density against the semantic clusters, checking which clusters are sufficiently represented and which are under-mentioned. It evaluates the description’s overall structure, starting with opening strength: the first three visible lines before the “more” tap carry outsized conversion weight, and the engine scores whether those lines communicate the app’s core value proposition or waste space on generic copy. Feature coverage is assessed by whether the description addresses the primary use cases users search for. Social proof and call-to-action presence are checked against store-specific conversion patterns.

The engine differentiates natural keyword integration from keyword stuffing by analyzing cluster mention frequency relative to description length and checking whether keyword appearances are distributed across paragraphs or concentrated in a single block. A cluster mentioned eight times in one paragraph signals stuffing; the same frequency spread across the full description signals natural usage.

Platform-specific notes matter here too. On App Store, descriptions need to balance keyword optimization with conversion copy. On Google Play, natural keyword usage is weighted over keyword density. The analysis flags any high-priority cluster that appears zero or one time across 4,000 characters of description.

What you get: Field optimization and content quality scores (0-100). Cluster mention frequency analysis showing exactly how many times each semantic cluster is referenced. Recommendations targeting under-represented clusters with specific keywords to weave in. Three alternative description openings (conservative, keyword-optimized, creative) with commentary.

Cross-Field Scoring

The problem: Optimizing each field in isolation misses the bigger picture. Your title, subtitle, and description need to work as a coordinated system. Keyword distribution, messaging consistency, and character allocation across all three fields determine your overall store text effectiveness.

How the engine handles it: After all three fields are analyzed individually, the engine runs a cross-field analysis. It computes four aggregate scores:

Character utilization score (0-100): Measures how effectively you use the available character space. The engine checks each field’s utilization against thresholds and flags fields that are critically underused.
Field optimization score (0-100): Weighted average of per-field optimization scores. Title gets the highest weight (40%), with subtitle and description splitting the remainder based on platform.
Content quality score (0-100): Average quality across all fields.
Cross-field score (0-100, App Store only): Evaluates keyword distribution and messaging consistency across title and subtitle specifically, since those fields are cross-indexed.

These four scores combine into a single overall score (0-100) with a letter grade (A through F).

What you get: An overall optimization score and letter grade. Character utilization status (sufficient, needs more content, or too short). A list of cross-field opportunities, each typed as keyword distribution, messaging consistency, cross-reference, or character reallocation, with an impact score (0-100) and a specific suggested action. Key insights summarizing the most important findings. Priority actions ordered by estimated impact. Across a multi-app portfolio, these scores surface which apps and markets need attention first: focus optimization effort where the letter grades are lowest and the ranking gains are largest.

Factual Grounding

Most ASO tools analyze keywords and rankings but do not audit the factual accuracy of claims in your store text.

The problem: Store descriptions accumulate claims over time. “#1 fitness app.” “Award-winning.” “4.9 stars.” Some of these were true once. Some were never verifiable. Unsubstantiated claims hurt credibility with users and can trigger store policy violations. AI assistants like Siri and ChatGPT are increasingly recommending apps, and they cross-check your claims against real data. A description claiming “4.9 stars” when the current rating is 4.3 gets noticed, both by users and by the AI systems deciding which apps to recommend.

How the engine handles it: The factual grounding pipeline runs four steps. First, an AI extraction pass identifies every factual claim in your store text, categorizing each as a metric, award, superlative, feature, health/financial claim, comparison, or freshness indicator. Second, a rule-based verification step cross-references verifiable claims against actual app data: your current star rating, review count, download count, pricing, last update date. Third, unverified claims go through AI-powered classification that sorts them as unverifiable, misleading, stale, inconsistent, or risky. Fourth, a deterministic scoring pass computes an overall credibility score (0-100). High-severity flags (like a claimed star rating that contradicts your actual rating) carry steep penalties.

What you get: A credibility score (0-100). A list of flagged claims, each with the claim text, location (which field it appears in), issue type, severity level (high/medium/low), and a specific suggested fix. A list of verified claims that demonstrate credibility. Breakdowns by issue type and severity so you can triage fixes.

Bringing It Together

Store text optimization is a coordination problem across three fields, two platforms, and dozens of keyword targets. The Store Text Engine treats it as exactly that: a system-level analysis where semantic keyword clustering informs per-field scoring, per-field findings feed into cross-field evaluation, and factual grounding catches the trust issues that manual review rarely surfaces.

Running this analysis once is valuable. Running it on every audit, across every app in a portfolio, with keyword intelligence refreshed from the Keyword Engine each time, is where the compounding advantage builds. The combination of ASO domain expertise encoded in the analysis prompts, real keyword data driving the semantic clustering, platform-specific indexation awareness, and cross-validated AI analysis automates the mechanical work that would take an experienced ASO professional 3-5 hours to assemble per app: keyword-to-field mapping, cross-field coverage analysis, character optimization, and claim verification. The engine handles the systematic grunt work. The professional focuses on strategic judgment the engine cannot replace.

Each recommendation comes with specific rewrite suggestions you can review side-by-side with your current text. All changes are presented for team review before anything is applied to a store listing. When you’re ready to act, updates can be drafted, translated across markets, and published directly to App Store Connect or Google Play Console within the platform.

Run a free Quick Audit now Paste your App Store or Google Play URL at apptonomy.ai and see what the Store Text Engine finds.