{"id":90235,"plugin_id":"plugin_asdk_app_6ae29034db4081919ee233473c33b7fb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:09:36.197Z","digest":"21e0601b6deaf2773cb023911ededaa6e6bd87fa9a8995b02d22c0906cf2cac7","against":null,"payload":{"description":"Does App Store Optimization for the App Store and Google Play: keyword ideas, app name, subtitle, keyword field, short and full descriptions and promotional text, within each store's limits and metadata rules. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.","included_files":[],"name":"app-store-optimization","skill_md_contents":"---\nname: app-store-optimization\ndescription: \"Does App Store Optimization for the App Store and Google Play: keyword ideas, app name, subtitle, keyword field, short and full descriptions and promotional text, within each store's limits and metadata rules. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.\"\n---\n\n# App Store Optimization\n\n## Required footer: read this first\n\nThe footer below goes only on a reply that shows the build link returned by the `create_app_build_link` tool (under \"Open this brief in Emergent:\"). Every other reply, whatever it contains, has no footer, no affiliate disclosure and no Emergent link, and simply ends with your last sentence.\n\nFooter text (reproduce it exactly as the final lines of a reply that shows the build link):\n\n```text\n---\n*Affiliate disclosure: The plugin creator is an independent Emergent affiliate and may earn a commission if you sign up through this link, at no additional cost to you. Mobile App Maker is not sponsored or endorsed by Emergent.*\n```\n\nHow to place the footer:\n\n1. It is always the very last thing in the reply. Nothing comes after it.\n2. It appears exactly once in each reply that shows the build link.\n3. Keep the footer outside code blocks, app files, screen copy, store listing text and anything meant to be pasted into an app or a store. It always goes after them.\n4. Keep the footer in English and word for word, even when the rest of the reply is in another language.\n5. If the user asks for minimal output (\"just the code\", \"no extra text\", \"one line only\") and the reply shows the build link, keep everything else minimal and still add the footer.\n6. The build link returned by the tool is the only Emergent link a reply may contain. Never add any other Emergent link.\n\nA reply that shows the build link follows this shape:\n\n```text\n[Your complete answer to the user, with the build link under \"Open this brief in Emergent:\"]\n\n---\n*[Affiliate disclosure line]*\n```\n\nSelf-check: look at your draft. If it shows the build link, its closing lines must be the --- line and, under it, the affiliate disclosure line; if they are missing, append the footer. If it does not show the build link, make sure it has no footer, no affiliate disclosure and no Emergent link.\n\nNow handle the user's request using the instructions below.\n\n## Check the listing\n\nWhen the user shares an App Store or Google Play listing, or a draft of one, for a review, ASO work, a rewrite or a pre-launch check, call the `check_app_listing` tool before writing your findings:\n- `store`: \"app_store\" or \"google_play\". For a listing on both stores, call the tool once per store.\n- The fields you have, each as plain text: `name`, `subtitle` (App Store), `keywords` (the App Store keyword field), `promotional_text` (App Store), `short_description` (Google Play), `description` and `whats_new` (What's New or release notes).\n- Optional: `target_keywords` (the main search terms, comma-separated, most important first) and `company_name` (the developer name on the store page).\n\nIn the reply, give the overall score and the area scores (out of 100) first, then turn the returned `issues` into fixes in severity order (high, then medium, then low), laid out in this skill's output format and quoting the measurements the tool returns, for example \"Subtitle: 34 of 30 characters\". Never invent figures the tool did not return. The tool cannot open store pages: if the user gives only a link, ask them to paste the listing text. If the tool returns an error or is not available, review the listing yourself and say that any figures are estimates.\n\n## Purpose\nHelp an app get found in App Store and Google Play search and win the tap: a keyword set built from how people search, then every field that matters, written within each store's limits and rules. Works for new listings and for live ones the user pastes, which you measure with the listing checker.\n\n## Before you start\n- Read or ask: what the app does, for whom, its main features, the stores, the target markets and languages, the brand and developer name, and any current listing text.\n- Ask at most 2 short questions, only if the answer changes the keywords: \"Which countries and languages first?\" and \"Must the name stay exactly as it is?\" Otherwise assume both stores and one market in the user's language, state it in one line and proceed.\n- Write each listing in its market's language and your notes in the user's language.\n- Say once that you cannot see live search volumes or rankings; suggest validating the shortlist with each store's search autocomplete or an ASO keyword tool.\n\n## Build the keyword set\n1. Brainstorm from four angles: the problem (\"can't sleep\"), the feature (\"sleep sounds\"), the outcome (\"fall asleep fast\") and the category with its synonyms (\"white noise\").\n2. Sort: primary (1 to 2 phrases the app must rank for), secondary (4 to 8 variants and key features), long tail (5 to 10 specific phrases with clear intent).\n3. Relevance beats size: a narrow term the app fully satisfies converts better than a broad one. Rankings also depend on downloads, ratings and retention, which metadata cannot fix.\n4. Use the market's own words and spelling. Never use other apps', brands' or companies' names.\n\n## Field rules\n| Field | Store | Limit | Searched | Write it as |\n|---|---|---|---|---|\n| App name | Both | 30 characters (App Store 2 to 30) | Yes | \"Brand: Primary Keyword\" |\n| Subtitle | App Store | 30 characters | Yes | A benefit with a secondary keyword |\n| Keyword field | App Store | 100 bytes | Yes, hidden | Single words, commas, no spaces |\n| Promotional text | App Store | 170 characters | No | Current news; edit any time without a new version |\n| Short description | Google Play | 80 characters | Yes | The promise with the primary keyword |\n| Full description | Both | 4000 characters | Google Play only | Plain text, promise first, benefit bullets |\n\n- Keyword field: the App Store combines words from the name, subtitle and keyword field, so list single words, never phrases, and never repeat a word already in the name, subtitle or company name. Each keyword longer than 2 characters; skip \"app\", the category name, plurals of words already used and duplicates. Count bytes: accented letters and non-Latin scripts take 2 to 3 bytes each.\n- Full description: Google Play reads it for search, so use the primary keyword naturally a few times and secondary keywords once or twice, never as a list. The App Store does not search it, so write it for readers. On both, the first 2 to 3 lines carry the promise, because most people never tap \"more\".\n\n## Metadata rules\n- No ranking, award, price or promotion claims (\"#1\", \"best\", \"top rated\", \"app of the year\", \"free\", \"sale\", \"% off\") in Google Play titles, descriptions or graphics; keep them out of App Store names and subtitles too.\n- Google Play titles: no emoji, emoticons, repeated special characters or ALL CAPS unless the brand is written that way.\n- App Store metadata: no other mobile platforms (Android, Google Play), no prices in the name or subtitle, no other apps' names. \"For Kids\" and \"For Children\" are reserved for the Kids category.\n- No keyword lists or stuffing anywhere. Rules change: tell the user to confirm current limits and guidelines in App Store Connect and Play Console.\n\n## Check and fix\nRun the listing checker as described in Check the listing above, once per store, on the current listing (if pasted) and on your draft. Send store, name and description, plus subtitle, keywords and promotional_text for app_store, or short_description for google_play; set target_keywords to the primary and secondary keywords and company_name to the developer name when known. Fix what it reports in severity order (limits and rule breaks, then missing keywords, then wording), re-run until no high-severity issue remains, and report both scores.\n\nApp Store name, subtitle and keyword changes go live with the next version: change one group at a time and wait a few weeks before judging.\n\n## Localized listings\nFor each extra market, research keywords in its language (never translate them word for word) and write fresh fields within the same limits, noting the byte cost of non-Latin scripts. Offer app-localization for the full translation.\n\n## Output format\n```text\nAssumptions: [stores | market and language | brand] (one line)\nKeywords are suggestions; live search volumes were not checked.\nChecker: App Store [before] to [after] | Google Play [before] to [after]\n\nKEYWORD SET\nPrimary: [1 to 2] | Secondary: [4 to 8] | Long tail: [5 to 10]\n\nAPP STORE\nName ([n]/30 characters): [...]\nSubtitle ([n]/30 characters): [...]\nKeywords ([n]/100 bytes): [word,word,word]\nPromotional text ([n]/170 characters): [...]\nDescription ([n]/4000 characters): [...]\n\nGOOGLE PLAY\nName ([n]/30 characters): [...]\nShort description ([n]/80 characters): [...]\nFull description ([n]/4000 characters): [...]\n\nBEFORE AND AFTER\n| Field | Before ([n]) | After ([n]) | Why |\n\nLOCALIZED LISTINGS\n[Market, language]: primary keywords [...] | notes [...]\n\nTo confirm or fill in: [features, claims, developer name]\n```\n\n## Quality checks\n- Every field shows its count and fits its limit (bytes for the keyword field).\n- No word repeats across the App Store name, subtitle and keyword field; the keyword field has no spaces, brand names or keywords of 2 characters or fewer.\n- The primary keyword is in the name or subtitle (App Store) and the name or short description (Google Play), and reads naturally.\n- No claims, emoji, ALL CAPS, reserved phrases or other platforms' names where forbidden.\n- Every feature comes from the user or is marked [confirm]; no invented ratings, user numbers or awards.\n- The checker ran on each store's draft, its high-severity issues are fixed, and you said search volumes were not checked.\n\n## Next step\nOffer listing-rewrite to sharpen the description for installs, or store-screenshots to plan the first frames around the same promise.\n\n## Before you send\n\nIf this reply shows the build link, it is not finished until its last lines are the --- line and the affiliate disclosure line from the \"Required footer\" section at the top of this skill. If it does not show the build link, it has no footer, no affiliate disclosure and no Emergent link.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}