The 28-character rewrite: a subtitle change that doubled tap-through for a flatlined app

Subtitles are the most underrated 30 characters in App Store Optimization. They’re indexed for search at almost the same weight as the title. They’re the line directly under the app name on every search results card. And almost every indie dev I know spends 10× more time on their app icon than on this single sentence.

This is a case study about an app where rewriting the subtitle — and only the subtitle — moved tap-through rate noticeably in two weeks.

The setup

The app was a niche productivity tool. Mature product, decent reviews, growing user base, but the search-impressions-to-installs ratio had been flat for months. Apple Search Ads campaigns were working fine, but the organic conversion line refused to move.

The hypothesis: people were seeing the app in search results and scrolling past. The icon wasn’t the problem (we did a quick sanity-check with five strangers and got “this looks polished” responses across the board). The screenshots weren’t the problem either — you don’t see them on the search results page.

That left the title, subtitle, rating count, and rating average. Title and rating are sticky. The subtitle was the only thing we could change immediately.

The before

Original subtitle (paraphrased): “Get more done. Stay organized.”

Two clauses, both generic, both literally describing what every app in the category claims to do. Zero unique surface area. Nothing that names a specific job or a specific user.

You could swap this subtitle onto any of the top 30 results for “productivity app” and it would still fit. That’s the diagnostic.

The framework we used to rewrite

Three rules:

1. Name a specific job, not a category

“Productivity” is a category. “Organize your day” is a category. “Plan your week the night before” is a job. The more specific you can be, the better the line works on both the algorithm and the human.

2. Use words you don’t already have in the title or keywords

If your title is “Foo — Habit Tracker”, your subtitle should not include “habit” or “tracker”. The App Store search index already gives you credit for them. The subtitle’s 30 characters are most valuable when they expand your keyword surface, not echo it.

3. Make it readable as a sentence fragment, not a feature list

Subtitles with & or · separators look fine in mockups, terrible in the actual search results card. A single readable phrase outperforms a comma-separated feature list almost every time.

The after

The new subtitle named the specific use case the developer wanted to compete on (a workflow with a defined start and end — not a vague “be more productive” pitch). It introduced 4 new keyword stems that weren’t already in the title. And it read as one sentence, not a list.

I won’t quote the exact line — the developer is still ranking on it and doesn’t want it copied — but the shape was something like:

“Plan tomorrow tonight in 5 minutes.”

Compare to the original:

“Get more done. Stay organized.”

The new line tells you:

• When to use the app (tonight).
• What it produces (a plan for tomorrow).
• How long it takes (5 minutes).

The old line tells you nothing. The new one is doing the work of a small, well-aimed ad.

What we measured

We didn’t run a proper A/B test — Apple’s Product Page Optimization only tests visual assets, not text fields. What we did instead:

• Tracked impressions, product page views, and installs in App Store Connect daily for 2 weeks before the change and 2 weeks after.
• Held everything else constant (no new ads, no new screenshots, no version push).
• Normalized for day-of-week (Mondays are different from Saturdays in this category).

After 14 days, the search-result tap-through rate (impressions → product page views) was up ~85%. Install conversion held steady, so the lift propagated straight to daily organic installs.

Was 100% of that the subtitle? Probably not. There’s always seasonality, competitor noise, algorithm drift. But the magnitude and timing both line up with the change. And it’s the only thing we touched.

How to do this for your app this afternoon

A 30-minute exercise:

1. Open App Store Connect. Copy your current subtitle into a doc.
2. Below it, write three rewrites that follow the three rules above. Name a job, avoid title duplicates, read as a sentence.
3. Read all three out loud in a normal voice. The one that doesn’t make you feel weird saying out loud is the one you ship.
4. Push the new subtitle (no version required for metadata-only changes).
5. Snapshot your impressions/views/installs in ASC the day you push. Don’t look again for 14 days.
6. After 14 days, compare against the 14 days before. Day-of-week match if you can.

What this case study isn’t

It isn’t proof that a subtitle rewrite always doubles tap-through. It’s one app, one rewrite, one category. The principle that generalizes is:

Treat your subtitle as 30 characters of cheap, free-to-edit ad copy, not as a tagline.

Rewrite it the same way you’d rewrite a paid ad headline. Then measure properly and let the next two weeks tell you what worked.

---

Related: how we took a habit tracker from rank 80 to rank 4 using a similar set of metadata moves, and the three numbers worth tracking when you measure the result.

If you want a workspace that lets you edit subtitles across every locale at once and push to App Store Connect in one click, Asomium is built for that. 3-day free trial, no card required.