Short answer: your ad is your listing

Apple builds your Search Ads creative from the metadata on your App Store listing: the title, subtitle, screenshots, and ratings a shopper sees. RevenueCat's ASA guide states this plainly, and it sets the order of operations for everything in this guide. When your listing is English-only, your ad is English-only too, no matter which country you target. No bid changes what the ad shows. Only a localized listing does that.

Two failure modes follow. The first is invisibility: your English keywords never match what shoppers type in Tokyo or Berlin, so the ad rarely shows. The second is waste: the ad shows to the right shoppers in the wrong language, they skip it, and you pay for taps that never convert. Both look like an ads problem. Both are listing problems.

So the sequence runs listing first, keywords second, account structure third. Localize the product page for one market. Build keyword lists from local behavior for that market. Then aim ad groups at that market alone. Our App Store Connect setup guide walks through the listing half, and this guide covers the ads half in the same order.

Why localized listings win paid Apple search

Paid search in the App Store rewards relevance the same way organic search does. An ad that matches the shopper's language gets the tap, and tap-through feeds the relevance signals Apple uses to price your next impression. An English ad shown to a German search starts behind on every auction. It earns fewer taps, weaker relevance, and a higher cost per tap. Localization moves the ad from foreign to native, which lifts the two numbers deciding whether a country pays for itself.

Here's the passage worth quoting. A complete Apple Search Ads localization pass runs in this order. First, localize the listing for one pilot country: title inside 30 characters, subtitle inside 30, keyword field inside 100, description and screenshots matched to that market. Second, build that country's keyword list from local behavior: run Search Match to harvest the terms shoppers type, pay a native speaker for one hour to mark which candidates carry demand, and log negatives for English terms that leak in. Third, structure one campaign per country with ad groups split by theme, brand versus category versus competitor, so bids stay readable per market. Fourth, measure tap-through rate and cost per install per country for six weeks, then expand only where the numbers earn it. ShyftUp puts the prize in context: the United States leads App Store spending near 6.5 billion dollars, China follows near 4.5 billion, and Japan adds near 1.7 billion. Those markets repay localized listings many times over once the listing reads native.

One research pass serves two channels. The keyword list you build for paid search doubles as raw material for your organic keyword field, and the Search Match terms Apple surfaces show you demand your organic research missed. Paid insights flow back into the listing, the stronger listing lifts both auctions, and each market funds the next one. Our keyword-field guide covers the packing discipline on the organic side.

Research keywords per country instead of translating them

A translated keyword is a guess. A researched keyword is evidence. Shoppers in different countries search with different words for the same app: slang, synonyms, and category terms that no dictionary maps one to one. ShyftUp's guide names this as the step most teams get wrong, and the fix is procedural, not clever Never ship a keyword list that nobody who searches in that language has checked.

Start with Search Match. Apple's discovery match shows your ad against terms it thinks fit, and the search-term report tells you what shoppers typed. Run it for two to four weeks in the pilot country, harvest the real queries, and promote the winners into exact-match ad groups. You'll find terms your English brain never generated, plus spelling variants and local brand comparisons worth bidding on.

Then pay a native speaker for one focused hour. Hand over the harvested list plus your translated candidates. Ask which terms carry buying demand, which sound stiff, and which slang you missed. One hour costs little and catches the errors that burn budget for months: a stiff term that never converts, a slang miss that hands the market to a local rival. AppFollow's 9-market Q and A adds a trick worth stealing: leftover terms from one locale can serve another, such as Spanish (Mexico) terms covering English (UK) gaps. Our cross-localization guide covers the organic side of that stacking so both channels share the homework.

Close with hygiene. Log negative keywords for the English terms that leak into each country's auctions. Favor long-tail terms early: they cost less per tap and signal clearer intent than single head words. Foxdata's keyword guide makes the same call for new accounts. Log the final list per country so next quarter diffs against a known baseline instead of starting from zero.

Localize the creative Apple shows with the ad

The ad carries your title, subtitle, screenshots, and rating into the search results. Shoppers decide in seconds whether that creative feels built for them, and nothing in your bid changes what they see. A German shopper who taps an ad with English screenshots lands on an English story and bounces. You paid for the tap. The listing lost the install.

Treat screenshots as ad creative, not decoration. Each pilot locale needs captions in its own language over app UI that matches that market: local currency, dates, and examples where your app shows them. ShyftUp's guide lists cultural relevance beside translation for this reason. A caption that promises a feature the screenshots never show reads as a broken promise in every language. Our screenshot translation guide walks through the drafting side, and our publish-screenshots guide covers the upload into each locale slot.

