Apple Search Ads or ASO: What Indie Devs Should Do First

Most indie apps spend on Apple Search Ads before they have fixed their App Store listing.

The order is wrong. ASO before ASA, every time, with one exception spelled out below. The reason is structural, not philosophical. Paying Apple to send buyers to a broken listing is the most expensive way to launch an indie app. Most indie devs do it anyway, because ads feel like progress and ASO feels like homework.

The order of operations

Two surfaces. One algorithm.

Apple Search Ads delivers a paid placement at the top of App Store search for a keyword you bid on. Apple charges per tap. The buyer who taps then lands on your App Store product page. That product page is what your ASO work optimises. The buyer decides to install or not based on the product page, not based on the ad.

The math falls out from there. If your product page converts taps to installs at three percent, every euro of ad spend produces a third of the installs it would produce at nine percent. The cost per install on ASA is dominated by your product-page conversion rate, which is set by your screenshots, your subtitle, and your first 170 characters of description. None of those are ad work. All of those are ASO.

Fix the listing first. Pay Apple second.

Why ASA on a broken listing burns money

Three things conspire to make this worse than indie devs expect.

First, ASA bidding is auction-based. Apple shows your ad to a buyer searching the keyword you bid on. If your product page does not convert, Apple still charges you for the tap. The buyer leaves. The next buyer in the auction sees a different ad. Your cost per install climbs every day the listing stays broken.

Second, organic ASA-driven traffic and organic search-driven traffic share a product page. The same broken screenshots suppress both. Fixing the listing lifts both at once. Running ASA first means you have spent the budget twice. Once on the broken page, again on the fixed page.

Third, Apple Search Ads exposes a free keyword tool to anyone with an ASA account. The tool surfaces popularity scores from 5 to 99 for any keyword you type. That data is the input to ASO. Most indie devs use the tool to bid on keywords. The higher-leverage move is to use the tool to pick the anchor keyword that sits in the first five characters of the title. The ASA tool is more useful for free ASO than for paid ASA on day one.

The €500 audit-before-spend framework

Before any indie dev gives Apple a euro on ASA, the audit:

1. Title check. Anchor keyword in the first five characters. Brand after. If the brand sits at the start, the listing is broken before ASA can save it.
2. Subtitle check. Second-best keyword plus a four-word benefit. Most indie subtitles are taglines. Apple ranks the subtitle. Use it as a ranking field.
3. 100-character keyword field. Singular nouns, zero overlap with title or subtitle. No stop words. No plurals when the singular ranks already.
4. First screenshot. Outcome of using the app, not your UI. The single highest-leverage conversion lever on the entire product page.
5. Description first 170 characters. Outcome the buyer is buying, not the feature list. Apple shows only the first 170 before the "more" link on iOS.
6. Localised metadata for at least the five highest-revenue storefronts. ASA is per-storefront. Running ASA in Germany on an English-only listing is the single most common indie waste.
7. Product-page conversion baseline. App Store Connect → App Analytics → Product Page. Note the current conversion rate. You need a baseline to know whether ASA spend is paying for itself.

Each of those checks takes about three minutes. Forty-five minutes of audit beats five hundred euros of misallocated ASA spend. The framework is not optional. It is the entry ticket to ads.

The one case where ASA goes first

ASA before ASO is correct in exactly one scenario. You have zero installs and zero data. The listing cannot be audited because there is no traffic to audit. You run a small ASA budget, fifty to one hundred euros, on a single high-intent keyword for seven days. The point is not installs. The point is product-page conversion data. Apple gives you tap-through and conversion-to-install in the ASA reports. Seven days of data tells you whether the listing converts at the rate you need to justify a larger ASA budget.

If conversion is above twenty-five percent, ASO is in good shape and ASA can scale. If conversion is below twenty percent, pause ASA, fix the listing, restart with the same small test budget. Iterate the listing, not the bid.

That is the one case. Everywhere else, ASO first.

Running ASA after the listing is fixed

Once the audit passes and the product page converts above twenty-five percent, ASA becomes a different tool. Three principles:

Bid on the anchor first, then the long tail. Your anchor keyword is the one you optimised the title around. ASA on the anchor reinforces the organic rank you already have. Long-tail variants pick up incremental impressions Apple is not surfacing organically yet.

Cap the daily budget at ten percent of expected MRR. Indie ASA spend that runs above ten percent of the revenue the app actually produces compounds into a cash-flow problem inside three months. The cap is not glamorous. The cap is survival.

Pause ASA when product-page conversion drops. Every screenshot regeneration, every metadata update, every seasonal copy refresh is a chance for conversion to dip. Pausing ASA during the dip prevents you from paying Apple to send buyers to a temporarily worse page.

ASA is a scaling tool. It is not a launch tool for indie apps with no install base. The discipline above keeps the spend from quietly eating the runway.

Why we built AsoGrove around this

The audit-before-spend framework is process work. Running it manually for one app on one storefront takes 45 minutes. Running it across five localised storefronts takes a Saturday.

AsoGrove's metadata generator runs the seven-check audit on every listing version before it ships. The 12 ranking signals it audits include all seven checks above, plus five more that catch the longer-tail issues an indie dev cannot keep in their head while iterating on the title.

Pair the audit output with App Store Keyword Research in 60 Seconds for the anchor-keyword work. Fix the listing first. Spend on ASA second. That order is the entire point of the post.

The order, summarised

1. Audit the listing on the seven checks above.
2. Fix any check that fails.
3. Optional. Spend €50 to €100 on ASA for seven days to read product-page conversion under paid traffic.
4. If conversion is above 25 percent, scale ASA.
5. If conversion is below 20 percent, pause, iterate the listing, restart.
6. Cap daily ASA spend at 10 percent of expected MRR.
7. Pause ASA on any week with a product-page edit. Resume after conversion stabilises.

That order is the difference between ASA as a tool and ASA as a tax.

50 founding seats at €49/mo for life are open while Cohort 1 is filling. Claim a founding seat 🌱.