Match the words too. The title and subtitle in the ad must read native inside Apple's 30-character caps, because truncation in German or Portuguese can cut the exact term you bid on. The description below the fold should carry the same claims the screenshots make, so the page reads as one story after the tap. If you run campaign-specific product pages, give each one the same treatment by hand in Connect: localized screenshots and promo text per page, since paid traffic lands there first.

Run the QA pass before you spend. Open each locale preview as a shopper sees it, check caption language against UI language frame by frame, and confirm each set sits in the right locale slot. Our localization QA guide gives you the full ordered pass. Ads multiply whatever the listing is, so point spend only at listings that read clean.

Launch one country at a time on an indie budget

Apple Search Ads fits small budgets better than most paid channels. RevenueCat's guide explains why: billing happens per tap, there's no post-install optimization engine demanding huge volume, and campaigns stay readable at spends that social networks would starve. That makes one-country pilots cheap to run and cheap to kill.

Pick the pilot from evidence. Open App Analytics and find a country with downloads or page views but no localized listing: demand exists, supply does not. That gap is your first campaign. Set a small daily cap, one campaign per country, with ad groups split by theme so brand terms never hide inside category spend. Keep the structure boring. Boring structures produce readable reports.

Read two numbers per market: tap-through rate and cost per install. Tap-through tells you whether the creative reads native. Cost per install tells you whether the market earns its keep. Give each pilot six weeks, the same window our strategy guide uses for funding waves, then expand in revenue order: the next country is the one whose numbers already argue for it. Kill pilots whose cost per install never bends, and roll their keyword homework into the next candidate. Small budgets win by sequencing, not by spraying.

How App Store Localizer fits Apple Search Ads

App Store Localizer (https://asolocalization.com) builds the locale pack this guide assumes. Paste a public App Store URL and it imports your title, description, icon, and screenshots through Apple's public lookup API. It translates the title, subtitle, description, and the 100-character keyword field per target locale, generates localized keywords from free heuristics over your listing, and re-renders screenshots with translated captions in iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732 sizes. Coverage runs to 20-plus target locales, from Japanese, Korean, and both Chinese scripts through German, French, Spanish, and Brazilian Portuguese down to Hindi, Thai, and Vietnamese. You download the finished assets or publish toward App Store Connect.

Prices are one-time per listing, which keeps multi-country pilots cheap to test. Starter at 19.99 dollars covers 3 languages with each available screenshot. Global at 99.99 dollars covers all supported languages. No subscription, no per-seat fees. Two honest limits shape where the tool stops and your workflow starts. Output is machine-generated, so run the native-speaker hour from this guide over each pilot market before you bid, starting with keywords, name, and screenshots. Keyword ideas come from listing heuristics rather than paid search-volume data, so confirm top terms against Search Match reports once spend flows. The tool serves the store listing only, never the app itself.

Frequently asked questions

  • Does Apple Search Ads use my App Store listing for the ad? Yes. Apple builds the ad creative from your listing metadata: title, subtitle, screenshots, and ratings. An English-only listing means English-only ads in every country you target. Localize the listing first, because no bid or budget changes what the ad shows. - Should I translate my ASA keywords or research new ones? Research new ones. Translated terms miss the slang, synonyms, and category words locals type. Run Search Match for two to four weeks, harvest real queries, promote winners to exact match, and pay a native speaker for one hour to mark demand and add slang. - How do I find keywords in a language I don't speak? Combine three sources: Search Match reports from a pilot campaign, competitor titles buyers already tap, and one native-speaker hour over your candidate list. Log the final list per country so next quarter diffs against a known baseline. - Which country should I run Apple Search Ads in first? The one where App Analytics already shows downloads or page views but your listing is still English. Proven demand plus missing supply is the cheapest test. Set a small daily cap, run one campaign for that country, and expand only where tap-through and cost per install earn it. - Should I localize my listing before spending on ads? Yes, always. Ads multiply the listing: clean localized pages turn spend into installs, while English pages turn the same spend into bounces. Draft the locale pack, run the QA pass, then switch on the campaign. Our cost guide helps you budget the listing half before the ads half starts.

Paste your App Store URL at https://asolocalization.com today and draft this quarter's pilot locale pack this afternoon. Localize the listing, research one country's keywords, run the QA pass, then switch on a single-country campaign with a small daily cap. Read tap-through and cost per install for six weeks and fund the next market only where the numbers earn it.